Who This Helps
This is for junior analysts who need to move from just reporting a problem to explaining it. It pulls from the Data Storytelling for Stakeholders course, specifically the 'Stakeholder Lens' mission. That mission is all about defining who your update is for and what decision it should drive.
Mini Case
Your weekly report shows a 15% drop in user sign-ups. Your first thought is to check the marketing campaign. But when you apply a stakeholder lens, you ask: 'What does the Product VP need to know?' You dig deeper and find the drop is isolated to users on a specific, older app version. The real issue isn't marketing—it's a compatibility bug affecting 12% of your user base. Now your recommendation is sharp and actionable.
Do This Now (5 Steps)
- Block 45 minutes. Seriously, put it on your calendar. This is your one focused session.
- Write down the exact KPI and the drop. For example: 'Weekly Active Users down 8% vs. last month.'
- Ask 'Who cares most about this?' Name one key stakeholder. Is it the Head of Sales? The Product Lead?
- Brainstorm three possible causes. Think user, technical, and external. For example: feature change, site slowdown, or a competitor launch.
- Pick the most likely cause and find one piece of evidence. Look for a related metric that also moved. Did page load time increase by 2 seconds when the drop started?
Avoid These Traps
- Don't present a list of five possible reasons without pointing to the main one. It leaves your stakeholder doing your job.
- Don't dive into the data without first asking what decision your stakeholder needs to make. Context is everything.
- Avoid jargon like 'negative variance.' Say 'drop' or 'decrease.' Keep it human.
- Don't forget to check if the change is even significant. A 1% wobble might just be noise. Save your energy for the real fires.
Your Win by Friday
By your next check-in, you can walk in and say: 'The 15% drop in sign-ups? It's being driven by a bug in the old app version. I recommend we prioritize the fix in the next sprint, and here's the data that shows why.' That's the difference between reporting data and telling its story. You've got this.