The misconception
A reduced roadmap is still a roadmap
Teams often scope an MVP by trimming every planned feature. The result is a smaller product that still tries to prove pricing, demand, usability and retention at the same time.
Focus comes from choosing the question the first version must answer. Everything else should support that proof or wait.
The diagnosis
Identify what must be true for the idea to work
Write down the assumption that would make the product irrelevant if it were false. It may be that users have the problem often enough, will change an existing habit or will trust a new way of completing the task.
A useful MVP turns that assumption into something observable.
- Name one target user
- Define one painful situation
- Choose one action that creates value
- Decide what evidence would change your mind
The scope
Build the shortest complete value loop
Give users enough to reach the intended outcome from start to finish. Remove settings, edge cases and secondary journeys that do not affect the test.
Once real behaviour answers the first question, the next version can respond to evidence instead of assumptions.
