Componentized 10 patterns into one library; 6 product teams now ship from it.
See the full storyProof of work
Users were dropping off before they ever reached the thing that made the product worth paying for. I instrumented the funnel, separated real friction from perceived slowness, and rebuilt the first-run flow around the shortest path to that first win.
Componentized 10 patterns into one library; 6 product teams now ship from it.
The interface had grown by accretion and every change risked a regression somewhere nobody thought to check. I set the architecture, drew the boundaries the team had been missing, and made the safe path the easy one so doing it properly stopped costing extra time.
Moved 5 surfaces incrementally with zero feature freeze — the app never stopped shipping during the migration.
Rendering everything on the client meant a slow first paint and an SEO problem we kept explaining away. I moved the right work to the edge — streamed the shell, hydrated what mattered — and got a fast first view without giving up interactivity.
Simplified the flow to three steps; checkout completion rose from 27% to 38%.
Every developer had their own way to start the app, and half the tooling only ran on the machine of whoever wrote it. I rebuilt the dev experience — one command to run everything, fast feedback, and defaults that made the right thing the easy thing.
Reworked the first-run flow; activation rose from 41% to 73% within two release cycles.
Sweat the boring details so the experience feels effortless.
Off the clock
In public
Practical bits
Unlock with a company account to message directly and reveal:
Jump back to the board with this background already filtered in.
