Minimum Viable Product, MVP
Updated 2026-07-31
INTRODUCTION
English translation pending.
CORE DEFINITION
Popularized by Eric Ries in The Lean Startup, the minimum viable product is the least build that lets a team test its riskiest assumption with real users and then iterate through a build-measure-learn loop. Its purpose is validated learning before heavy investment, not a cheap version of the final product.
SCAFFOLDING EFFECT
Reduce cognitive load
- Anti-perfectionism: ship something testable before spending heavily on polish and scale. - Assumption testing: name the riskiest belief and build only what tests it. - Learning loop: treat each release as an experiment with a decision attached to the result it produces.
Anchor fast decisions
Uncertainty rather than engineering effort is the binding constraint early on. A minimal build shortens the time between hypothesis and evidence, so the team learns which assumptions hold while the cost of being wrong stays small enough to absorb and reverse.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- zh.wikipedia.orghttps://zh.wikipedia.org/wiki/%E6%9C%80%E7%B0%A1%E5%8F%AF%E8%A1%8C%E7%94%A2%E5%93%81verified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS