Variance Explanation & Accountability Prompt
Prompt
Explain variance between plan and actual. Metric: [NAME]. Plan: [TARGET]. Actual: [RESULT]. Variance: [$ and %]. Output: Explanation of variance (not excuse). Root causes. Responsible party. Corrective action plan. Timeline to recover to plan.
Why it works
The 'not excuse' framing in the output specification is the most important element — it forces the output to distinguish between external factors (market conditions, weather) and controllable causes, and then focus corrective action on the latter. Identifying the responsible party by role rather than by person converts the accountability from blame assignment to process ownership. The timeline to recover ensures the variance isn't just explained but is connected to a specific commitment.
Watch out for
Variance explanation frameworks that are used primarily for blame assignment rather than learning will cause teams to defensively over-attribute variance to external factors. Create a culture where honest variance explanations that identify internal failure points are rewarded rather than punished, and use variance patterns over time to improve forecasting rather than to evaluate individual performance on single-period results.
Used by