What should an MVP include?
A framework for choosing the users, workflows, evidence and technical foundations that belong in a first product release.
Direct answer
An MVP should include the smallest complete workflow that lets one target user achieve one valuable outcome and lets the team measure whether it worked. It should not include every expected role, automation or edge case, but it must still be reliable enough to earn real feedback.
The four parts of a useful MVP
- A specific target user
- One complete high-value workflow
- A measurable success signal
- A reliable technical and analytics baseline
Include now or later?
| Include in the MVP | Usually defer |
|---|---|
| Core onboarding | Several onboarding variants |
| Primary workflow | Secondary personas |
| Basic account controls | Advanced organisation admin |
| Essential notifications | Full automation suite |
| Core analytics | Executive reporting dashboards |
A prototype is not always an MVP
A clickable prototype can test comprehension and flow, but it cannot validate repeat use, operational cost or willingness to pay. Use a prototype for interface risk and a working MVP for behaviour and business risk.
The scope test
If removing a feature prevents the target user from completing the core outcome, it may belong in the MVP. If removing it only makes the product less convenient or less scalable, it can probably wait.