For Practitioners
Sixteen playbooks for the people running experiments day to day. Each one is a standalone guide you can use this week.
How to Run an Evidence-Based Brainstorming Workshop
Start with what you already know, not what you think. A step-by-step guide to grounding new ideas in evidence.
ReadHow to Onboard a New Person to Your Experimentation Programme
What a new joiner needs in their first month, and why most of it probably is not documented.
ReadHow to Write an Experiment Brief That Actually Gets Approved
The six elements every brief needs. Most teams get one or two right and skip the rest.
ReadHow to Set Quarterly Experimentation Objectives That Connect to Business Strategy
Connecting experiments to what leadership cares about. Not retrospectively. Structurally.
ReadHow to Run a Backlog Grooming Session
Ninety minutes to turn a dumping ground into a pipeline. How to prune, reprioritise, and reconnect to objectives.
ReadHow to Run an Experiment Review Board
A quality gate that catches weak plans before they cost time. How to set one up without creating a bottleneck.
ReadHow to Design a Governance Framework People Do Not Route Around
Governance survives only when it can refuse and when it gives value back. How to build both in from the start.
ReadMinimum Viable Governance
The three things a small team needs before anything scales. Deliberately small, so nobody can plead bureaucracy.
ReadHow to Define Success Before the Test Runs
If success is defined after the results arrive, every test wins. How to register the call before the data exists.
ReadHow to Reject an Idea Properly
A rejection is a decision, and decisions deserve records. Why the same idea keeps coming back, and how to stop it.
ReadHow to Verify a Win After Implementation
Claimed wins that never survive scrutiny are the quickest way to lose leadership trust. A protocol for checking.
ReadHow to Handle a Negative or Inconclusive Result
What to do when the test loses. How to extract value and prevent the learning from being discarded.
ReadHow to Write Insights That Inspire Action
The difference between findings and insights. Findings describe what happened. Insights drive what happens next.
ReadHow to Avoid Running the Same Experiment Twice
Duplication is invisible, expensive, and more common than anyone admits. Here is how to prevent it.
ReadHow to Present Experiment Results to Leadership
A structure that shows impact, not activity. Results, decisions, learnings, and a clear ask.
ReadHow to Run a Cross-Team Learning Share
Getting teams to learn from each other's experiments. Not a broadcast. A working session.
ReadHow to Build a Quarterly Experimentation Report for Executives
What the report should contain and why most of the data it needs probably requires manual reconstruction.
ReadHow to Get Stakeholder Buy-In for Your Experimentation Programme
Building support with evidence, not enthusiasm. How to make the case that survives a budget conversation.
ReadHow to Hand Over an Experimentation Programme When Someone Leaves
The resignation test. What your programme would lose if the key person left on Friday.
ReadHow to Run a Programme Health Check
A structured diagnostic across five dimensions. Score honestly and see where the gaps are.
ReadHow to Recover a Stalled Experimentation Programme
When the programme has lost momentum, where to start and what to fix first.
Read