Forgiving validation and progressive disclosure; completion on the highest-traffic form rose from 23% to 34%.
See the full storyProof of work
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.
Forgiving validation and progressive disclosure; completion on the highest-traffic form rose from 23% to 34%.
The app felt fine on a developer laptop and slow on the devices and networks our users actually had. I made performance a first-class constraint with budgets enforced in CI, then went after the critical path until the numbers held on mid-tier hardware.
Reworked the first-run flow; activation rose from 25% to 50% within two release cycles.
The product shipped in one language, and bolting on the rest turned every string into a small argument about layout. I made internationalization structural — extraction, pluralization, and right-to-left handled once — so a new locale became configuration rather than a rewrite.
Moved to a CRDT-style merge; offline conflict reports fell 30% quarter over quarter.
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.
Replaced a dozen ad-hoc patterns with one predictable store; state-related bug reports dropped 65%.
Cut complexity until what's left is obvious — then ship it.
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.
