I spent my twenties trying to make the internet feel a little less noisy. These days I do it for early-stage founders, design-led teams, and the occasional museum.
I care about the boring bits — empty states, error copy, the third tap — because that's usually where trust is won or quietly lost.
From a sticky problem to a shipped product. I embed with your team for 8–16 weeks and leave behind patterns, principles, and a design partner on speed-dial.
A system your engineers actually use. Tokens, components, docs, and a governance model that survives your next PM reorg.
For founders and small teams: critique rituals, research crash-courses, and half-day workshops that turn “make it pop” into a shared vocabulary.
Every engagement is different, but the shape is mostly the same: look closely, make something, look again, make it better.
Stakeholder chats, a handful of customer calls, and a ruthless audit of what already exists.
Flows, rough frames, and 2–3 divergent directions. We pick one, together, before pixels get precious.
Hi-fi screens, a working prototype, and the component scaffolding your engineers need to move fast.
Pairing with engineering through launch, plus a 30-day check-in once it's in users' hands.