Architecture
A token taxonomy and component API designed to scale — primitive, semantic, and component layers that stay legible as the system grows. Good architecture means the right change is the easy change.
About
I build the systems other designers build on
Ten years across enterprise SaaS, healthcare, and the public sector — with a bias toward tokens, accessibility, and governance that outlasts a single launch.
Approach
What I bring to a team
I’m happiest where design, engineering, and platform overlap — turning scattered patterns into infrastructure teams can rely on. I care as much about the token no one sees as the component everyone does.
Craft
Precise typography scales, a sensible spacing system, and interaction detail that feels considered rather than decorated. In a design system the details are the product — they set the bar every team inherits.
Accessibility
WCAG 2.2 AA baked into the tokens and patterns, not bolted on. I test with keyboards, screen readers, and real contrast ratios, so accessibility ships by construction instead of by audit.
Background
A short version of the story
Replace this with your own biography — it’s written as neutral placeholder copy you can edit freely.
I started in product design and drifted toward systems work when I realized the same inconsistencies kept surfacing across every team — and that the leverage lived in the shared foundation, not any single screen. Since then I’ve led design systems used by dozens of designers and engineers.
My favorite engagements are the ones where a system has stalled and no one quite trusts it anymore. I like doing the honest inventory, rebuilding the tokens and governance, and watching adoption climb as teams start reaching for the library instead of working around it.
Outside of client work I write about token architecture, mentor systems designers, and spend an unreasonable amount of time perfecting spacing and type scales. Available for select full-time and consulting engagements.
FAQ
Common questions
Full design system builds, token and theming pipelines, accessibility pattern work, and governance — the operating model that keeps a system adopted. If it’s a real consolidation problem with committed stakeholders, I’m interested.
Let’s build a system teams reach for
Send a note with a bit of context — how many teams, and what’s inconsistent today — and I’ll get back to you within a few days.