Minimum Viable Product
A Minimum Viable Product (MVP) is the smallest complete product that tests the biggest value risk. Real users must be able to use it.
Another example
A team first helps people schedule by hand. It tests demand before automating every calendar edge case.
Main parts
- 01Core promise
- 02Included and excluded work
- 03Riskiest assumption to test
Use it when
Use it to learn at low cost while still giving users the main promised value.
Do not use it when
Never call a broken piece of a product an MVP. Small still needs to work as a whole.
Name used in code
MVP hypothesis Before you ship
Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision.
Outcome: Use Minimum Viable Product to make a focused product decision backed by evidence. User context: A team first helps people schedule by hand. It tests demand before automating every calendar edge case. Product concept to apply: Minimum Viable Product. Why it fits: Use it to learn at low cost while still giving users the main promised value. Do not use it when: Never call a broken piece of a product an MVP. Small still needs to work as a whole. Product framing: Name the target user and wanted result. Record the current baseline and evidence. Set what is in and out of scope, the limits, the owner, and the time frame. Decision quality: Keep facts, guesses, and unknowns separate. Record the options you did not choose and what evidence would change the decision. Acceptance criteria: The document names an owner, target user, measurable result, scope limit, evidence source, open risks, and next test. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Target group, baseline, success level, owner, time frame, dependencies, and review schedule.
Check this request
Review the current use of Minimum Viable Product. Definition: A Minimum Viable Product (MVP) is the smallest complete product that tests the biggest value risk. Real users must be able to use it. Release checks: Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.