Phase 2: Validate
Verify the problem is real and the solution is viable before investing in building.
Purpose
Avoid building something nobody wants. Validation answers:
- Is the problem real?
- Is it worth solving?
- Will the proposed solution work?
Activities
User Research
- User interviews (5-10 minimum)
- Surveys for quantitative data
- Observation of current workflows
Market Analysis
- Competitive landscape
- Market size estimation
- Differentiation opportunities
Feasibility Check
- Technical feasibility
- Resource requirements
- Timeline estimation
Outputs
| Output | Description |
|---|---|
| Research Findings | Summary of user interviews/surveys |
| Competitive Analysis | Comparison with existing solutions |
| Go/No-Go Decision | Clear decision to proceed or pivot |
Validation Framework
Score each dimension 1-5:
| Dimension | Score | Notes |
|---|---|---|
| Problem Severity | How painful is this problem? | |
| Market Size | How many people have this problem? | |
| Willingness to Pay | Would users pay/switch? | |
| Technical Feasibility | Can we build this? | |
| Competitive Advantage | Can we win? |
Total Score > 15: Strong proceed signal Total Score 10-15: Consider with caution Total Score < 10: Pivot or abandon
Exit Criteria
Ready to move to Design when:
- Conducted user research
- Analyzed competition
- Made explicit go/no-go decision
- Documented findings
Tips
- Listen more than talk in user interviews
- Look for patterns across users
- Be willing to kill bad ideas early
- Validation is cheap; building is expensive
Next Phase
Phase 3: Design - Define the user experience.