← All use cases

Analyze KPI root causes

Account for a surprising metric shift using evidence, then propose follow-up steps.

Hand ZeroTwo KPI dashboards, definitions of the metrics, exports, segment breakdowns, launch context, and stakeholder threads, and it distinguishes confirmed drivers from hypotheses in a root-cause brief tied to sources.

Intermediate
1h

Skills & Plugins

  • Spreadsheets
    Runs the cuts and builds supporting charts ($spreadsheets).
  • Google Drive
    Reads metric definitions, dashboards, and launch context.
  • Slack
    Checks stakeholder context and recent changes.
  • Documents
    Packages the analysis as a brief with sources and caveats ($documents).

Starter prompt

Weekly active users dropped about 9% in the four weeks after March 3. I've attached the dashboard export, the metric definition, and the release notes for that period. Break the drop down by platform, signup cohort, region, and acquisition channel, and write a short brief that separates drivers the data supports from guesses. For each driver, say what would disprove it and what check I should run next.

Define the metric before explaining movement

Fix the definition, comparison window, and source data first.

  1. State KPI, period, expected direction, decision.
  2. Attach dashboard, definition, exports.
  3. Check data quality and breakdowns.
  4. Run the prompt; keep drivers and hypotheses apart.
  5. Validate with the metric owner.

Challenge the root cause

Before leadership sees it, ask for counterevidence, segments where each driver fails, data limits, and the next confirming check.

Related use cases