More on how I work.
My role is to bring structure and direction to ambiguity, helping teams define what actually matters, make tradeoffs explicit, and turn complexity into something people can understand and use. I care about how things feel as much as how they function: how clarity, hierarchy, and interaction design shape trust and behavior over time. The goal is making sure it holds up when it ships, scales, and gets used in the real world.
What that means in practice
Design systems that hold up under pressure
Create patterns and foundations that scale without losing clarity or cohesion.
Build accessibility in from the start
Accessibility isn't a layer, it's how I structure decisions, flows, and interactions.
Define and refine what actually matters
Cut through noise and make complex products feel clear and usable.
Turn constraints into workable solutions
Use product, technical, and business limitations to create practical, shippable outcomes.
Find the signal in noisy products
Simplify complexity and bring focus to products that have grown hard to understand.
Know how it gets built
I work in HTML, CSS, SCSS, and enough JavaScript to build the real thing. This site, its token pipeline, and its component library are mine, and the source is public.