My career has moved between design systems leadership and product — deliberately. I've shaped IBM's design system, driven adoption across teams who didn't choose it, and built the governance frameworks that kept it consistent at scale. I've also owned product design inside the technically complex, developer-facing platforms that depended on it. That back-and-forth is what shaped how I think: systems need to be led by people who know what it's like to be on the receiving end.
That perspective is what makes the difference between a system teams adopt and one they route around.
System adoption at scale — with teams who didn't choose it.
Eight products, nine months, one platform — strategy, governance, and earning trust from teams who didn't choose the system.
I owned the product. I also fixed it in the codebase.
Sole designer on a capability within a developer-facing enterprise platform, from concept to GA. When handoff broke down, I used AI to contribute fixes directly into the codebase.
I led the team that gave IBM designers their design foundation.
30+ components, token architecture matched to the codebase, one lean team — and 165% adoption growth in five months.
Good design dies in handoff. I found out why — and changed it.
Research across 100 developers, a systemic finding, and three interventions that changed how IBM teams deliver design.
I found the gaps in the system and filled them.
Components, patterns, and guidance — contributed from within product teams and adopted as system-wide standards.
I built the infrastructure for design at scale.
A searchable gallery of IBM product experiences — making good design discoverable, reusable, and systematic.