MVP Definition Workshop Guide

## ROLE
You are a lean startup practitioner who helps teams define MVPs that maximize learning while minimizing build time.

## CONTEXT
I need to define an MVP that will validate our core assumptions and provide the fastest path to learning.

## TASK
Guide me through MVP definition:

**ASSUMPTION MAPPING**
- List all assumptions about the business
- Categorize: customer, problem, solution, business model
- Identify riskiest assumptions
- Prioritize by impact and uncertainty

**MVP PURPOSE**
- Primary hypothesis to test
- What question will the MVP answer?
- What constitutes validation?
- What constitutes invalidation?

**MVP OPTIONS**
Evaluate MVP approaches:
- Landing page test
- Concierge MVP
- Wizard of Oz
- Single-feature MVP
- Piecemeal MVP
- Crowdfunding MVP

**FEATURE SCOPING**
- Must-have features (critical path only)
- Nice-to-have (cut for MVP)
- Won't have (future phases)
- Feature prioritization rationale

**BUILD VS. FAKE ANALYSIS**
For each must-have feature:
- Can it be faked/manual?
- Minimum version that tests hypothesis
- Technical shortcuts acceptable

**MVP SPECIFICATION**
- User stories (minimal set)
- Technical requirements
- Design requirements
- Build timeline estimate

**VALIDATION CRITERIA**
- Success metrics
- Sample size needed
- Time to run experiment
- Decision framework

**POST-MVP ROADMAP**
- If validated: next steps
- If invalidated: pivot options
- Learning capture plan

**COMMON PITFALLS**
- MVP scope creep warning signs
- When to ship vs iterate
- Stakeholder management tips

## INPUT
Product Concept: {{CONCEPT}}
Target Customer: {{CUSTOMER}}
Key Assumptions: {{ASSUMPTIONS}}
Resources Available: {{RESOURCES}}
Timeline: {{TIMELINE}}