Isolate regional or platform drivers behind KPI drops
Break down aggregate product or revenue declines across platform and geographic dimensions. Use this when global numbers drop and leadership needs the root driver.
You getPrimary Contributor Summary, dimension Breakdown and ruled Out Segments
Prompt
Act as a senior operations data analyst. Analyze the KPI decline data pasted below to pinpoint the operational, regional, or platform-level source of the drop.
- Calculate or isolate which sub-segment accounts for the largest proportion of the total missing volume.
- Separate global baseline trends from isolated local shocks (such as localized outages, broken builds, or regional holidays).
- Provide clear attribution without conflating correlation with causation.
Output format:
- Primary Contributor Summary (what drove the drop and by what percentage)
- Dimension Breakdown (table with: Dimension, Performance Change, Share of Total Loss)
- Ruled Out Segments (segments that performed normally)
- Recommended Next Investigative Steps
The performance data and context are below:Example output
Paste your multidimensional summary table (such as daily active users cut by OS, country, or app version) into ChatGPT, Claude, or Gemini. Ask a follow-up prompt requesting a draft incident ticket for the engineering team responsible for that platform.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build three scenarios for revenue and demand forecasts
Generate structured best, base, and worst-case forecast models to prepare for demand swings. Use this during annual planning or runway updates.
Create an anomaly investigation checklist for analytics teams
Run a disciplined diagnostic process before investigating metric shifts. Use this checklist whenever unexpected data spikes or drops appear in reports.
Evaluate past forecast variances to set accurate targets
Analyze past forecast misses to identify systematic over- or under-projection patterns. Use this before locking in next quarter's revenue or operational targets.
Summarize customer segment shifts for executive updates
Convert raw cohort and customer segmentation tables into clear movement summaries. Use this to highlight changing customer mixes before monthly leadership reviews.
Analyze support ticket trends by category
Spot surging ticket drivers and recurring bugs across support logs. Use this to allocate team coverage and escalate product flaws quickly.
Pinpoint friction points in conversion funnels
Identify the exact bottleneck stage where prospective customers abandon your funnel. Use this when aggregate conversion drops without obvious reason.
- Resolve split device identities into single user records
- Summarize weekly metric anomalies into executive briefings
- Convert monthly operations metrics to executive updates
- Extract retention insights from cohort retention tables
- Select three core KPIs for your business goal
- Interpret A/B test results plainly