Summarize weekly metric anomalies into executive briefings

Convert raw week-over-week metric spikes and drops into concise executive briefs with business context and next steps.

You getExecutive Headline, critical Anomalies and watchlist

Prompt

Prompt
Act as a senior operations analyst. Review the weekly metric anomalies below and turn them into an executive-level status briefing.

Rules:
- Focus only on significant variations (greater than 10% change or outside standard baseline ranges).
- Translate raw metric shifts into practical business impacts (revenue, customer satisfaction, or operational drag).
- Distinguish between known seasonal/operational causes and unresolved incidents.
- Propose one concrete owner and next step for each highlighted anomaly.
- Keep language concise, factual, and free of filler phrases.

Output format:
1. Executive Headline: One sentence summarizing the net weekly operational health.
2. Critical Anomalies: Bulleted list where each item includes: Metric Name, Variance, Root Cause or Status, and Recommended Action.
3. Watchlist: A 2-column table listing Secondary Metrics to monitor next week and their Trigger Thresholds.

My weekly anomaly data is below:

Example output

Example for: weekly metrics covering an e-commerce checkout and logistics funnel

1. Executive Headline

Operational health remained stable overall, but payment gateway timeouts drove a brief conversion drop that requires engineering mitigation.

2. Critical Anomalies
  • Payment Gateway Failures: +28% week-over-week. Root Cause: Third-party API timeouts during peak Thursday traffic. Action: Engineering lead to implement automatic fallback routing by Wednesday.
  • Warehouse Pick-to-Ship Time: -14% improvement (down to 3.2 hours). Root Cause: Additional weekend shift clearing dispatch queues faster. Action: Supply chain manager to evaluate shift labor cost versus customer delivery ratings.
  • Return Merchandise Authorizations (RMA): +18% increase for apparel category. Root Cause: Unresolved; suspected sizing chart discrepancy on newly launched summer lines. Action: Product merchandising team to audit customer return reason codes by Friday.
3. Watchlist
Secondary MetricTrigger Threshold
Checkout Cart Abandonment> 68% (currently 66.2%)
First-Contact Resolution Rate< 75% (currently 77.4%)
Written by AI from this prompt. Your results will vary.

Paste your weekly metric variances, percentages, and incident notes into ChatGPT, Claude, or Gemini. As a follow-up, ask the model to draft a 3-bullet Slack update based on the resulting briefing.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Data Analysis
Data Analysis

Build a monthly metric review scorecard

Design a clean scorecard structure with clear metric definitions, target thresholds, and operational owners. Perfect for structuring monthly business reviews.