Who This Helps
You're a Junior Analyst who just saw a key metric tank. Maybe conversion dropped 12% overnight. Your boss wants answers, not excuses. This guide helps you diagnose the root cause fast and ship a clean analysis with clear recommendations. It's based on the Product Portfolio Strategy course, which teaches you to size bets and sequence work—perfect for turning a fire drill into a focused session.
Mini Case
Imagine you track daily active users (DAU) for a feature called "Quick Export." Last week, DAU was 5,000. This week, it's 4,400—a 12% drop. Your first instinct might be to panic. Instead, grab a coffee and a notebook. In 45 minutes, you can pinpoint the cause and recommend a fix. Here's how.
Do This Now (5 Steps)
- Check the date. Look at the drop timeline. Did it start on a Monday or a weekend? That clues you into whether it's a user behavior shift or a technical glitch.
- Segment the data. Break DAU by browser, device, or region. In our case, you find the drop is 90% on mobile Safari. Now you're narrowing in.
- Look for external events. Did a competitor launch a new feature? Did your team push a code update? Check release notes. You spot a CSS change rolled out 3 days before the drop.
- Run a quick correlation. Plot the drop against the code deploy. If the timing matches, you've got a suspect. In this case, the deploy happened 2 hours before the drop started.
- Write one recommendation. Don't list 10 fixes. Pick the most likely cause and suggest a rollback or a targeted fix. For example: "Revert the CSS change on mobile Safari and monitor DAU for 7 days."
Avoid These Traps
- Blame the data first. Don't assume a bug. Check if the drop is real by comparing to last month's same week.
- Skip the context. A 12% drop might be normal if it's a seasonal pattern. Always check historical trends.
- Overcomplicate. You don't need a dashboard. A simple spreadsheet with 3 columns (date, metric, event) works.
- Ignore the small stuff. Sometimes a KPI drop is just a tracking error. Verify your data source before diving deep.
- Forget the recommendation. Analysis without action is just noise. Always end with a clear next step.
Your Win by Friday
By Friday, you'll have a one-page analysis that shows: the root cause (mobile Safari CSS change), the impact (12% DAU drop), and the fix (rollback and monitor for 7 days). Your boss will see you as the person who turns chaos into clarity. And you'll have learned a repeatable process from the Product Portfolio Strategy course—specifically the "Kill Criteria" mission, which teaches you to spot when a bet isn't working. That's a win you can build on.