From weekly detail to a strategic story
Where the weekly review is operational and driver-level, the monthly leadership summit is strategic and narrative. It does not re-walk every branch - it rolls the month of weekly detail up into a story leadership can decide on: are we on plan, what moved and why, what we are doing about it, and what we need from the room above. This session closes the leader track by covering how to run that summit, how to govern your metrics so they stay honest, and where to go next once the whole system is running.
Roll the drivers up into a narrative 9 min live
The monthly summit takes a month of weekly driver trees and rolls them into one strategic narrative. The four questions leadership actually needs answered are simple: are we on plan, what moved and why, what are we doing about it, and what do we need from you? The weekly detail is the evidence; the monthly story is the argument. Narrative wins over dashboards here, because leadership decides on stories, not on two hundred tiles.
LiveThe four questions leadership needs answered3 min▶
A monthly summit is not a status meeting. Strip it down to the four questions leadership genuinely has to decide on, and answer them with the driver evidence the weekly cadence already produced.
- Are we on plan? - top line versus target, with the trailing trend, not a single dot.
- What moved and why? - the one or two drivers that explain the gap, named from the tree.
- What are we doing about it? - the actions already underway, each with an owner and a date.
- What do we need from you? - the decisions that require the room above to unblock.
Self-studyNarrative over dashboards, decisions over updates2 min read▶
Two failure modes kill a monthly summit. The first is the wall of dashboards - two hundred tiles, no story, leadership left to guess what matters. The second is the update parade - everyone reports that work happened, nobody asks for a decision. A good summit inverts both: a written narrative that argues a position, and an agenda built around the handful of decisions that actually need leadership. The dashboard is the appendix, not the meeting.
- Narrative over dashboards - a story leadership can decide on, with charts as evidence beneath it.
- Decisions over updates - the meeting exists to decide, not to inform; informing can be a pre-read.
- The tree stays underneath - every claim in the narrative traces to a driver, so it can be challenged with numbers.
Self-studyWhere the weekly evidence pays off2 min read▶
The reason a good monthly summit feels effortless is that the weekly review already did the work. The driver moves are already named, the segments already found, the actions already owned and dated. The monthly summit is not investigation - it is synthesis. If your monthly meetings feel like archaeology, the problem is upstream: your weekly cadence is not producing the record the monthly needs.
The pre-read is what makes it fast. Teams that write a short narrative memo and circulate it before the summit spend the meeting deciding, not presenting. The room reads in silence, then goes straight to the exceptions and the asks. It is the same instinct behind the weekly review - the document does the informing so the meeting can do the deciding.
Governance, guardrails, and Goodhart 8 min live
A metric system is only as trustworthy as its governance. Three habits keep it honest: one definition per metric (owned and documented, so nobody argues about what the number means), guardrail metrics (so you cannot optimise one number into harming another), and a working respect for Goodhart's Law - the moment a measure becomes a target, it stops being a good measure. Metrics get gamed, they go vain, and the defence is designed, not hoped for.
LiveGoodhart's Law, in one sentence3 min▶
Goodhart's Law: when a measure becomes a target, it stops being a good measure. The instant you tie rewards or pressure to a single number, people optimise the number rather than the thing it was meant to represent - and the two quietly come apart. Push signups as a target and someone buys junk traffic. Push tickets-closed and quality craters. The metric still goes up; the outcome it stood for does not.
- Gaming - the number is hit by shortcuts that do not serve the goal (junk signups, closed-but-unresolved tickets).
- Vanity - a number that always goes up and never informs a decision (cumulative totals, raw pageviews).
- The defence - pair every target with a guardrail, watch the pair, and rotate what you target as the constraint shifts.
LiveGuardrail metrics, by design3 min▶
A guardrail is a metric you commit not to harm while you push a target. Grow signups without letting activation fall. Cut cost without letting quality drop. Speed up delivery without raising the defect rate. The guardrail is what stops a driver tree from being weaponised - because any single lever can be pushed to an extreme that helps its own number and quietly damages the business. You design the pair before you set the target, not after someone games it.
Self-studyWhere OKRs fit - and where they bite2 min read▶
OKRs connect the metric system to strategy: an objective is the direction, key results are the measurable drivers you will move. The tree and the OKR are the same shape - a top-line ambition broken into levers. But OKRs are exactly where Goodhart bites hardest, because a key result is a metric turned into a target by design. That is why mature OKR practice pairs stretch key results with guardrails ("grow activation to 40% without lifting churn") and treats a gamed key result as a failure even when the number was hit.
The signups-versus-activation trap is the classic. A growth team is targeted on signups and hits it by pouring in low-intent traffic. Signups soar, the OKR turns green, and activation quietly collapses because none of the new accounts were real prospects. With activation set as a guardrail from the start, the team would have been forced to grow signups that actually activate - which was the point all along.
The summit done right, then onward 6 min live
A monthly summit done right has three features: a pre-read so the room arrives informed, an exceptions-only agenda so time goes to what moved rather than what did not, and decisions logged with owners so nothing dissolves on the way out the door. This is where the metric system connects to strategy and OKRs - and where this course hands you off to the siblings that build the machinery underneath the numbers.
LivePre-read, exceptions-only, decisions logged3 min▶
Three habits carry most of the value. The pre-read - a short narrative circulated ahead - means the meeting starts informed and can go straight to judgement. The exceptions-only agenda means you spend the hour on the branches that deviated, not the ones that behaved. And decisions logged with owners and dates mean the summit produces commitments, not just conversation. Skip any one and the summit slides back into a status parade.
- Pre-read - the document informs so the meeting can decide.
- Exceptions only - on-plan branches get a line; off-plan branches get the room.
- Decisions logged - owner and date on every decision, or it did not happen.
Self-studyWhere to go next2 min read▶
You now have the leader's half of metric decomposition: read a tree, run the weekly review, run the monthly summit, govern the numbers. The natural next steps build the machinery beneath the numbers you have learned to read.
- learn-business-intelligence - build the dashboards and reports that show these trees on a cadence.
- learn-data-warehouse - understand where the numbers under the tree actually come from.
- learn-strategic-thinking - connect the metric system to the strategy and OKRs it is meant to serve.
An honest note on scope. This course taught you to read and decompose metrics - the thinking, the cadence, the governance. It did not teach you to build the data platform under them: the pipelines, the models, the dashboards. That is a genuine, separate discipline, and it is exactly what the sibling courses above cover. Knowing which half you have is itself a piece of good judgement.
Self-studyThe whole leader track, in one line2 min read▶
Six sessions, one arc. You learned what a driver tree is, how to spot leading indicators, how to trace a drop, how the method transfers across six domains, how to run the weekly operational review, and now how to run the monthly strategic summit and govern the system so it stays honest. The builder track (b1-b10) takes the same thinking into hands-on trees, SQL, and a capstone diagnosis - a good next stop if you want to feel the mechanics, not just direct them.
Try it yourself - this week ◐ 20-30 min total
- Draft the four-question narrative for your unit this month: are we on plan, what moved and why, what are we doing about it, what do we need from leadership. Keep it to one page.
- Take your most-pushed metric and write its guardrail - the number you are not allowed to harm while you grow it. If you cannot name one, you are inviting a gamed result.
- Pick one metric your org reports and check it has a single written definition and one owner. Definition fights are governance failures hiding in plain sight.
- Audit one OKR key result for Goodhart risk: could someone hit the number without serving the goal? If yes, add a guardrail before next quarter.
- Choose your next course - learn-business-intelligence, learn-data-warehouse, or learn-strategic-thinking - depending on whether your gap is dashboards, data sources, or strategy.
Frameworks this session draws on
This closing session leans on the frameworks that keep a metric system honest and connected to strategy. This page draws on:
Three questions before you go 🎯 ◐ 90 seconds
1 · How does the monthly summit differ from the weekly review?
The weekly is operational and driver-level. The monthly synthesises a month of that detail into a decision-grade story for leadership - narrative over dashboards, decisions over updates.
2 · What does Goodhart's Law warn a leader about?
Tie pressure to a single number and it gets gamed or goes vain. The defence is designed: pair every target with a guardrail metric it is not allowed to harm.
3 · You are pushing signups hard as an OKR. What keeps it honest?
A target without a guardrail invites gaming - buy junk signups, hit the number, wreck activation. Pairing the target with a guardrail forces growth that actually serves the goal.