As the UI designer, my work was part of a team effort at Virgin Australia that delivered big results. Our squad's features drove over $4M in new annual revenue, including a $1.7M lift from a new flight search and a $2.3M+ boost from new in-app purchase options.

The key is making the system the easiest path for them to build. I partner with engineers to create a workflow they can trust, which includes clear semantic versioning (MAJOR.MINOR.PATCH), detailed changelogs, and design tokens that are synced directly from Figma via its REST API. Help setup Figma's CodeConnect, with some team on-boarding and you have strong foundation > It’s about building a practical toolkit, not just a rulebook.

On the 'Journey Tracker' project at Virgin Australia, our squad had to wrangle a massive amount of live flight data. My role was to design a clean and simple UI that made all that complexity feel calm and intuitive for the user. It was a huge team effort that ended up being a first for any Australian airline.

The opposite. A good system handles the boring, repetitive stuff so the team can focus its energy on solving the truly unique, hard problems. It creates consistency where you need it, and freedom where it counts.

It's a team sport. I design to WCAG standards, but the real work is partnering with developers to build accessibility into our core components from the start. That way, building inclusively becomes the default for everyone.

The time it saves developers is huge, but we also track its impact on the product itself. We look for things like fewer UI bugs, getting new features out the door faster, and seeing real lifts in conversion on the things we build with it.

I've worked at both ends of the spectrum: from lean startups where I've built nimble systems from scratch, to enterprise scale at Virgin Australia where the system I helped build was used across 2 brands, 7 squads, and 150+ people.