Framework: Problem Validation -> RICE Scoring (Reach, Impact, Confidence, Effort) -> MoSCoW Method -> Fast Feedback Loops.
1. Define the Core Value Hypothesis:
- What is the single, non-negotiable problem this product must solve better than existing alternatives? Everything else is secondary.
2. RICE Evaluation:
- Score potential features on Reach (users impacted), Impact (lift to core metric), Confidence (data backing the estimate), and Effort (engineering weeks required).
3. MoSCoW Categorization:
- Must-Haves: The essential happy path and security fundamentals (e.g., auth, core workflow, payment capture). Without these, the product cannot launch.
- Should-Haves: Important convenience features (e.g., email receipts, password resets) that can use manual workarounds for initial beta users if needed.
- Could-Haves: Delight features (custom themes, dark mode) deferred to Post-MVP.
- Won't-Haves: Complex integrations that can be replaced by third-party tools.
4. Validation Cadence:
- Ship a functional slice to a private cohort of 20 pilot users within four weeks to validate retention before building secondary features.