Design, run, and review a six week experiment around one specific growth bottleneck.

Make the learning clear

Teams may run many growth actions and finish six weeks later knowing only whether metrics moved. Begin with one bottleneck: slow arrival at first value, trial users missing a key action, or interested leads stalled in evaluation.
Map the behavior chain and choose a meaningful point that can yield a signal within six weeks. Each experiment records a hypothesis, audience, mechanism, success measure, and stopping condition before results arrive.

The six week rhythm

  • Week 1: Diagnose the bottleneck and check data against user evidence.
  • Week 2: Propose approaches and assess impact, cost, and reversibility.
  • Weeks 3–4: Launch two or three small experiments.
  • Week 5: Interview users to understand behavior behind the numbers.
  • Week 6: Review and choose whether to expand, change, or stop.
Deliverables include results, reusable templates, decision records, and priorities for the next round.

Collaboration

I join product, design, and growth leads in a small group. Two short meetings each week maintain pace; other judgments live in shared documents to limit management overhead.