KPI Variance Analysis & Commentary
Generate variance analysis commentary explaining why KPIs deviated from targets with root causes and corrective actions.
Your dashboard shows revenue is 12% below target but nobody knows why. Leadership doesn't want more charts — they want the story behind the numbers. Variance commentary that explains what happened, why it happened, and what to do about it is what turns data into decisions.
Who it's for: FP&A analysts writing monthly variance reports for leadership, controllers explaining budget-to-actual deviations, business intelligence teams adding narrative to dashboards, operations managers reporting on KPI performance, department heads preparing for quarterly business reviews
Example
"Explain why our Q3 KPIs missed targets" → Variance analysis package: 8 KPIs with actual vs. target comparison, root cause commentary for each deviation, impact quantification in dollars, 3 structural vs. 2 one-time variances identified, corrective action recommendations, and executive-ready summary paragraph
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
npx ccplaybooks add recipe-kpi-variance-commentary# KPI Variance Analysis & Commentary
## Your Role
You are an expert performance analyst. Your job is to explain KPI variances with root causes and generate actionable management commentary.
## Core Principles
- Explain WHY, not just WHAT changed
- Separate structural trends from temporary events
- Show interconnections between KPIs
- Project forward impact on annual targets
- Focus on significant variances (>10% from target)
Get new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Analyzes KPI performance against targets, explains variances with root causes, assesses whether deviations are temporary or structural, and generates commentary suitable for management reporting.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Prepare KPI Data
Gather: actual vs. target for each KPI, prior period comparisons, and known context.
Step 3: Start Using It
claude
Say: "Analyze these KPI variances for Q3. Revenue beat by 5% but customer acquisition cost missed by 20%. Explain what's happening."
Commentary Structure
| Element | Content |
|---|---|
| Variance Summary | Which KPIs beat, met, or missed targets |
| Root Cause Analysis | Why each significant variance occurred |
| Structural vs. Temporary | Is this a trend or one-time event? |
| Interconnections | How variances in one area affect others |
| Forecast Impact | What this means for year-end projections |
| Corrective Actions | What to do about misses |
Tips
- Explain the WHY, not just the WHAT: "Revenue up 5%" is data; "Revenue up 5% driven by 2 large enterprise deals" is insight
- Separate structural from temporary: One-time events need different responses than trend shifts
- Show interconnections: High CAC and high revenue might mean you're buying growth
- Always project forward: "If this trend continues, we'll end the year at..."
Commands
"Analyze these KPI variances and explain root causes"
"Is the CAC increase temporary or structural?"
"How do these variances affect our year-end forecast?"
"Generate management commentary for the monthly review"
Troubleshooting
Commentary is too surface-level Provide context: "We launched a new marketing campaign in week 3 — that's driving the CAC spike"
Too many KPIs to analyze Focus: "Only analyze variances greater than 10% from target"
Can't determine root cause Flag: "Mark as 'requires further investigation' and recommend specific data to gather"