Build the smallest product that can create evidence
An MVP is not the cheapest version of a full roadmap. It is the smallest releasable product that lets a real user complete the core outcome and gives the team evidence for the next decision.
Step-by-step
- Define the user and painful situation.
- Record the current alternative.
- Identify the riskiest assumption.
- Choose one workflow that tests it.
- Set success and stop criteria.
- Write acceptance criteria and exclusions.
- Select a stack the team can operate.
- Build, test, and deploy.
- Launch to a limited group.
- Review usage, support, and failures before expanding.
What not to skip
Authentication, authorization, data protection, backups, monitoring, and operational ownership should match the risk of the product. “MVP” does not excuse unsafe handling of users or money.
Timeline and cost
Do not promise one duration or price for every MVP. A simple workflow with available designs and integrations may ship quickly. Regulated data, mobile releases, complex integrations, or unresolved product decisions take longer. Publish estimates only with assumptions and dependencies.
The goal is fast learning with a product that is safe enough for the intended users and context.
Fact-check sources
- NIST Secure Software Development Framework
- Editorial framework; no external benchmark asserted
Sources and product documentation can change. Recheck time-sensitive pages on the publication date.