Process
Feb 20, 2026
4 min read
Shipping the unglamorous version
The version you're embarrassed by teaches you more in a week than the perfect version teaches you in a quarter of polishing.
Atlas — the travel app I'm proudest of — launched without the map. The feature everyone now screenshots wasn't in version one, because version one had a job: find out if anyone would journal at all.
Polish is a hiding place
I've watched teams spend a quarter refining an onboarding flow for a product nobody had confirmed wanting. Polish feels like progress because it produces visible improvement daily. But it's improvement of the wrong certainty — you're sharpening the answer before checking the question.
Embarrassment is data
The unglamorous version tells you which missing thing users actually hit. Atlas's beta users didn't ask for the map — they asked for offline capture, which we hadn't ranked in our top five. The roadmap we shipped against was written by the gap between the rough version and real trips, not by our taste.
Ship the version that answers the question. The version worth being proud of is built from what you learn.