The MVP
Scope Reduction.
1. The Executive Summary
The MVP Scope Reduction Protocol is a constraint-based framework designed to prevent "Validation Debt"—the accumulation of features that have not been proven necessary by paying customers.
The Philosophy: Code is not an asset; code is a liability. Every line of code you write must be maintained, debugged, and explained. Therefore, the goal of the MVP is not to build a "small version" of the final product, but to build the simplest mechanism required to deliver the core value.
Strategy: The Dump → The Purge → The Override → The Time-Box.
2. The Outcome
By the end of this planning session, you will possess:
- A "V1" roadmap 80% smaller than original.
- Clear distinction between Core vs. Vanity.
- A strict 14-day build schedule.
- Total elimination of "Nice-to-Haves".
3. The Prerequisites
Required Mindset Shift
You are not building software. You are building a solution. If you can solve the user's problem using a spreadsheet and an email, that is the MVP.
The "Anti-Stack" (Tools to Avoid)
- No KubernetesYou do not need scale yet.
- No Custom AuthUse off-the-shelf (Clerk/Firebase).
- No "Settings" PageHard-code everything.
4. The Algorithm
The Brain Dump
Goal: Clear your mental RAM.
Open a blank document. List every single feature, button, page, and integration you have imagined. Do not filter yet.
Result: 30–50 items. This is your "Backlog of Death."
The "Painkiller" Filter
Goal: Brutal elimination. Categorize every item into three buckets.
Keep (Max 3)
Without this, the product literally cannot solve the Bleeding Neck Problem.
Delete / V2
Makes it "better" or "easier." (e.g., Search history, Dark mode).
Delete Immediately
Makes YOU feel cool but adds zero utility. (e.g., Animations, Gamification).
The Manual Override
Goal: Replace code with labor. (Concierge MVP)
Do not automate a process until you have done it manually 10 times.
Build AI matching engine.
Create Typeform. Read answers. Intro via email.
Automated PDF generation.
Screenshot the data. Email it manually.
The 14-Day Time Box
Goal: Enforce scarcity. Work expands to fill the time available.
The Contract
- You have exactly 14 days from today to ship V1.
- If a feature takes 3 days but you have 2 days left, cut it.
- Done Definition: User can sign up/pay, receives core value, no crashes.
5. The Decision Matrix
| Feature Type | Example | Action |
|---|---|---|
| Core Value | "Generate Lead List" | Build (P1) |
| User Admin | "Forgot Password" | Manual Support |
| Trust Signals | "User Reviews" | Hard-code HTML |
| Growth Loops | "Referral Program" | Cut (Month 3) |
6. The Failure Points
Competitor Parity Trap
"Competitor X has a mobile app." They have been building for 5 years. You are Day 1. Don't compete on features.
The Embarrassment Factor
"It looks ugly." If you aren't embarrassed by V1, you launched too late. (Reid Hoffman)
Future-Proofing
Optimizing DB for 1 million users when you have zero. If you crash at 1M, that's a good problem.