/epic-hypothesis

name: epic-hypothesis
description: Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.
intent: >-
  Frame epics as testable hypotheses using an if/then structure that articulates the action or solution, the target beneficiary, the expected outcome, and how you'll validate success. Use this to manage uncertainty in product development by making assumptions explicit, defining lightweight experiments ("tiny acts of discovery"), and establishing measurable success criteria before committing to full build-out.
type: component

Purpose

Frame epics as testable hypotheses using an if/then structure that articulates the action or solution, the target beneficiary, the expected outcome, and how you'll validate success. Use this to manage uncertainty in product development by making assumptions explicit, defining lightweight experiments ("tiny acts of discovery"), and establishing measurable success criteria before committing to full build-out.

This is not a requirements spec—it's a hypothesis you're testing, not a feature you're committed to shipping.

Key Concepts

The Epic Hypothesis Framework

Inspired by Tim Herbig's Lean UX hypothesis format, the structure is:

**If/Then Hypothesis:**

• **If we** [action or solution on behalf of target persona]
• **for** [target persona]
• **Then we will** [attain or achieve a desirable outcome or job-to-be-done]

**Tiny Acts of Discovery Experiments:**

• **We will test our assumption by:**
• [Experiment 1]
• [Experiment 2]
• [Add more as necessary]

**Validation Measures:**

• **We know our hypothesis is valid if within** [timeframe]
• **we observe:**
• [Quantitative measurable outcome]
• [Qualitative measurable outcome]
• [Add more as necessary]

Why This Structure Works

• **Hypothesis-driven:** Forces you to state what you believe (and could be wrong about)
• **Outcome-focused:** "Then we will" emphasizes user benefit, not feature output
• **Experiment-first:** Encourages lightweight validation before full build
• **Falsifiable:** Clear success criteria make it possible to kill bad ideas early
• **Risk management:** Treats epics as bets, not commitments

Anti-Patterns (What This Is NOT)

• **Not a feature spec:** "Build a dashboard with 5 charts" is a feature, not a hypothesis
• **Not a guaranteed commitment:** Hypotheses can (and should) be invalidated
• **Not output-focused:** "Ship feature X by Q2" misses the point—did it achieve the outcome?
• **Not experiment-free:** If you skip experiments and go straight to build, you're not testing a hypothesis

When to Use This

• Early-stage feature exploration (before committing to full roadmap)
• Validating product-market fit for new capabilities
• Prioritizing backlog (epics with validated hypotheses get higher priority)
• Managing stakeholder expectations (frame work as experiments, not promises)

When NOT to Use This

• For well-validated features (if you've already proven demand, skip straight to user stories)
• For trivial features (don't over-engineer small tweaks)
• When experiments aren't feasible (rare, but sometimes you must commit before testing)

---

Application

Use `template.md` for the full fill-in structure.

Step 1: Gather Context

Before drafting an epic hypothesis, ensure you have:

• **Problem understanding:** What user problem does this address? (reference `skills/problem-statement/SKILL.md`)
• **Target persona:** Who benefits? (reference `skills/proto-persona/SKILL.md`)
• **Jobs-to-be-Done:** What outcome are they trying to achieve? (reference `skills/jobs-to-be-done/SKILL.md`)
• **Current alternatives:** What do users do today? (competitors, workarounds, doing nothing)

**If missing context:** Run discovery interviews or problem validation work first.

---

Step 2: Draft the If/Then Hypothesis

Fill in the template:

### If/Then Hypothesis

**If we** [action or solution on behalf of the target persona]
**for** [target persona]
**Then we will** [attain or achieve a desirable outcome or job-to-be-done for the persona]

**Quality checks:**

• **"If we" is specific:** Not "improve the product" but "add one-click Slack notifications when tasks are assigned"
• **"For" is a clear persona:** Not "users" but "remote project managers juggling 3+ distributed teams" (reference `skills/proto-persona/SKILL.md`)
• **"Then we will" is an outcome:** Not "users will have notifications" but "users will respond to task assignments 50% faster"

**Examples:**

• ✅ "If we add one-click Google Calendar integration for trial users, then we will increase activation rates by 20% within 30 days"
• ✅ "If we provide bulk delete functionality for power users managing 1000+ items, then we will reduce time spent on cleanup tasks by 70%"
• ❌ "If we build a dashboard, then users will use it" (vague, not measurable)

---

Step 3: Design Tiny Acts of Discovery Experiments

Before building the full epic, define lightweight experiments to test the hypothesis:

### Tiny Acts of Discovery Experiments

**We will test our assumption by:**
- [Experiment 1: low-cost, fast test]
- [Experiment 2: another low-cost, fast test]
- [Add more as necessary]

**Experiment types:**

• **Prototype + user testing:** Fake the feature with a clickable prototype, test with 5-10 users
• **Concierge test:** Manually perform the feature for a few users, see if they value it
• **Landing page test:** Describe the feature, measure sign-ups or interest
• **Wizard of Oz test:** Present the feature as if it's automated, but do it manually behind the scenes
• **A/B test (if feasible):** Test a lightweight version vs. control

**Quality checks:**

• **Fast:** Experiments should take days/weeks, not months
• **Cheap:** Avoid full engineering builds—use prototypes, manual processes, or existing tools
• **Falsifiable:** Design experiments that could