01Name the uncertainty
If you do not know whether customers value the outcome, invest in learning before broad engineering. A prototype or manual pilot may answer the question before you need production software.
02Choose a complete user journey
An MVP should be small, but still useful. Select one audience and one outcome. Include the security, accessibility, and reliability needed for that context. “Minimum” does not justify unsafe handling of user data.
03Define a learning checkpoint
Write down the evidence that would lead you to continue, change direction, or stop. Review actual usage and customer feedback before adding the next group of capabilities.
04Know when a broader release is necessary
Regulated workflows, contractual integrations, migration requirements, and replacement of business-critical tools can require a more complete first release. Document these constraints before estimating.
Editorial approach
This guide offers practical planning questions. It is not a guarantee of delivery outcomes. Adapt the checklist to your project and validate assumptions with the proposed team.
Further reading: GOV.UK Service Manual — related delivery guidance