validation-frameworks

# Validation Frameworks

Frameworks for validating problems, solutions, and product assumptions before committing to full development.

## When to Use This Skill

**Auto-loaded by agents**:
- `research-ops` - For problem/solution validation and assumption testing

**Use when you need**:
- Validating product ideas before building
- Testing assumptions and hypotheses
- De-risking product decisions
- Running MVP experiments
- Validating problem-solution fit
- Testing willingness to pay
- Evaluating technical feasibility

## Core Principle: Reduce Risk Through Learning

Building the wrong thing is expensive. Validation reduces risk by answering critical questions before major investment:

- **Problem validation**: Is this a real problem worth solving?
- **Solution validation**: Does our solution actually solve the problem?
- **Market validation**: Will people pay for this?
- **Usability validation**: Can people use it?
- **Technical validation**: Can we build it?

## The Validation Spectrum

Validation isn't binary (validated vs. not validated). It's a spectrum of confidence:

```
Wild Guess → Hypothesis → Validated Hypothesis → High Confidence → Proven
```

Early stage: Cheap, fast tests (low confidence gain)
Later stage: More expensive tests (high confidence gain)

**Example progression**:
1. **Assumption**: "Busy parents struggle to plan healthy meals"
2. **Interview 5 parents** → Some validation (small sample)
3. **Survey 100 parents** → More validation (larger sample)
4. **Prototype test with 20 parents** → Strong validation (behavior observed)
5. **Launch MVP, track engagement** → Very strong validation (real usage)
6. **Measure retention after 3 months** → Proven (sustained behavior)

## Problem Validation vs. Solution Validation

### Problem Validation

**Question**: "Is this a problem worth solving?"

**Goal**: Confirm that:
- The problem exists
- It's painful enough that people want it solved
- It's common enough to matter
- Current solutions are inadequate

*