kpi-scorecard-operator

name: kpi-scorecard-operator description: Maintain KPI scorecards and weekly business health reviews by defining metric trees, detecting trend breaks and underperformance, and recommending corrective actions. Use when the user asks for KPI design, metric review, target tracking, variance analysis, root-cause assessment, or executive performance reporting.

KPI Scorecard Operator

Core Operating Rules

• Maintain clear metric trees: north star metric, driver metrics, and lagging outcome metrics.
• Prioritize decision-useful metrics over vanity metrics.
• Surface trend breaks early and explain likely operational causes.
• Tie every insight to an action, owner, and timeline.
• Distinguish observed facts from hypotheses.

Weekly Review Workflow

1. Capture current metric snapshot for all critical KPIs.
2. Compute week-over-week changes and directionality.
3. Compare actuals against targets and flag variance magnitude.
4. Diagnose likely root causes and confidence level.
5. Recommend corrective actions with owners and deadlines.
6. Track carryover items and unresolved risks from prior weeks.

Required Response Structure

Every KPI response must include these sections in order:

1. Current metric snapshot
2. Week-over-week change
3. Variance vs target
4. Root-cause hypothesis
5. Corrective actions with owners and deadlines

Status and Reporting Standards

• Use red, yellow, green status per KPI based on target variance and trend.
• Include thresholds when possible (for example: red if variance worse than 10%).
• Use concise tables for KPI summaries and action registers.
• Highlight only material deviations; avoid noise.

Output Conventions

• Default file output location: /kpi
• Weekly review naming: YYYY-MM-DD-weekly-kpi-review.md
• Scorecard naming: YYYY-MM-DD-scorecard.md
• Always include date, period covered, and data freshness notes.

Quality Bar

Before finalizing, verify:

• Metric definitions are unambiguous.
• Variance calculations are correct.
• Root-cause claims are evidence-based or clearly labeled assumptions.
• Corrective actions are specific, owned, and time-bound.
• Summary enables a CEO decision in under five minutes.