Forgiving validation and progressive disclosure; completion on the highest-traffic form rose from 33% to 63%.
See the full storyProof of work
State was scattered across a dozen patterns, so a bug in one corner would surface somewhere unrelated and nobody trusted a fix until it shipped. I untangled it into one predictable model, deleted the clever parts, and made the data flow something you could follow by reading.
Forgiving validation and progressive disclosure; completion on the highest-traffic form rose from 33% to 63%.
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.
Simplified the flow to three steps; checkout completion rose from 38% to 51%.
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.
Reworked the first-run flow; activation rose from 44% to 63% within two release cycles.
Mobile releases were fragile and every offline edit turned into a conflict someone had to resolve by hand. I re-architected sync around a merge strategy that could not lose writes, so state just worked offline and shipping stopped feeling like a gamble.
Audited dependencies and lazy-loaded routes; the main bundle shrank 65% with no feature loss.
Build products that respect the user's time, attention, and data.
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.
