Business Metrics
Intermediate 13 min read Business Metrics

Analytics-Stakeholder Communication

Facts persuade only when framed for the decision

Analytics lands when it answers a stakeholder's decision, in their language, with a clear call to action. Framing, metrics choice and executive summaries decide whether insights move people.

communicationexecutive summaryframingsituationcall to actiondata narrative
Prerequisites: Dashboard KPI Design
Before we start

What you will learn

  • Frame analysis for a specific stakeholder decision
  • Write an executive summary with a call to action
  • Choose the metric that matches the audience's lever
Introduction

What is this?

Stakeholder communication is the skill of turning analysis into action: state the situation, the finding, the magnitude, and a recommended move, in the stakeholder's vocabulary. It replaces 'here is a dashboard' with 'churn rose in the bedding cohort; parental outreach grew it back in a pilot; we propose scaling it now'.

Motivation

Why do you need it?

  • Analysts who cannot explain lose their seat at the table regardless of talent.
  • Framing decides whether a finding lands as a threat or an opportunity.
  • Executives reward clarity: one headline, one number, one ask.
  • Healthy analytics teams communicate findings as recommendations, not file dumps.
Think about it

Mental model

Imagine

A doctor's consultation

Think of

Analytics communication

The doctor reads the labs (the analysis), then communicates: symptom, diagnosis, urgency, and the treatment decision. Nobody wants the raw lab PDF; they want what it means and what to do next.

Mechanics

How it works

  • Identify the stakeholder's decision and the constraint they own.
  • Pick the metric that moves that decision, from the registry.
  • Write the summary in one paragraph: situation, finding, magnitude, recommendation.
  • Support with a visual that shows the mechanism, not a chart dump.
  • Close with a call to action and the owner of the follow-up.

From analysis to decision message.

Analysis
Interpret
Frame
Recommend
Act
Hands-on

Examples

An executive summary in three lines

An executive summary in three lines
Situation:  MRR +4% MoM with retention flat.
Finding:    Growth is acquisition-led; expansion revenue fell for new cohorts.
Magnitude:  -180bps contribution, masking +9% gross during the pilot firm.
Recommendation: scale parental-outreach pilot to bedding cohorts by Oct 1;
owner growth-analytics, review weekly.

Situation, finding, magnitude, recommendation — one paragraph enables a decision without making the stakeholder do the analytics themselves.

Real world

In production

  • A weekly churn briefing leads with one retention number, its change, the cause and the proposed pilot — never a 14-sheet workbook.
  • A campaign review frames lift by funnel segment and closes with the budget reallocation ask.
  • A pipeline review narrates bookings vs plan with the single most-attributable driver each week.
Guidelines

Best practices

  • One message per communication; support it with up to three visuals.
  • Name the magnitude: number, direction, delta, and why it matters.
  • Use the stakeholder's vocabulary from their own KPI registry.
  • End with a concrete call to action and who owns it.
Watch out

Common mistakes

  • Leeding with methodology or SQL when the audience wants the decision.
  • Presenting a hundred slides of neutral data because status looks safer than a recommendation.
  • Ignoring the stakeholder's constraint, recommending what you want to build.
  • Letting the metric choice hide the message (GMV vs net revenue in an op narrative).
Root cause analysis

Common issues

Error
Stakeholder asks twenty clarifying questions at every review
Root cause

The message lacks scaffolding: context, magnitude, recommendation

Fix

Front-load the summary and put the evidence in backup slides.

Error
Recommendations get ignored
Root cause

No owner and no cadence attached to the ask

Fix

Close with a named owner and a review date.

Error
Two decks cite different numbers for the same KPI
Root cause

Definitions diverged between teams

Fix

Point both at the registry entry and reconcile to v#.

When things break

Debugging tips

  • Draft the one-paragraph summary first; only then pick the chart that proves it.
  • Ask 'what will you do differently with this?' at the review — if nothing, the communication missed.
  • Test your summary on a peer: can they restate the call to action?
  • Bring the metric definition to the table so the number is not questioned twice.
Interviews

Interview checkpoint

Test yourself

Quick quiz

0/2
1

What should an analytics update close with?

2

Choosing a flattering metric is the best way to persuade a stakeholder.

Go deeper

Official documentation

Storytelling with data (book site)
docs
Executive communication (HBR guide)
docs