Case 03 · 0→1 Product · 2024
Atlas
A consumer app from concept to prototype — shaping a new product idea end to end, from the first sketch to a clickable, testable thing.
Overview
A short summary of what Atlas was and why it mattered.
Set the scene in a few plain sentences. What was the idea, who was it for, and what were you trying to prove? Zero-to-one work lives and dies on a clear premise — state it cleanly here.
[Replace with the one-breath story: the hunch, the exploration, and where it landed.]
The Problem
The need you were designing into.
For a new product, the "problem" is the unmet need or the bet. Describe the behaviour you observed, the gap in what existed, and why it was worth building for. Keep it grounded in real people, not a market-size slide.
[Add the insight that made you believe there was something here.]
Approach
How you shaped it.
Walk through going from ambiguity to form: the concepts you sketched, how you narrowed, the core interaction you designed around, and how you pressure-tested it. Show how you make decisions with incomplete information.
Outcome
Where it landed, and what you learned.
Close with what the prototype proved (or disproved), how it tested, and what you'd carry forward. For 0→1 work, an honest account of the learning is often more compelling than a vanity metric.
[End with a short reflection.]