Sky – Orion Design System

Web-based components did not translate cleanly to native mobile environments, and there was no shared toolkit aligned with iOS and Android guidelines. Accessibility practices were inconsistent, and design-to-development handoff lacked structure.

A key technical objective was defining a scalable component naming convention that could integrate with Sky’s internal AI system, the “Sky namespace”, enabling automated recognition and management of components. The broader goal was to establish a single source of truth that could scale across teams, products, and platform

I contributed to defining and designing core mobile components while helping shape the structure and documentation of the system. I worked closely with UX, research, and engineering teams to ensure the system was practical, scalable, and aligned with platform conventions.

A significant part of my role involved documenting behaviours, usage patterns, and naming structures so components could be consistently understood and implemented across teams.

I helped establish a dedicated mobile component set tailored to iOS and Android guidelines, embedding accessibility considerations from the outset.

Rather than simply adapting web components, we defined patterns suited to native environments and ensured their properties were clearly documented. This supported more reliable implementation and reduced ambiguity during development.

I built and maintained a shared design toolkit in Sketch and contributed to detailed documentation in Confluence. Workshops and collaborative sessions were used to align teams around naming conventions, scalability principles, and cross-platform thinking.

To communicate the longer-term vision of Orion as a centralised design resource, I created an interactive InVision prototype that demonstrated how the system could evolve into a unified internal hub.

The work helped establish clearer standards for native mobile design within Orion and strengthened collaboration between design and development teams.

The interactive prototype played a key role in communicating the broader vision, encouraging adoption beyond mobile. Over time, additional teams began contributing components, reinforcing Orion’s role as a shared, cross-platform system rather than a siloed toolkit.

This project deepened my understanding of governance, documentation, and the operational side of design systems at enterprise scale.