Close every product experiment with a decision record
Every experiment records hypothesis, guardrails, result, confidence, segment limits, and the resulting decision.
The problem
Experiments end with a chart but no durable decision, limitation, or follow-up.
What you get
A working system with the steps, tools, checkpoints, and expected return made explicit.
- Setup
- 75 minutes
- Back each week
- 3 hours
- Difficulty
- assisted
Expected return
The working case
A planning estimate, not a guaranteed result. Measure the first four weeks against your own baseline.
144
hours returned per year
At 3 hours/week across 48 working weeks.
1
week to earn back setup
Compare the setup estimate with the weekly time returned.
Operating contract
Input
The source material, constraints, and examples a human would need to do this work well.
Checkpoint
A person reviews judgment calls, sensitive content, unfamiliar tools, and irreversible actions.
Success signal
Track time returned, corrections required, and exceptions. Keep it only if the measured result compounds.
Before you start
- ·A named product analytics lead
- ·An approved source-of-truth and review template
The steps
- 01
Name product analytics lead as the accountable owner and define the decision this workflow is allowed to support.
- 02
Collect experiment plan, exposure data, metric results, and analyst notes; preserve source links, timestamps, and access controls before any synthesis.
- 03
Produce a durable experiment decision record using the approved template. Do not call significance or causality beyond the approved analysis.
Copy this prompt
Create a durable experiment decision record from the supplied evidence. Separate facts, assumptions, and missing inputs. Cite every material claim. Do not call significance or causality beyond the approved analysis. Evidence: [approved inputs]
- 04
product analytics lead reviews the draft, records the decision or next action, and corrects the source system before distribution.
What it runs on
Where this goes wrong
- Do not let the model act beyond do not call significance or causality beyond the approved analysis.
- Keep sensitive fields out of unapproved tools and retain a human-readable evidence trail.
Definition of done
Run it for four weeks. Then make it earn its place.
- □ Baseline the manual time before launch.
- □ Keep a human approval step for consequential output.
- □ Record corrections and exceptions, not just successes.
- □ Expand, revise, or retire it after the first review.
Build the system around it
Related workflows
If this one stops working, tell us. Three reports in a month and it leaves the library until a person has looked at it again.