Skip to main content

How do you build a design system that people actually use, not just one that exists?

Auro: Alaska Airlines Design System

Built, managed, and taught a company-wide design system at Alaska Airlines, then created the structure that let it serve the Hawaiian Airlines brand too.

  • Design Systems
  • Design Tokens
  • Front End
  • Product
Role
Product Designer, Design Systems. Grew with the team from UI design intern to contract product designer, associate UI designer, and product designer.
Team
3 engineers, 1 UI designer, 1 product manager, and me, partnering with 40+ designers across product teams
Timeline
June 2022 to December 2024
Location
Seattle, WA

Problem, decision, result

Problem
There was no source of truth: UI was inconsistent, components were duplicated, and designers and engineers worked from different sources.
Decision
One source of truth for everyone: a single documentation site plus a Figma library holding every token.
Result
35+ WCAG 2.1 AA compliant web components, used by 40+ designers, and a token structure the team used to deliver Hawaiian Airlines theming.

The problem

Before Auro, there was no source of truth. UI was inconsistent across products, components were duplicated, raw values were hard-coded everywhere, and designers and engineers worked from different sources.

Who was affected: Designers, engineers, and product owners across Alaska's digital products.

Why it mattered: Slower builds, accessibility gaps, brand drift, miscommunication between designers and developers, and inefficient processes.

What I did

  1. Move 1: Blueprints both designers and engineers can read

    I created a documentation template, pre-filled with language that works for both engineers and designers. Each blueprint became the engineering handoff. Designers and engineers then met for refinement sessions on edge cases and technical limits, and I iterated until we all agreed.

    TODO: add visual: documentation template pages (anatomy, structure, states, behavior).

  2. Move 2: Designing in Figma and in code

    I designed and managed 35+ components in our Figma library and contributed to the front-end code itself, pair programming with our engineers in CSS, Sass, and JavaScript to refine component UI.

    TODO: add visual: code screenshot next to the Date Button variants.

  3. Move 3: A structure built for more than one brand

    I created a token structure that could work across multiple brands, setting the foundation for theming Auro for Hawaiian Airlines. It was hard to push for something that didn't exist anywhere at the company yet. I handed it off when I moved teams, and the team delivered it well.

    TODO: add visual: Figma variables with brand modes.

  4. Move 4: Teaching the system so people actually use it

    A design system only exists if people use it, so education was part of maintaining it. I ran workshops, classes, and trainings (Figma tutorials, Design System 101, Systematic Design Thinking) and wrote step-by-step docs, like how to contribute new icons.

    TODO: add visual: education slides and the live training screenshot (blur coworkers' faces and names first).

What didn't work

TODO: June to add what didn't work on this project. The source draft has no content for this section.

Key decision

One source of truth for everyone: a single documentation site plus a Figma library holding every token, shared by designers and engineers, instead of separate design and engineering references.

What it took

A real shift in how designers and engineers worked and thought, and buy-in from leadership, which was critical to making a single source of truth stick.

Outcome

  • 35+ WCAG 2.1 AA compliant web components, adopted across all products
  • Library used by 40+ designers across e-commerce
  • A multi-brand token structure that the team used to deliver Hawaiian Airlines theming
  • Mentored 4 junior designers and interns
  • 10+ internal sessions on systems thinking and Figma best practices
  • Shared the work at Figma Config 2024 in "Design Systems for XL Displays," which covered both Auro and the lobby signage

TODO: June to add a link to the Config 2024 talk, and optionally a one-sentence quote from an engineer or designer.

What I'd do next

Push the structure further into multi-theming, so one system can serve more brands and contexts beyond two airlines.