The MVP Scope Cut List
Checklist
A working checklist for cutting scope back to what actually needs testing first.
Assumption
- What's the one assumption this version needs to test?
- Does every remaining feature serve that assumption?
- What's in the plan just because it seemed obvious to include?
Necessity
- What would break if this feature were removed entirely?
- Could this be done manually instead of built?
- Is this needed for the test, or just for the ambition?
Cost
- What does this feature cost in time, complexity and risk?
- Is that cost proportional to what it teaches us?
- What else could that time buy instead?
Cut
- What's the first thing you'd cut under time pressure?
- Why hasn't it been cut already?
- What would you need to see to add it back later?
Start a conversation
Have a product or AI decision to make?
Useful first calls usually start with one unclear decision, a deadline and a team that needs a practical next move.
Tell us about it