An MVP should let a real customer complete one valuable job and give you evidence about the hardest assumption in the business.
Work through it
Write the outcome
Describe what changes for the customer after using the first version.
Map the critical path
List only the steps required to reach that outcome.
Remove hidden ambition
Cut scale, automation, customization, and edge cases that the first test does not require.
Define the learning
State what user behavior will make you continue, change, or stop.
Common mistakes
- Calling a broken demo an MVP
- Building infrastructure for imaginary scale
- Treating every request as required