Who This Helps
You're a Junior Analyst who just saw a key metric drop. Maybe revenue slipped 12% this month. Or user growth stalled. Your boss wants answers by Friday. You need a fast, structured way to find the real cause and recommend a fix. This is for you.
Mini Case
Meet Sam, a Junior Analyst at a growth-stage company. Sam noticed the weekly active users dropped 8% in two weeks. Panic? Nope. Sam used the Board Finance & Runway Narrative course approach. First, Sam listed all possible triggers: a bug, a marketing pause, a competitor move. Then Sam checked the data. The bug was real—a login error hit 15% of new users. Sam's fix: roll back the update and add a test. Result? Users recovered in 3 days. Sam's boss was happy.
Do This Now (5 Steps)
- List all possible causes. Write down every reason the KPI could drop. Think big: product, marketing, sales, external events.
- Check the data for each cause. Look at the numbers. Did traffic drop? Did conversion fall? Did churn spike? Find the one that matches the pattern.
- Pick the most likely root cause. Choose the cause with the strongest data support. For Sam, it was the bug because the error rate jumped exactly when users dropped.
- Quantify the impact. How much did the KPI drop because of this cause? Use numbers. Example: "12% drop in sign-ups due to login error."
- Write one clear recommendation. What should the team do? Be specific. "Fix the login bug by Thursday. Then monitor recovery for 7 days."
Avoid These Traps
- Chasing every shiny cause. Don't list 20 possibilities without checking data. Focus on the top 3.
- Blinding yourself with averages. Averages hide spikes. Look at daily or weekly trends.
- Ignoring the timing. Did the drop happen after a product launch? That's a clue.
- Forgetting to ask "why now?" The drop has a trigger. Find it.
- Writing a vague recommendation. "Improve user experience" is not a plan. Say "fix the login error."
- Overcomplicating the analysis. A simple table with causes and data is enough.
- Not sharing your work early. Show your boss a draft before Friday. Get feedback.
- Assuming it's one thing. Sometimes two causes combine. Check for interactions.
Your Win by Friday
By Friday, you'll have a one-page analysis that says: "Here's the root cause, here's the impact, here's the fix." Your boss will see you as a problem-solver. You'll feel confident. And hey, you might even get a high-five. (Okay, maybe just a nod. But still.)