Who This Helps
You're a junior analyst who just saw a key number drop. Maybe revenue per user dipped 12% overnight. Or active users slid for 7 days straight. Your boss wants answers by Friday. You want to deliver a clean analysis with clear recommendations. This is for you.
Mini Case
Mei runs analytics at a fast-growing SaaS company. One Monday, she noticed the "trial-to-paid" conversion rate dropped from 18% to 14%. That's a 22% relative decline. Panic started. But Mei had a process from the Data Reliability Leadership course. She didn't guess. She diagnosed.
She grabbed the first-30-min incident triage card from the course's Incident Triage mission. She checked three things: data pipeline health, recent code changes, and user behavior shifts. Within 45 minutes, she found the root cause: a new onboarding screen confused users. The fix was a simple copy change. Conversion bounced back in 3 days.
Do This Now (5 Steps)
- Pause and define the drop. Write down the exact metric, time window, and magnitude. Example: "Revenue per user fell 12% from Monday to Tuesday." This stops you from chasing ghosts.
- Check your data pipeline first. Is the data source still reliable? Look for missing timestamps, null values, or sudden volume changes. If the pipeline broke, your analysis is garbage.
- List possible causes. Brainstorm three to five reasons. Don't overthink. Common ones: a bug, a marketing campaign ended, a competitor launched a feature, or a seasonal effect.
- Test each cause with one chart. For each hypothesis, build a simple chart. For example, if you suspect a bug, plot conversion by user segment. If the bug only hit mobile users, you'll see a clear split.
- Write your recommendation in one sentence. After you find the root cause, state the fix clearly. Example: "Revert the onboarding change to restore trial-to-paid conversion." Then ship it.
Avoid These Traps
- Don't blame the data first. 80% of KPI drops are real. Check the pipeline, but assume the number is correct until proven otherwise.
- Don't analyze alone for too long. Share your early findings with a teammate. Fresh eyes spot blind spots.
- Don't write a novel. Your analysis should fit on one page. Bosses love brevity.
- Don't ignore the calendar. Did a holiday start? Did a major product launch happen? Context matters.
- Don't forget to celebrate. Finding the root cause in one session is a win. High-five yourself.
Your Win by Friday
By Friday, you'll have a one-page analysis with the root cause and a clear recommendation. Your team will trust your numbers. Your boss will see you as reliable. And you'll feel like a detective who cracked the case. That's the power of a focused diagnosis session.