Product Task
Define a usable MVP boundary
The proposed first release exceeds the team’s capacity, yet removing more work could leave the core user path incomplete.
“This is costing me delivery time while the first release remains too broad or too incomplete to use.”
Outcome
The result to aim for
Set a reviewable boundary around one complete use case and state every material exclusion and consequence.
Best practices
- Bring the chosen audience, the evidenced problem, current solution outline, team capacity, and known non-negotiable obligations.
- Write the user’s starting state, each essential action, the successful finish, and the evidence for why this path matters; then mark every optional branch separately.
- List each omitted capability, the affected user or scenario, the consequence, and the revisit trigger; then ask delivery specialists to confirm that the remaining path is coherent.
- Confirm that a target user can complete the named path inside the boundary.
- Escalate unresolved legal, safety, accessibility, or operational obligations.
Related sources
Further information
- Documented guidance: Hacker News: Ask HN: Can you build an MVP in one week?
- Related guidance: Basecamp: Set Boundaries
- Related guidance: GOV.UK Service Manual: How the alpha phase works