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.
Sixteen playbooks for the people running experiments day to day. Each one is a standalone guide you can use this week.
Start with what you already know, not what you think. A step-by-step guide to grounding new ideas in evidence.
What a new joiner needs in their first month, and why most of it probably is not documented.
The six elements every brief needs. Most teams get one or two right and skip the rest.
Connecting experiments to what leadership cares about. Not retrospectively. Structurally.
Ninety minutes to turn a dumping ground into a pipeline. How to prune, reprioritise, and reconnect to objectives.
A quality gate that catches weak plans before they cost time. How to set one up without creating a bottleneck.
Governance survives only when it can refuse and when it gives value back. How to build both in from the start.
The three things a small team needs before anything scales. Deliberately small, so nobody can plead bureaucracy.
If success is defined after the results arrive, every test wins. How to register the call before the data exists.
A rejection is a decision, and decisions deserve records. Why the same idea keeps coming back, and how to stop it.
Claimed wins that never survive scrutiny are the quickest way to lose leadership trust. A protocol for checking.
What to do when the test loses. How to extract value and prevent the learning from being discarded.
The difference between findings and insights. Findings describe what happened. Insights drive what happens next.
Duplication is invisible, expensive, and more common than anyone admits. Here is how to prevent it.
A structure that shows impact, not activity. Results, decisions, learnings, and a clear ask.
Getting teams to learn from each other's experiments. Not a broadcast. A working session.
What the report should contain and why most of the data it needs probably requires manual reconstruction.
Building support with evidence, not enthusiasm. How to make the case that survives a budget conversation.
The resignation test. What your programme would lose if the key person left on Friday.
A structured diagnostic across five dimensions. Score honestly and see where the gaps are.
When the programme has lost momentum, where to start and what to fix first.