Apps, Software, and SaaS — Lesson 4
MVPs, Roadmaps, and Product Thinking
Learning Objectives
- 1Define an MVP as the smallest version that proves core value.
- 2Build a roadmap that separates launch requirements from future improvements.
- 3Avoid common scope creep patterns that delay launches.
What an MVP really is
A minimum viable product is the smallest version of a product that delivers the core value proposition to real users. It is not a prototype, a mockup, or a half-finished version. It is a complete but focused product that intentionally excludes lower-priority features to reach users faster and learn sooner.
The purpose of an MVP is risk reduction. Instead of spending six months and $100,000 building a full vision, you spend six weeks building the core, put it in front of real users, and learn whether the fundamental idea works before investing further. Most assumptions about what users want are wrong — the MVP is how you find out which ones.
A good MVP requires discipline. Every stakeholder will have features they consider essential. The MVP conversation forces a distinction between "must have for launch" and "important but can wait." Features that can wait should move to the roadmap, not delay the launch.
Roadmaps and phased delivery
A roadmap explains what comes next and why. It separates the product vision into phases, each tied to evidence — user feedback, usage data, revenue milestones, or operational needs. A useful roadmap is a planning tool, not a promise.
Phase 1 is the MVP — the core that proves the value. Phase 2 adds features based on what you learned from Phase 1 users. Phase 3 expands based on growth patterns. Each phase should have clear goals and criteria for deciding what to include.
Treat roadmaps as living documents. What seemed important before launch may be irrelevant after watching real users. The best roadmaps are updated monthly based on evidence, not locked in quarterly based on opinions.
Scope creep and how to manage it
Scope creep is the gradual expansion of project requirements during development. It usually sounds reasonable one request at a time: "Can we also add..." "What if users could..." "We should probably include..." Each addition seems small, but together they delay the launch, increase cost, and dilute focus.
Managing scope creep requires a written scope document that everyone agrees to, a clear process for evaluating new requests against the MVP definition, and the discipline to say "yes, but in Phase 2" rather than "yes, let us add that now."
The most expensive scope creep is the feature that nobody uses. Research consistently shows that a large percentage of software features are rarely or never used. Building fewer features that work well is almost always better than building many features that work adequately.
Case Study
The MVP that saved the business
Situation
A consulting firm planned to build a comprehensive project management platform with client portal, time tracking, invoicing, resource allocation, and reporting. The estimated build was $150,000 and eight months. Instead, they launched an MVP with just the client portal and document sharing for $25,000 in six weeks.
Analysis
The MVP revealed that clients primary need was not project management — it was easy document exchange and status visibility. The features the team assumed were essential (time tracking, resource allocation) were not valued by clients. The firm redirected their investment toward the features clients actually used.
Takeaway
The MVP did not just save money — it prevented investing heavily in features that would not have been used. Learning before building is the entire point.
Reflection Questions
- 1. If you had to launch a product in four weeks instead of four months, what would you keep and what would you cut?
- 2. Has your organization ever built a feature that turned out to be rarely used? What would have happened if you had tested the assumption first?
Key Takeaways
- ✓An MVP is the smallest complete product that tests the core value proposition.
- ✓Roadmaps separate vision into phases, each informed by evidence from the previous phase.
- ✓Scope creep delays launches — manage it with written scope and a clear change process.