Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
You getSituation read, table and first three actions for the next hour
Prompt
Act as a senior product analyst who has led many metric-drop investigations.
Your job: help me diagnose a sudden drop in a product metric and rank the likely causes. Before answering, ask me these questions in one numbered message, then wait for my reply:
1. Which metric dropped, by how much, and compared to what baseline?
2. When did it start (date and hour if known), and is it still falling?
3. Which platforms, regions and key user segments does the product have?
4. What changed recently: releases, experiments, campaigns, pricing, tracking or data pipeline work?
Rules:
- Walk the tree in this order: tracking and data pipeline, segment, platform, release or experiment, seasonality and calendar, external factors.
- Rule out broken tracking first. Do not treat the drop as real until the data is confirmed.
- For every cause, give one exact check: a SQL query sketch, a dashboard cut or a log to inspect, plus the result you would expect if that cause is true.
- Rank causes by likelihood based on my answers, with a one-line reason.
- Keep each check doable in under 30 minutes where possible.
Output format:
1. Situation read (one short paragraph)
2. Table: Rank | Cause | Branch | Why likely | Exact check | Expected result if true
3. First three actions for the next hour
4. Short update to send stakeholders
End with one line naming the missing data that would most change the ranking.Example output
Tips and common edits
Why this works
- Forcing the tracking check first stops teams from chasing a drop that is really a broken event.
- Each cause gets an exact query plus its expected result, so every check gives a clear yes or no.
- The fixed tree order covers seasonality and external causes that rushed investigations often skip.
Use this in ChatGPT, Claude or Gemini right after spotting a drop on a dashboard. Have the metric, start time, platform split and a list of recent releases or experiments ready.
Common edits
- Name your warehouse (BigQuery, Snowflake) so the SQL sketches match your syntax.
- Swap the stakeholder update for a Slack-length message for a leadership channel.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Interpret A/B Test Results and Decide Whether to Ship, Iterate or Kill
Paste your A/B test numbers and get a Ship, Iterate or Kill verdict backed by significance, sample ratio, guardrail checks and a list of what the data cannot prove.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
Write a Go-to-Market Launch Plan with Owners, Dates and Go/No-Go Criteria
Get a tiered launch plan with a T-minus timeline, one owner role per task, measurable go/no-go criteria, an hour-by-hour launch-day checklist and week-one metrics.