Hypothesis-Driven Planning Template

---
title: "Hypothesis-Driven Planning Template"
methodology: "universal"
complexity: "advanced"
owner: "mirichard"
updated: "2026-10-08"
domain: "Uncertainty"
primary_principles: ["risk-optimization", "evidence-based-decisions"]
secondary_principles: ["adaptability", "systems-thinking"]
principle_rationale: "Prioritizes uncertain assumptions for evidence-led testing so strategy can adapt while managing cross-model risk exposure."
tags: ["lean-startup", "hypothesis-driven", "assumptions", "risk-management"]
---

# Hypothesis-Driven Planning Template

## Overview
Hypothesis-driven planning transforms assumptions into testable hypotheses that can be validated or invalidated through experiments. This approach reduces risk by testing the riskiest assumptions first.



## When to Use
- Use during early planning when teams need to convert assumptions into testable hypotheses with explicit validation criteria.
- Apply before funding, roadmap, or staffing commitments when uncertainty is high and learning order matters.
- Run this approach when decision-makers require a transparent registry of hypotheses, status, and risk-weighted priority.

## When NOT to Use
- Do not use as a documentation ritual where hypotheses are written but never linked to actual validation experiments.
- Do not assume template completion equals sound judgment without contextual adaptation and accountable decisions (see [Template as substitute for judgment](../../../docs/principles/anti-patterns.md#template-judgment)).
- Do not keep invalidated hypotheses active in planning artifacts without explicit rationale and replanning.

## Pairs Well With
- [Experiment Design Template](experiment-design-template.md)
- [Lean Canvas Template](lean-canvas-template.md)

Decision context model reference: 800-801-context-assessment-model.md
## Hypothesis Framework

### Hypothesis Structure
```
We believe that [customer segment] has [problem/need] 
and will [desired behavior] when we provide [solution] 
because [underlying assumption].

We will know this is true when we see [measurable outcome] 
within [time period] with [success criteria].
```

### Example Hypothesis
```
We believe that busy working parents have difficulty finding healthy meal options for their families 
and will subscribe to a meal planning service when we provide personalized, quick recipes 
because they value their time but want to maintain healthy eating habits.

We will know this is true when we see 25% of surveyed parents sign up for our beta service 
within 2 weeks with at least 70% completing their first meal plan.
```

## Hypothesis Categories

### 1. Customer Problem Hypotheses
**Focus**: Validating that the problem exists and is significant

#### Template
```
Customer Problem Hypothesis #[X]:
We believe [customer segment] experiences [specific problem] 
and this problem causes [impact/frustration] 
because [underlying cause].

Validation Method: [How will you test this?]
Success Criteria: [What would prove this true?]
Timeline: [When will you test this?]
Risk Level: [High/Medium/Low]
```

#### Examples
- "We believe small business owners struggle with social media content creation and this causes missed marketing opportunities because they lack time and expertise."
- "We believe college students have difficulty managing their finances and this causes stress and poor financial decisions because they lack financial education and tools."

### 2. Customer Solution Hypotheses
**Focus**: Validating that your solution addresses the problem effectively

#### Template
```
Customer Solution Hypothesis #[X]:
We believe [customer segment] will adopt [solution approach] 
to solve [problem] and will prefer it over [current alternatives] 
because [unique value proposition].

Validation Method: [How will you test this?]
Success Criteria: [What would prove this true?]
Timeline: [When will you test this?]
Risk Level: [High/Medium/Low]
```

### 3. Customer Acquisition Hypotheses
**Focus**: Validating how customers will discover and try your solution

#### Template
```
Customer Acquisition Hypothesis #[X]:
We believe [customer segment] will discover our solution through [channel] 
and will engage with [marketing message/approach] 
because [motivation/trigger].

Validation Method: [How will you test this?]
Success Criteria: [What would prove this true?]
Timeline: [When will you test this?]
Risk Level: [High/Medium/Low]
```

### 4. Revenue Model Hypotheses
**Focus**: Validating how you'll make money and pricing

#### Template
```
Revenue Model Hypothesis #[X]:
We believe [customer segment] will pay [price] for [solution] 
via [payment model] and will find this price [acceptable/valuable] 
because [value justification].

Validation Method: [How will you test this?]
Success Criteria: [What would prove this true?]
Timeline: [When will you test this?]
Risk Level: [High/Medium/Low]
```

### 5. Growth Hypotheses
**Focus**: Validating how your business will scale

#### Template
```
Growth Hypothesis #[X]:
We believe customers will [growth mechanism] our solution 
at a rate of [frequency/volume] 
because [motivation for sharing/expanding].

Validation Method: [How will you test this?]
Success Criteria: [What would prove this true?]
Timeline: [When will you test this?]
Risk Level: [High/Medium/Low]
```

## Hypothesis Registry

### Active Hypotheses Tracking

| ID | Category | Hypothesis | Validation Method | Success Criteria | Status | Results |
|----|----------|------------|-------------------|------------------|---------|---------|
| H1 | Problem | [Brief description] | [Method] | [Criteria] | Testing | [Outcome] |
| H2 | Solution | [Brief description] | [Method] | [Criteria] | Validated | [Outcome] |
| H3 | Acquisition | [Brief description] | [Method] | [Criteria] | Invalidated | [Outcome] |

### Hypothesis Status Definitions
- **Draft**: Hypothesis identified but not yet formulated
- **Testing**: Experiment in progress
- **Validated**: Evidence supports the hypothesis
- **Invalidated**: Evidence contradicts the hypothesis
- **Needs More Data**: Results inconclusive, requires additional testing

## Experiment Design for Hypotheses

### Experiment Planning Template
```
Hypothesis ID: H[X]
Experiment Name: [Descriptive name]
Objective: [What you're trying to learn]

Experiment Design:
- Method: [Survey/Interview/A/B Test/Landing Page/etc.]
- Duration: [How long will the experiment run?]
- Sample Size: [How many participants needed?]
- Resources Required: [Time, money, people]

Measurements:
- Primary Metric: [Main success indicator]
- Secondary Metrics: [Additional indicators]
- Data Collection Method: [How will you measure?]

Success Criteria:
- Validated if: [Specific conditions for validation]
- Invalidated if: [Specific conditions for invalidation]
- Inconclusive if: [What would require more testing?]
```

### Common Experiment Types

#### 1. Problem Validation Experiments
- **Customer Interviews**: 15-30 interviews with target customers
- **Survey Research**: 100+ responses from target segment
- **Observation Studies**: Watch customers in their natural environment
- **Jobs-to-be-Done Analysis**: Understand underlying motivations

#### 2. Solution Validation Experiments
- **Prototype Testing**: Interactive mockups or demos
- **Concierge MVP**: Manually deliver the service
- **Wizard of Oz**: Fake automation with manual backend
- **A/B Testing**: Compare different solution approaches

#### 3. Acquisition Validation Experiments
- **Landing Page Tests**: Measure interest and conversion
- **Social Media Campaigns**: Test messaging and channels
- **Content Marketing**: Track engagement and leads
- **Partnership Pilots**: Test channel effectiveness

#### 4. Pricing Validation Experiments
- **Van Westendorp Analysis**: Price sensitivity research
- **Conjoint Analysis**: Feature vs. price trade-offs
- **Pre-order Campaigns**: Test willingness to pay
- **A/B Price Testing**: Compare different price points

## Hypothesis Prioritization

### Risk Assessment Framework
Rate each hypothesis on two dimensions:

#### Impact if Wrong (1-5)
1. Minor setback
2. Moderate resource waste
3. Significant pivot required
4. Major strategy change
5. Business failure

#### Confidence Level (1-5)
1. Wild guess
2. Some evidence
3. Moderate evidence
4. Strong evidence
5. Nearly certain

### Prioritization Matrix
```
High Impact, Low Confidence = TEST FIRST (Highest Priority)
High Impact, High Confidence = Monitor
Low Impact, Low Confidence = TEST LATER (Lower Priority)
Low Impact, High Confidence = Assume True
```

### Testing Sequence
1. **Critical Path Hypotheses**: Must be true for business to work
2. **High Risk/Low Confidence**: Could kill the business if wrong
3. **Customer Problem Validation**: Foundation for everything else
4. **Solution Validation**: Core product-market fit
5. **Business Model Validation**: Revenue and growth mechanisms

## Hypothesis Learning Loop

### 1. Formulate Hypothesis
- [ ] Use the structured hypothesis template
- [ ] Make it specific and measurable
- [ ] Identify the riskiest assumption
- [ ] Set clear success criteria

### 2. Design Experiment
- [ ] Choose appropriate validation method
- [ ] Define sample size and duration
- [ ] Set up measurement systems
- [ ] Plan resource allocation

### 3. Run Experiment
- [ ] Execute according to plan
- [ ] Collect data systematically
- [ ] Document observations
- [ ] Avoid confirmation bias

### 4. Analyze Results
- [ ] Compare results to success criteria
- [ ] Look for unexpected patterns
- [ ] Consider alternative explanations
- [ ] Document insights and surprises

### 5. Update Business Model
- [ ] Revise assumptions based on learning
- [ ] Update business model canvas
- [ ] Pivot if necessary
- [ ] Plan next experiments

## Common Hypothesis Planning Mistakes

### 1. Vague Hypotheses
❌ "Customers will like our product"
✅ "Busy professionals will use our meal planning app at least 3 times per week because it saves them 2+ hours of meal planning time"

### 2. Untestable Assumptions
❌ "We believe customers want better design"
✅ "We believe customers will choose our product over competitors when design is 20% more polished based on usability testing scores"

### 3. Testing Multiple Variables
❌ Testing price, features, and messaging simultaneously
✅ Testing one variable at a time to isolate cause and effect

### 4. Confirmation Bias
❌ Only looking for evidence that supports your hypothesis
✅ Actively seeking evidence that could disprove your hypothesis

### 5. Insufficient Sample Size
❌ Making decisions based on 3-5 customer conversations
✅ Using statistically significant sample sizes for quantitative tests

## Hypothesis Documentation Templates

### Hypothesis Validation Report
```
Hypothesis ID: H[X]
Date: [Completion date]
Status: [Validated/Invalidated/Inconclusive]

Original Hypothesis:
[Copy original hypothesis statement]

Experiment Summary:
- Method: [How it was tested]
- Duration: [Time period]
- Sample Size: [Number of participants]
- Response Rate: [If applicable]

Key Results:
- Primary Metric: [Result vs. target]
- Secondary Metrics: [Additional findings]
- Qualitative Insights: [Key observations]

Conclusion:
[Validated/Invalidated with reasoning]

Implications:
- Business Model Changes: [What needs to be updated]
- Next Hypotheses: [What to test next]
- Action Items: [Immediate next steps]

Supporting Evidence:
- Data: [Links to data/charts]
- Customer Quotes: [Relevant feedback]
- Other Observations: [Additional insights]
```

### Pivot Decision Framework
When a critical hypothesis is invalidated:

#### 1. Customer Segment Pivot
- Change target customer while keeping the problem and solution
- Example: B2B to B2C or different industry vertical

#### 2. Customer Problem Pivot
- Change the problem you're solving for the same customer segment
- Example: From productivity to communication tools

#### 3. Solution Approach Pivot
- Change how you solve the problem while keeping customer and problem
- Example: From mobile app to web platform

#### 4. Revenue Model Pivot
- Change how you make money while keeping customer, problem, and solution
- Example: From subscription to transaction-based pricing

#### 5. Channel Pivot
- Change how you reach customers
- Example: From direct sales to partner channel

## Success Metrics for Hypothesis-Driven Planning

### Process Metrics
- **Hypothesis Quality**: % of testable vs. vague hypotheses
- **Testing Velocity**: Number of hypotheses tested per month
- **Learning Rate**: Insights generated per experiment
- **Iteration Speed**: Time from hypothesis to validated learning

### Outcome Metrics
- **Validation Rate**: % of hypotheses that are validated
- **Pivot Success**: Business improvement after major pivots
- **Risk Reduction**: Decrease in business model risk over time
- **Product-Market Fit**: Customer satisfaction and retention improvements

---

*Remember: The goal is not to validate all your hypotheses, but to learn quickly and cheaply what works and what doesn't*
*Failed hypotheses are successful learning experiences if they inform better decisions*