Building design systems that scale product teams, not just toolkits.
I'm a UI designer who specializes in design systems production, documentation, and component library management. 15+ years building and scaling design systems across Intuitive Surgical, Microsoft, REI, Lululemon, and Kaiser Permanente.
Approach
Good systems make the next decision easier.
The best design system work isn't a library of perfect, polished components sitting in a file waiting to be admired. It's production infrastructure — a way of making decisions together that stays useful across releases, products, and the people who inherit it.
Parity is a production practice. A design library, a documentation site, and a coded component can share the same name and still tell three completely different stories. The small details are the real work.
Documentation is a design surface. If the explanation is hard to scan, the interface underneath is probably hard to use too. Clear docs push the API toward clarity — they're part of the product.
Adoption is a design problem. A system grows when teams can find what they need, understand why it exists, and contribute changes without asking permission for every single move they make.
Selected work
A closer look at design system work built and scaled inside enterprise teams, each project shaped by its own production, adoption, or governance challenge.