The core idea
An analytics project is only as good as the decision it enables. The final skill is translating a model into a recommendation a non-technical stakeholder can act on — emphasising the decision, the uncertainty, and the cost of being wrong. A model that is statistically significant but makes a £2 difference per transaction is a fascinating curiosity, not a £10M rollout. — after decades of dashboards nobody used
The hero diagram
The analytics maturity ladder.
Each rung requires the one below it.
The tools on the bench
Ideas that pay rent.
How to apply
Writing the one-page executive memo.
- Lead with the decision. Not the method. The decision.
- State the uncertainty in business units. "We are 95% confident profit is between £1.2M and £1.8M" — not t-statistics.
- Name the cost of being wrong. If the CI straddles breakeven, say so. Recommend a pilot, not a rollout.
- Leave equations in the appendix. The CFO is not impressed by your R².
Key reading · Session 5 · Christodoulou
From data to decisions.
Most analytics projects die in the hand-off. The best regression is worthless if it confuses the decision-maker. Simplicity, business context and honest communication of uncertainty are not optional — they are the whole deliverable.
What should we do? Always answer the question being asked.