design system
one coherent set of tokens, components, and rules that kept a fast team consistent.
the product had grown feature-first, and it showed — power users coped, everyone else bounced. the brief was deceptively simple: keep the depth, lose the noise, and make the first five minutes feel calm and obvious.
understanding the real job
we started in the field — interviews, support tickets, and a teardown of the existing flows — to separate what users said from what they actually did. the pattern was clear: the product was capable but overwhelming.
many directions, one principle
i explored several structures in parallel and pressure-tested each against the core principle: calm by default, depth on demand. prototypes went in front of users weekly so the direction earned its confidence.
getting the details right
the final stretch was about the small things — motion, density, empty states, the exact weight of a label — and a system that let a fast team stay consistent without slowing down.
the redesign shipped in stages and quietly changed how people felt about the product — fewer support questions, faster onboarding, and a base the team could keep building on.