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.
Related links
Skills & Plugins
- SpreadsheetsRuns the cuts and builds supporting charts (
$spreadsheets). - Google DriveReads metric definitions, dashboards, and launch context.
- SlackChecks stakeholder context and recent changes.
- DocumentsPackages the analysis as a brief with sources and caveats (
$documents).
Starter prompt
Define the metric before explaining movement
Fix the definition, comparison window, and source data first.
- State KPI, period, expected direction, decision.
- Attach dashboard, definition, exports.
- Check data quality and breakdowns.
- Run the prompt; keep drivers and hypotheses apart.
- 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
Analyze product feedback across tools
Cluster feedback from Slack threads, issue queues, and survey exports into themes with clear next steps.
Prepare a business review
Convert regular KPI, close, and forecast data into a performance story with cited sources.
Prepare a leadership reporting pack
Convert company progress, financial figures, and owner updates into a reporting pack backed by sources.


