An MVP is the start of the journey, not the end. The question after it is: what next, and in what order? A phased roadmap answers that without trapping you in a plan that reality will rewrite. Here is how to build one.
The short answer
Phase your roadmap as: MVP (prove the core value with the minimum), then a learning phase (improve based on real users), then v1 (the solid, fuller product for your main audience). Plan the near phases in detail and the far ones only in broad themes.
Phase 1: MVP
The smallest thing that delivers the core value and produces learning (see what belongs in your MVP). Its job is not to be complete; it is to validate and teach.
Phase 2: Learn and refine
Real users will surprise you. This phase is about acting on what the MVP taught: fixing what is broken, doubling down on what works, and cutting what nobody used. Resist piling on new features before you have digested the MVP's lessons.
Phase 3: v1
The version that is solid, complete, and polished enough to stand as your real product for your core audience. Crucially, v1's shape is decided by MVP learning, not by your original guesses, which is exactly why you should not over-plan it in advance.
How to phase well
- Detail decreases with distance. MVP in detail, phase two in rough shape, v1 in themes.
- Each phase has a goal. Validate, learn, then solidify, not just "more features."
- Let learning drive sequencing. Reorder later phases as real usage teaches you.
- Keep a "someday" bucket. Ideas that are not in any planned phase yet, parked, not lost.
The foundation that makes phasing easy
Phasing works best when each phase builds on a solid base rather than a patchwork. Starting the MVP from a documented, runnable foundation, a product simulation, means later phases extend a clean, well-architected core instead of fighting early shortcuts, so the path from MVP to v1 is smooth instead of a series of rebuilds.
Ready to lay phase one's foundation? Start a project.
Frequently asked
How far ahead should I plan?
Plan the MVP in detail, the next phase in rough shape, and beyond that only in themes. You will learn things from real users that reshape later phases, so detailed long-range plans are mostly wasted effort.
When is it 'v1' rather than still an MVP?
Loosely, the MVP proves the core value with the minimum; v1 is the version solid and complete enough to stand as your real product for your main audience. v1 is shaped by what the MVP taught you.