Validation Sprints
On this page
Definition. A validation sprint is a time-boxed, evidence-disciplined way to de-risk one behavior bet: confirm the problem, validate the behavior is feasible in real context, then test whether a minimal solution enables it.
- Problem Market Fit: active solution seeking 40-80 percent depending on domain and segment.
- Behavior Market Fit: observed completion of the target behavior in realistic context 50-75 percent.
- Solution Market Fit: time to first instance of the target behavior under 5 minutes consumer, under 15 minutes enterprise pilot.
- Product Market Fit: 90-day retention of the target behavior, S-curve adoption pattern, domain-specific thresholds.
Objective: De-risk one target behavior and its enabling solution in 10 working days.
Cadence and Deliverables
Day 1-2: Problem & Behavior Re-validation
- Re-compute PMF from latest inputs
- Observe in-context attempts to confirm the behavior is feasible in the contexts that matter (BMF)
- Ethics and privacy check: consent language, data retention, anonymization plan
Day 3: Behavior Path Sketch
- Diagram the exact steps and context for the behavior
- Identify weakest step and hypothesize barriers
Day 4-5: Prototype to Enable Behavior
- Build the lightest prototype that removes the weakest barrier
- Pre-define SMF metrics and analytics
Day 6-8: Field Test
- Starting point: n ≥ 30 users, or ≥ 15 for enterprise pilots. Calibrate the sample to the behavior’s frequency and to the smallest effect that would change the decision.
- Measure: Behavior Completion Rate, Time to First Behavior, Repeat Within 7 Days
Day 9: KPI Plan + Cohort Setup
- Define bPMF targets and cohort instrumentation
Day 10: Decision Memo
- Go if Solution Market Fit criteria are met and qualitative failure modes are solvable
- No-Go or Iterate if validation signals are weak (calibrate thresholds by domain)
Artifacts: behavior path sketch, KPI plan, decision memo, raw observation notes.
Frequently asked questions
What is a validation sprint?
A time-boxed (default: 10 working days) process to de-risk one behavior bet: confirm the problem, validate the behavior is feasible in real context, then test whether a minimal solution enables it.
Why 10 days?
It is a practical default: long enough to observe real attempts and run a small field test, short enough to avoid building on unvalidated assumptions. Calibrate by domain constraints.
How many users do we need?
Aim for a clear denominator and the smallest sample that can falsify the plan. Treat n≥30 as a starting point, not a benchmark. Enterprise pilots can use fewer users when the behavior is high-frequency and measurement is clean.
What are the go/no-go criteria?
Pre-register Solution Market Fit criteria (e.g., completion, TTFB, repeat-within-window) and decide from the data. If Behavior Market Fit fails, do not compensate with design work; change the behavior or the population/context constraints.
How does this relate to DRIVE?
It is a compressed DRIVE cycle focused on early gates: Define + Research (PMF/BMF), Integrate (prototype enablement), Verify (field test), and a decision memo that feeds Enhance.
Licensing
Content © Jason Hreha. Text licensed under CC BY-NC-SA 4.0 unless a more specific asset notice applies. Framework names may be used accurately without implying endorsement.