Variance Analysis for Non-Finance PMs

When I started managing programs with real budgets, variance analysis felt intimidating. The finance team would send reports full of terminology I did not fully understand. But over time, I realized that the version of variance analysis PMs need is much simpler than what accountants do.

The Three Questions

Every month, I answer three questions about each program's budget.

Are we spending what we planned to spend? This is straight math. Planned spend for the period minus actual spend. Positive variance means underspend. Negative means overspend. I track this at the category level — labor, tools, infrastructure, and third-party services.

Why is the number different? This is where the value is. I categorize every variance above 3% into one of four buckets: timing (we spent it earlier or later than planned), scope (work was added or removed), rate (the cost per unit changed), or efficiency (we used more or fewer resources than expected).

What do we do about it? Timing variances usually self-correct. Scope variances need a change order conversation. Rate variances need a vendor or staffing discussion. Efficiency variances need a process review.

Making It Stick

I present this analysis in a single slide during monthly business reviews. Three columns: category, variance percentage, and root cause. No charts. No twelve-page reports. Leadership wants to know if we are on track and what needs attention. This format gives them exactly that.

The first time I presented variance analysis this way, my director asked me to teach the other PMs how to do it. It is not complicated. But the discipline of categorizing why a variance exists, not just that it exists, is what separates useful analysis from number reporting.

Stop sending spreadsheets. Start telling the story behind the numbers.