The Validation Playbook

Stage 4: Assess

Turn commitment into repeat use. Test the MVP, measure fit signals, and decide what to fix next.

Stage 4 of 54 min read

The promise of this stage

By the end of Stage 4, you will have an MVP test result with a clear pass/fail, a PMF signal score with a loop sketch, and a focused iteration path (improve, pivot, or stop). If you cannot get repeat use, you likely do not have fit yet.

Stage 3 tested whether people will commit. Stage 4 tests whether they come back. This is where early fit appears. A loop is the trigger-action-return pattern that brings people back. If the loop is weak, everything breaks here.

What You Will Build

Experiment Card + MVP Results

Pass/fail against a clear line

PMF Signal Checklist + Loop Sketch

Repeat use, time-to-value, retention

Iteration Decision Note

Next change + pass line

These are the proof points that justify the commitment decision in Stage 5.

The Three Modules

Each module narrows the signal. If Module 1 is weak, Module 2 is noise. If Module 2 is unclear, Module 3 is guesswork. Do them in order.

1MVP SprintRun the smallest test that proves demand. Test with the smallest possible build.Start →2Fit SignalsCheck if people come back and use it again. Measure repeat use and early retention.Start →3Fit FixesFix what blocks fit, not what is shiny. Choose one change and test it, not five.Start →

Stage Rules

Keep it honest

  • A test is not a product. Smallest proof beats biggest build.
  • Repeat use beats signups. Behavior beats buzz.
  • Change one variable at a time. Otherwise you learn nothing.
  • If the loop is weak, fix the blocker, not the distracting feature.

The goal is not growth. The goal is repeatable proof.

Quick Reference

Evidence Standard

1. A pass/fail MVP result against a clear line

2. Repeat use within the natural problem cycle

3. A loop you can explain in one sentence

No signals? Pause and fix the gap.

Pace

1. One MVP test in the next two weeks

2. One PMF signal checklist from real usage

3. One focused iteration test with a pass line

Learn fast, not ship perfect.

Common traps

  • Building too much before a pass line
  • Celebrating signups instead of repeat use
  • Changing three things at once
  • Ignoring churn because a few users are loud
  • Fixing symptoms instead of the loop

What to ignore for now

Full product buildouts, scaling acquisition, hiring growth teams, vanity dashboards. Those depend on fit signals you do not have yet.

What Success Feels Like

By the end of this stage, you should be able to say:

"This test passed"

"This loop exists"

"This is the next fix"

Stage 4 is your filter. It protects you from scaling a weak loop.

Repeat use is the compass.

Begin Module 1: MVP Sprint

Sign in