The insight
Why a rebuild feels like the clean answer
When a product has accumulated awkward flows, old decisions and unfinished features, starting again can look simpler than untangling it. A blank canvas promises speed, clarity and relief.
But customers do not experience your architecture. They experience the moment they cannot understand, trust or complete. Rebuilding everything before locating that moment puts the largest possible solution against an unmeasured problem.
The checks
Five questions to answer first
The useful question is not whether the product feels old. It is whether the current product prevents the next important customer outcome.
- Can new users understand the value without help?
- Where do qualified users stop or hesitate?
- Are people asking for a missing capability or a clearer path?
- Is the underlying system genuinely blocking safe changes?
- What already works well enough that it should be protected?
The decision
Find the smallest fix that changes the outcome
A focused fix gives you something a rebuild cannot: a fast learning loop. Improve the critical path, watch what changes, then decide whether the foundation needs deeper work.
Sometimes that evidence confirms a rebuild. More often, it reveals that a handful of product, design or positioning decisions were creating most of the friction.
The principle
Protect signal while you remove friction
Keep the behaviours customers already understand. Change one meaningful layer at a time. Define the outcome before the output. That is how you improve a live product without replacing certainty with a prettier form of guesswork.
