Boeing Design System

The problem at scale

Boeing operates across dozens of internal product teams, mission-critical flight deck software, logistics tooling, enterprise applications, each with its own design history and front-end stack. Without a shared visual language, teams were encountering the same problems independently, shipping inconsistent experiences, and creating a design sprawl compounding until it was almost impossible to unwind.

The design system team was stood up to address this. I joined as part of the founding cohort, with responsibility spanning component design and code, standards, documentation, education, and cross-org adoption.

Token infrastructure

Maintaining that contract meant reviewing contributions for semantic integrity, keeping the documentation current, and coaching designers on how to structure Figma files (variables, component logic, auto-layout) so the semantic relationships held all the way through handoff. That's where token infrastructure either compounds or collapses.

Component standards

Component standards work at a large enterprise isn't primarily a design problem. It's a communication problem. The harder work is establishing what "done" means in a way that multiple teams with different codebases and different definitions of quality can actually converge on.

This involved: defining anatomy and naming conventions that could translate across frameworks, building documentation templates that surfaced usage guidance alongside visual specs, and creating the review patterns that kept component quality consistent as the library grew.

Adoption and coaching

A design system that isn't adopted is just documentation. The adoption work involved working directly with product teams, helping designers understand how to structure Figma components and variables in ways that would generate clean, predictable token output, and helping engineers understand when to use a component versus diverge, and how to flag gaps back to the system team.

I also coached designers on the Figma scaffolding practices that support AI-assisted development workflows: the structural choices in auto layout, component properties, and variable binding that determine whether a handoff produces usable code or requires extensive cleanup.

What this work is

Enterprise design systems work is unusual because success is mostly invisible. The sign that it's working is that nothing breaks when teams move fast, that the system stays coherent as it grows, and that consuming teams feel enabled rather than constrained. That kind of work doesn't produce a single dramatic before/after. It produces a different trajectory.

The Boeing Design System is the most concentrated expression of my systems thinking. It connects everything: the token work, the front-end craft, the cross-functional collaboration, and the organizational will to make something like this actually land at a company that size.