DESIGN SYSTEMS

Contributing to systems that ship at scale

Design systems work is most interesting when the stakes are high. I've contributed to Oracle Redwood, Oracle's enterprise-wide design system, and to Microsoft's Fluent Design System, where patterns land across Edge, Internet Explorer, and Windows. Working at that scale changes how you think about every decision. A spacing rule that works wrong, or a component that's ambiguous to interpret, becomes a problem in thousands of contexts.

At Expedia Group I led the development of a new design system built from the ground up to support a product organization that had grown faster than its shared vocabulary. The goal was to create structure that gave teams speed without sacrificing consistency.

Microsoft Fluent: patterns at platform scale

As part of the Windows Controls and Patterns team, I designed components and interaction patterns for the Microsoft Fluent Design System. Working at platform scale means every decision has downstream consequences. A focus behavior or a spacing rule that works wrong becomes a problem in thousands of contexts across multiple products.

A component without clear usage guidance is a component that will be used wrong. The most durable design system work isn't the components themselves. It's the rules that explain when to use them, when not to, and why. That documentation is what lets a system outlast the team that built it.