Diagnose a KPI Drop: Junior Analyst's 5-Step Fix

Who This Helps

This is for you, Junior Analyst. You see a number go red. Your stakeholder wants answers. You need to find the real reason fast. The Data Storytelling for Stakeholders course gives you a repeatable method to do exactly that.

Mini Case

Meet Priya. She's a Junior Analyst at a subscription box company. Last month, new sign-ups dropped 12%. Her boss asked for a root cause by Friday. Priya used the One Key Message mission from the course. She focused on one metric: conversion rate from free trial to paid. She found the drop happened 7 days after a pricing page change. She shipped a clean analysis with one clear recommendation: revert the pricing page and A/B test the new version.

Do This Now (5 Steps)

1. Pick one KPI. Don't chase three metrics at once. Choose the one that matters most to your stakeholder.

1. Pull the last 30 days of data. Compare week over week. Look for the exact day the number changed.

1. List three possible causes. Brainstorm fast. Was it a product change? A marketing campaign? A seasonal trend?

1. Check each cause against the data. For each one, ask: does the data support this? Priya checked the pricing page change date against the drop date. Match.

1. Write one key message. State the root cause and one clear action. Example: "The pricing page change on March 10 caused a 12% drop in sign-ups. Revert the page and test the new version."

Avoid These Traps

• Trap: Blaming everything. If you list five causes, your stakeholder won't know what to fix. Pick one.
• Trap: No recommendation. Analysis without action is just noise. Always end with a clear ask.
• Trap: Skipping the date check. The root cause often hides in a single day's change. Find that day.
• Trap: Using complex charts. A simple line chart with an annotation is better than a heatmap your boss can't read.
• Trap: Waiting for perfect data. You have enough to start. Ship the analysis, then refine.

Your Win by Friday

By Friday, you will have one clean analysis with one root cause and one clear recommendation. Your stakeholder will say, "Great work, now I know what to do." That's the win. And honestly, it feels pretty good to be the person who brings clarity instead of confusion.