Who This Helps
This is for you, the junior analyst who just saw a key number tank. Maybe it's a 12% drop in weekly active users. Or a 7-day slide in conversion rate. You need to figure out why, fast. And you need to present it in a way that makes your manager say, "Nice work." The Product Portfolio Strategy course teaches you to size bets and sequence work. But first, you have to diagnose the problem.
Mini Case
Imagine you work on a product portfolio with three main features: a search tool, a recommendation engine, and a user dashboard. Last week, overall engagement dropped 15%. Your gut says it's the recommendation engine, because it had a buggy update. But you need proof. You pull data for each feature. Search is flat. Dashboard is up 3%. Recommendations? Down 22%. That's your culprit. Now you can dig into the update's impact and recommend a rollback or fix.
Do This Now (5 Steps)
- Grab the raw numbers. Pull the KPI for the last 30 days. Look for the exact day the drop started.
- Segment by feature or channel. Break the KPI into parts. Is one piece dragging everything down?
- Check for external factors. Did a competitor launch something? Was there a holiday? A marketing campaign end?
- Talk to one person who owns that piece. A quick chat with the engineer or product manager can reveal a known issue.
- Write a one-page summary. State the drop, the root cause, and one clear recommendation. Keep it to three bullet points.
Avoid These Traps
- Don't blame the data first. Sometimes the drop is real and you need to accept it.
- Don't jump to conclusions. That 12% drop might be from a bot attack, not a product issue.
- Don't overcomplicate your analysis. Your manager wants the one thing that matters, not a 10-page report.
- Don't ignore the easy fix. A broken link or a slow page load can cause big drops.
- Don't forget to check the date range. A 7-day drop might just be a weekend effect.
- Don't present without a recommendation. Always end with what to do next.
- Don't assume it's a single cause. Sometimes two small things add up to a big drop.
- Don't skip the follow-up. After you ship your analysis, check back in a week to see if the fix worked.
Your Win by Friday
By Friday, you will have identified the root cause of a KPI drop, written a one-page analysis with a clear recommendation, and shared it with your team. Your manager will see you as someone who can diagnose problems fast. And you'll have a clean artifact you can reuse for the next drop. That's a win. And hey, you might even get to leave early on Friday.