Knowledge
Knowledge HubConcepts and strategic researchGlossaryDefinitions across six domainsFrameworksStructured strategy methodsTopicsConnected subject areasLibrary
PlaybooksPractical strategy guidesBooksBooks and long-form researchOperator VaultMember resources and toolkits
Explore Discover, the Knowledge Hub, playbooks, and the Operator Vault.
Glossary
Minimum viable product
A minimum viable product (MVP) is an early version of a product with just enough capability to begin validated learning about customers and the business model — reducing the cost of testing critical hypotheses without pretending the MVP is the finished product.
Why it matters
Teams overbuild when they treat the first release as a miniature final product. An MVP is a learning vehicle: it should expose the riskiest assumptions to real use or purchase behavior.
Distinguish MVP from prototype and proof of concept. A prototype often explores design or technical feasibility with limited market exposure. A proof of concept (PoC) typically tests whether a technical approach can work. An MVP is aimed at learning about customer value and business-model viability with a shippable-enough experience. Eric Ries’s Lean Startup framing is the common anchor; it is not a license to ship careless quality under the MVP label.
Example (enterprise): A bank tests a new expense-assistant with one workflow, clear human escalation, and instrumentation on completion and trust — not a full finance suite. The MVP answers whether employees use it weekly; architecture breadth waits on that learning.
Mechanisms
- Identify the critical hypothesis the MVP must test (value, usability, willingness to pay, or workflow fit).
- Include only the capability required to run that test with real users or buyers.
- Instrument outcomes and decide to persevere, pivot, or stop — rather than expanding scope by default.
Boundaries
- MVP ≠ prototype; prototypes often prioritize design/tech exploration over market learning.
- MVP ≠ proof of concept; PoCs primarily test technical feasibility.
- MVP ≠ “ship junk”; viability includes enough quality for the learning goal to be valid.
- Calling every beta an MVP does not create validated learning.
Related topics
None linked yet.
Related concepts & frameworks
Related Discover collections
Further research
No related resources yet.