I build the quiet parts of great products.

I'm a UX software engineer and design systems consultant. For two decades I've lived at the seam between design and engineering — building the component libraries, tokens, and documentation that let teams ship faster without tripping over themselves.

My favorite question to sit with is a quiet one: how do you build a system where the right output is the natural result of using it — not something individual developers have to remember to do correctly?

Design Systems Accessibility Documentation UX Engineering

What I'm building right now

Three systems, three stacks

I like being in the work — not above it. Here's what's on my bench this quarter.

Travelers

Web Components · React

An accessible component library that crosses framework boundaries — built so the right markup is the only markup you can ship.

Berkshire Hathaway Specialty

Vue.js · Nuxt.js

An enterprise-scale component library for an insurance platform where consistency isn't aesthetic — it's regulatory.

America's Test Kitchen

React · Next.js

A shared component system unifying multiple editorial brands — where design tokens carry as much weight as the recipes.

How do you build a system that makes the right output the natural result of using it — rather than the result of individual developers making the right decisions?

— the question I'm always chasing

How I work

Three things I hold on to

Accessibility as architecture

Not an audit at the end. Not a ticket for later. A structural constraint, built into the foundation, so every component that leaves the library is accessible because it can't be any other way.

Documentation is delivery

A component without accurate docs isn't done. It's a riddle. I treat the written word as part of the shipped artifact — examples, rationale, edge cases, and all.

Directness over diplomacy

If your system is sick, I'll tell you exactly where and why — kindly, but without hedging. Then we'll map the shortest honest path to health. You're hiring me for the truth, not the comfort.

Always learning

Twenty years in, still reading the spec drafts

I stay close to the sources: WAI-ARIA working drafts, the Design Tokens Community Group, CSS Working Group proposals. The platform moves — the best systems move with it.

I also maintain Rudiment UI, an open-source library where I sharpen ideas in public before they land in client work.

currently on the nightstand

WAI-ARIA & APG
currently dog-eared

Authoring practices for patterns that truly work for assistive tech.
Design Tokens CG
highlighter-stained

The emerging standard for portable, multi-platform design decisions.
CSS Working Group
ink still wet

Container queries, anchor positioning, cascade layers — the good stuff.
Rudiment UI
built in public

My open-source sandbox for accessible component primitives.

Think we'd work well together?

Start with the free 10-minute scorecard, or grab an intro call. I'll tell you honestly whether I can help — and if not, I probably know who can.

Score your design system Book an intro call