To scope an MVP, define the problem and the specific user, identify the single core action that delivers value, list the assumptions that must be true, build only what is needed for users to complete that action and test those assumptions, write down what you will not build, and decide in advance how you will measure the result.
The steps
- Write the problem in the user's own words.
- Choose one specific user group to serve first.
- Define the core action: the one thing users must be able to do.
- List critical assumptions and rank them by risk.
- Define the minimum features needed for the core action.
- Write the no-build list: features deliberately excluded.
- Define measures of success and failure.
- Plan how you will reach the first users.
- Set the date for the build, reshape or stop decision.
Example
Idea: a platform for small hauliers to find loads. Core action: a haulier finds and accepts a suitable load. Riskiest assumption: shippers will post loads on a new platform. MVP: shippers post loads through a simple form, hauliers browse and accept, payment is invoiced manually. Not built yet: in-app payments, ratings, route optimisation, mobile app.
Limitations and considerations
- An MVP can disprove an idea; be ready to accept that result.
- Small scope is not an excuse for insecure or unreliable software.