Turn data into decisions, not slide decks.
How to communicate metrics to stakeholders
Most metrics communication fails because it treats every audience the same and every number as equally important. The result is a data dump that nobody acts on. This guide covers how to structure metrics communication around narrative, tailor the depth and framing for different audiences, and use a metric tree to provide the causal context that raw numbers lack.
9 min read
Why most metrics communication fails
There is a common assumption in business that sharing data is the same as communicating. It is not. Sharing data means putting numbers in front of people. Communicating means helping them understand what those numbers mean, why they changed, and what should happen next.
Most organisations fall into the data dump trap. Someone exports a dashboard, adds a few bullet points, and sends it to a distribution list. Or they build a forty-slide deck that walks through every metric in sequence, one chart per slide, with the implicit message: here are the numbers, you figure out what matters.
The problem is not that people lack data. It is that they lack narrative. A number on its own tells you almost nothing. Revenue was 2.3 million last month. Is that good? Bad? Expected? Surprising? Without context, the number is inert. It occupies space on a slide without occupying space in anyone’s thinking.
The data dump
Every metric the organisation tracks is presented with equal weight. The audience is left to work out which numbers matter and how they relate to each other. Important signals are buried in noise. The reader skims, absorbs nothing, and files the report away unread.
The chart without a story
A line goes up or down. No explanation accompanies the movement. The audience is expected to interpret the chart themselves, which means ten people in the room form ten different conclusions. Discussion becomes a negotiation over interpretations rather than a conversation about what to do.
One size fits all
The same metrics report goes to the board, the executive team, team leads, and individual contributors. The board wants to know if the business is on track. A team lead wants to know which lever to pull this week. They receive the same spreadsheet and neither gets what they need.
All signal, no action
The report highlights that a metric is off track but stops there. There is no hypothesis about the cause, no proposed response, and no owner. The audience reads the red number, feels vaguely concerned, and moves on. The metric is still off track next month.
“If your stakeholders read your metrics report and their first response is "so what?", the report has failed. The job of metrics communication is to make the "so what" obvious.”
The narrative structure for metrics
Every effective metrics communication follows a simple narrative arc: context, change, cause, action. This is not a presentation framework invented by consultants. It is the natural structure of how humans process information. When someone tells you a story, they set the scene, describe what happened, explain why, and tell you what comes next. Metrics communication should work the same way.
The reason most reports fail is that they skip straight to the middle. They show the change (revenue is down 6%) without the context (we expected 4% growth based on pipeline), without the cause (two enterprise deals slipped to next quarter), and without the action (the sales team is accelerating three mid-market opportunities to close the gap). A number without this narrative wrapper is a fact without meaning.
- 1
Context: where we expected to be
Before showing any number, establish the baseline. What was the target? What was the trend? What did we expect to happen and why? Context transforms a number from an abstract data point into a position on a map. "Revenue was 2.3 million" means nothing. "Revenue was 2.3 million against a target of 2.5 million, continuing a two-month downward trend" means everything.
- 2
Change: what actually happened
Now show the number. Highlight the gap between expectation and reality. Be precise about the magnitude, direction, and timing. When did the change start? How large is the deviation? Is it accelerating or stabilising? The change is the news, the thing that demands attention. Present it clearly and honestly, without softening language or burying it in qualifications.
- 3
Cause: why it happened
This is where most reports fall silent, and it is the part the audience cares about most. What drove the change? Present the hypothesis with supporting evidence. If you do not yet know the cause, say so explicitly and describe the investigation that is under way. An honest "we are still investigating" is far more useful than a vague "we are monitoring the situation."
- 4
Action: what we are doing about it
Close with the response. What specific actions have been taken or will be taken? Who owns each action? When will we know if the action worked? This final step is what transforms a metrics report from an observation into a decision. Without it, the audience has information but no direction.
Apply this structure to every metric you highlight, not just the ones that are off track. When a metric exceeds its target, the narrative is equally important: what drove the outperformance, and is it sustainable or a one-off? Context, change, cause, action works in both directions.
Tailoring metrics for different audiences
The same metric means different things to different people. Churn rate to a board member is a signal about the long-term health of the business. To a customer success team lead, it is a prompt to review the at-risk account list. To an individual customer success manager, it is a list of specific customers who need a call this week.
Effective metrics communication acknowledges these differences and adjusts three things for each audience: the level of abstraction (how high up the metric tree you focus), the framing (what the metric means in terms they care about), and the expected response (what you want them to do with the information).
| Audience | What they need | How to communicate |
|---|---|---|
| Board of directors | Confidence that the business is on track, early warning of strategic risks, clarity on where leadership attention is needed | Show 3-5 top-level metrics with trend context. Focus on the narrative: what changed, why, and what management is doing about it. Avoid operational detail. Use the metric tree to show how a top-level miss traces to a specific root cause. |
| Executive team | Cross-functional visibility, understanding of how different parts of the business interact, ability to make resource allocation decisions | Walk the full metric tree from the North Star down to the second or third level. Highlight the 2-3 branches that need attention and the trade-offs involved. Provide enough detail to enable decisions, not so much that discussion gets lost in the weeds. |
| Team leads and managers | Clear picture of which metrics their team owns, whether those metrics are on track, and which levers are available | Focus on the branch of the metric tree that maps to their team. Show the sub-metrics they can influence and how those connect upward to the outcomes the business cares about. Include specific targets and the gap between current and target. |
| Individual contributors | Understanding of how their daily work connects to business outcomes, and which specific actions will move the metrics they influence | Show the leaf-level metrics they directly affect. Explain how those metrics feed into team and company-level outcomes. Keep it concrete: "when you reduce support response time, it improves customer satisfaction, which drives retention, which protects revenue." |
Notice the pattern. As you move down the organisation, the communication becomes more specific, more operational, and more directly tied to daily actions. As you move up, it becomes more aggregated, more strategic, and more focused on trade-offs and resource allocation.
This does not mean you need four separate reports. It means you need a single model, a metric tree, that each audience can navigate to the level that is relevant to them. A board member starts at the top and drills into one branch. A team lead starts at their branch and looks upward to understand the context. The tree is the same. The entry point is different.
How metric trees provide a natural narrative structure
A metric tree is not just an analytical tool. It is a communication tool. The hierarchical structure of a tree maps directly onto the narrative arc that makes metrics communication effective.
Start at the top of the tree. This is your context: the outcome the business is ultimately trying to achieve. Move down one level. Here are the drivers that determine whether that outcome is met. This is where you identify the change: which drivers are on track and which are not. Go one level deeper. Now you are at the cause: the specific sub-metrics that explain why a driver moved. The actions live at the leaves, where the operational levers are.
The tree gives you the narrative for free. You do not need to construct a story around the numbers. The story is the structure.
Consider the tree above. In a board meeting, you would present it like this: "Revenue is 4% below target this quarter. New revenue is on plan, so the miss is coming from existing customer revenue, which is down 8%. The root cause is a drop in retention rate. Our investigation shows that customers who do not complete onboarding within the first two weeks are three times more likely to churn. We are redesigning the onboarding flow and expect to see retention stabilise within 60 days."
That is context, change, cause, action, delivered in under 30 seconds, with the metric tree providing the structural backbone. The board understands exactly what happened, why, and what is being done. No slides required.
This is why organisations that use metric trees tend to have better metrics communication even without formal training. The tree itself teaches people to think in narratives because the structure forces you to connect outcomes to drivers to root causes to actions. It is difficult to present a tree walk as a data dump because the tree has a direction: top to bottom, outcome to action.
Visual design principles for metrics communication
How you present metrics visually has an outsized impact on whether your audience absorbs them. The goal of visual design in metrics communication is not to make things look polished. It is to make the important things impossible to miss and the unimportant things easy to ignore.
Lead with the gap, not the number
The most important piece of information is rarely the metric itself. It is the distance between the metric and the target. A chart that shows revenue at 2.3 million tells you less than a chart that shows revenue at 2.3 million against a target of 2.5 million. Always show metrics in relation to their target, their previous period, or their expected value.
Use colour to direct attention
Reserve colour for meaning. If everything is colour-coded, nothing stands out. Use a muted palette for metrics that are on track and a single accent colour for metrics that need attention. Your audience should be able to glance at the report and instantly know where to focus.
Show trends, not snapshots
A single data point is almost always misleading. Show at least 8-12 weeks of trend data so the audience can distinguish between noise and signal. A metric that dropped 5% this week looks alarming in isolation but unremarkable if it has been fluctuating within that range for months.
Preserve the hierarchy
When presenting metrics from a tree, maintain the parent-child relationship visually. Do not flatten the tree into a list of unrelated numbers. The hierarchy is the narrative. When an audience can see that retention rate sits beneath existing revenue, which sits beneath total revenue, they understand the causal chain without you having to explain it.
The five-second test
Show your metrics report to a colleague for five seconds, then take it away. Ask them: what is the single most important thing in this report? If they cannot answer, the visual hierarchy is not doing its job. The most critical information should be the first thing the eye lands on.
Common anti-patterns in metrics reporting
Recognising the patterns that undermine metrics communication is as important as knowing the practices that improve it. These anti-patterns are widespread because they feel productive. People invest real effort in creating reports that ultimately fail to drive action.
| Anti-pattern | Why it fails | What to do instead |
|---|---|---|
| The weekly data dump: 30 metrics in a spreadsheet, emailed every Monday | No hierarchy, no narrative, no indication of what matters. Recipients learn to ignore it entirely. | Highlight the 3-5 metrics that moved meaningfully. For each one, provide context, change, cause, and action. Send the full data as a link for those who want to dig deeper. |
| The green-yellow-red stoplight report | Oversimplifies reality. A metric marked "yellow" gives no information about direction, magnitude, or cause. Teams game the thresholds to avoid uncomfortable red indicators. | Replace traffic lights with trend arrows and gap-to-target percentages. Show whether the metric is improving or deteriorating, not just whether it crossed an arbitrary threshold. |
| The backward-looking narrative: "Last quarter we achieved..." | By the time the audience hears about it, the moment to act has passed. Backward-looking reports optimise for accountability, not for action. | Lead with what is happening now and what is about to happen. Use leading indicators from the bottom of the metric tree to surface emerging trends before they reach the lagging indicators at the top. |
| The metric without an owner: "Conversion rate dropped but we are not sure who is looking into it" | Without ownership, nobody investigates, nobody acts, and the same metric appears off track for months. The report documents the problem without solving it. | Every metric you communicate should have a named owner. When you highlight an off-track metric, name the person who is investigating and the date by which they will report back. |
| The vanity metric showcase: "We hit 100,000 sign-ups this month!" | The metric sounds impressive but has no connection to business outcomes. It creates a false sense of progress and diverts attention from metrics that actually matter. | Only communicate metrics that connect to the metric tree. If a number does not trace upward to a business outcome, it does not belong in a stakeholder report. |
The underlying pattern behind all of these anti-patterns is the same: they prioritise the act of reporting over the act of communicating. Reporting is mechanical. It answers the question "what are the numbers?" Communicating is intentional. It answers the questions "what do the numbers mean, why should you care, and what should happen next?"
If you find yourself spending most of your preparation time formatting a report and almost no time thinking about the narrative, you are reporting, not communicating. Invert the ratio. Spend 20% of your time on the data and 80% on the story the data tells.
Putting it into practice
Improving metrics communication does not require a transformation programme. It requires a few deliberate changes to how you prepare and present data. Start with these concrete steps and iterate from there.
- 1
Build or adopt a metric tree
You cannot communicate metrics effectively if you do not have a shared model of how they relate to each other. A metric tree provides that model. It shows every stakeholder where their metrics sit in the broader system and gives you the narrative structure for every conversation. If your organisation does not yet have a metric tree, building one is the single highest-leverage step you can take.
- 2
Apply context, change, cause, action to every metric you highlight
Before your next report or presentation, take each metric you plan to discuss and write one sentence for each element. What was the target? What happened? Why? What are we doing? If you cannot fill in all four, you are not ready to present that metric. Either investigate further or flag it as requiring investigation.
- 3
Tailor the entry point, not the data
Rather than creating separate reports for each audience, use a single metric tree and change where you start the conversation. For the board, start at the root. For team leads, start at their branch. For individual contributors, start at the leaves and trace upward. The data is the same. The perspective changes.
- 4
Replace static reports with tree walks
Instead of sending a PDF or slide deck, walk stakeholders through the metric tree in real time. Start at the top, identify which branches are off track, and drill into those branches. This format naturally enforces the narrative structure and prevents data dumps because you only discuss the branches that matter.
- 5
Close every communication with specific next steps
Every metrics update, whether it is a board presentation, a weekly email, or a Slack message, should end with named actions, owners, and timelines. If a metric is off track, state who is investigating and when they will report back. If a metric has recovered, state what worked and whether the fix is sustainable. The audience should never leave wondering "so what happens now?"
“The goal of metrics communication is not to demonstrate how much data you have. It is to give every stakeholder exactly the information they need to make the right decision at the right time. A metric tree, combined with a clear narrative structure, makes that possible without creating a separate report for every audience.”
Make every metric tell a story
KPI Tree gives your organisation a shared, navigable metric tree that every stakeholder can explore at the level that matters to them. Replace data dumps with narratives that drive decisions.
