← Back to blog

Junior Analyst · Metrics & Dashboards Basics

Diagnose a KPI Drop with Your Weekly Scoreboard

Stop guessing why a metric fell. Use your dashboard to find the real cause in one focused session.

Who This Helps

Hey Junior Analyst. You just saw your North Star metric drop 15% this week. Your boss wants answers. This is for anyone who needs to move from 'the number is down' to 'here's why, and here's what we should do'—fast. It uses the core dashboard skills from the Metrics & Dashboards Basics course.

Mini Case

Maya's team saw their 'Weekly Active Users' drop from 10,000 to 8,500. Panic started. Instead of guessing, she opened her weekly scoreboard. In 30 minutes, she saw the dip came entirely from one region (Europe, down 40%) and one user segment (new users, down 25%). The root cause? A broken sign-up flow deployed there 5 days ago. She had a clear recommendation before the team meeting even started.

Do This Now (5 Steps)

  1. Don't panic. A single data point is just a signal, not the full story. Take a breath.
  2. Open your weekly scoreboard. This is your single source of truth from the Metrics & Dashboards Basics course. Look at your primary metric and its supporting metrics.
  3. Check your guardrails. Did any supporting metric or alert fire? For example, if 'Sign-up Completion Rate' is a supporting metric, did it also drop?
  4. Slice by one dimension. Break the main KPI down by one key thing—like region, traffic source, or user type. Find where the drop is concentrated.
  5. Ask 'What changed?' For that specific slice, look for a product launch, a marketing campaign, or a technical change that happened just before the dip. Your dashboard layout should make this easy to spot.

Avoid These Traps

  • Chasing noise. Don't try to explain every tiny wiggle. Focus on significant, sustained changes.
  • Ignoring the good news. Sometimes a drop in the total hides a big win in one area. Find that too.
  • Starting without your dashboard. Ad-hoc queries in random tools will waste your hour. Your scoreboard is built for this.
  • Forgetting the timeline. Always note when the drop started. Match it to your team's release calendar.
  • Presenting just the problem. Your job is diagnosis and recommendation. Always pair the 'why' with a 'so what should we do?'

Your Win by Friday

By Friday, you can ship a clean analysis that says: 'Our main KPI dropped 15%. The root cause is a 40% drop in Europe, tied to last week's app update. I recommend we roll back that feature and message affected users.' You'll sound like the analyst who has things under control. That's a good feeling.