My career has moved between design systems leadership and product — deliberately. I've helped define IBM's design system, driven adoption across teams who didn't choose it, built the contribution and governance frameworks that kept it consistent at scale, and worked inside the product teams who 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 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 — contributions that shaped Carbon from the inside, not the top down.
I built the infrastructure for design at scale.
A searchable gallery of IBM product experiences — making good design discoverable, reusable, and systematic.
I design products. I also use AI to ship code.
Seven years across five IBM products — and when the handoff wasn't working, I stopped handing off and contributed the fixes myself.