about.

I build the frontend layer between design systems and production — mostly in AEM, mostly in regulated environments where the consequences of getting it wrong are measurable.

Since 2013 I've been building accessible, scalable frontend systems for enterprise teams. Most of my work lives at the intersection of design systems, AEM architecture, and accessibility — in organizations where the cost of getting the frontend wrong is real.

I specialize in AEM frontend architecture — component systems, ClientLib design, and the governance work that keeps shared codebases from fragmenting across teams. Seven years of that at Fortune 200 banking scale.

I also focus on accessibility. Not as a compliance layer added after the fact, but as something built into the component architecture — tested with NVDA and VoiceOver, not just axe-core.

The work that interests me most is at the boundary where design decisions become engineering decisions. Someone has to hold both — and that's the role I occupy.

I tend to diagnose before building. The most useful thing I've done on several projects was deciding what not to build.

I work best in organizations where design and engineering teams respect each other's constraints — where "that's not possible" and "that's not right" are both legitimate answers.