Zero-Based Budgeting

Definition

Zero-Based Budgeting (ZBB) is a budgeting technique in which every cost element — labour, equipment, indirects, overheads — is built up from zero for each new budget cycle and must be justified by the scope of work, productivity assumptions, and unit rates current at the time of estimating. ZBB contrasts with incremental budgeting, which simply escalates the previous period's budget. Standard definitions sit in the PMMilestone PM Glossary.

History

ZBB was developed by Peter A. Pyhrr at Texas Instruments in 1969 and famously adopted by U.S. President Jimmy Carter for the federal budget in 1977. It returned to prominence in the 2010s through corporate cost-transformation programs at AB InBev, Kraft Heinz, and several global EPC contractors. The historical case studies appear in the cost-transformation track of the Project Controls Academy.

Principles

• No baseline entitlement — every cost competes for inclusion on its current merits.
• Cost drivers, not cost categories — budget by the activity that consumes the resource.
• Accountable owner per decision package, with explicit linkage to scope and output.
• Ranking — decision packages are stack-ranked and funded down to the available envelope.
• Periodic, not perpetual — apply ZBB to a subset of costs each cycle, not to everything every year.

Real-World Construction Example

An EPC contractor running a portfolio of five concurrent refinery shutdowns applied ZBB to indirect cost for the 2025 turnaround season. Previous years' indirects had been escalated at 3 percent annually with no scrutiny. The ZBB exercise broke indirects into 42 decision packages — site offices, supervision crew size, scaffolding crew, transport, IT support, and so on. Three packages were eliminated entirely, eight were halved, and twelve were re-scoped to outsourced services. Net indirect cost dropped 18 percent against the incremental baseline while supervision hours per direct labour hour stayed flat — i.e. no quality compromise. The discipline was repeated annually but ZBB itself was applied only every third year.

IT / Agile Example

A digital transformation portfolio used ZBB to reset the engineering tools and platform budget after three years of accretion. SaaS subscriptions, observability stacks, build infrastructure, and developer-productivity tools were each rebuilt as decision packages. The exercise surfaced six redundant tools, four under-used licences, and one platform that two teams were paying for separately. Annual run-rate savings of USD 4.1 million were redirected to platform engineering capacity — a structurally better outcome than a flat cost cut.

Project Controls Perspective

ZBB is a strategic cost discipline more than a project controls technique, but the controls function executes it. The cost-engineering team owns the decision-package framework, the cost-driver model, and the reconciliation back into the project budget. After the ZBB exercise, the discipline transitions into normal job cost reporting and cost control. Validate the rebuilt budgets against the EVM Calculator and benchmark against historical projects in the Failure Database.

Practical Lessons Learned

• ZBB without reference-class benchmarking turns into politics. Anchor decision packages in external data.
• The first ZBB exercise on a portfolio always finds 10–20 percent waste. The fifth one finds 2 percent. Diminishing returns set in quickly.
• Confusing ZBB with a cost-cutting exercise destroys morale. The discipline is about justification, not reduction.
• Owners and contractors play it differently — owners ZBB at the portfolio level, contractors at the tender level.

Common Mistakes

• Treating ZBB as a one-off cost-cutting exercise instead of a recurring discipline.
• Confusing ZBB with simple budget cuts — the method is about justification, not reduction.
• Applying it to every cost every year — exhausting and rarely improves the result.
• Skipping the cost-driver analysis and going straight to line-item budgeting.

Expert Tips

• Pair ZBB with reference-class benchmarking — without external data, decision packages become political.
• Define decision packages around outcomes, not departments. "Maintain field IT availability of 99.5 percent" beats "IT department".
• Use ZBB selectively — typically on indirects, overheads, and the largest variable cost categories.
• Document the assumptions behind every decision package. Year 2 ZBB starts from the documentation, not from scratch.

Key Takeaways

• ZBB rebuilds the budget from zero with explicit justification for every cost.
• The discipline is about justification, not reduction — though savings usually follow.
• Reference-class benchmarking is the silent partner that makes ZBB credible.
• Apply selectively and periodically; perpetual ZBB exhausts the organisation.

Further Reading

Recommended titles on ZBB and cost transformation are listed in PMMilestone Books & Publications, curated by the PMMilestone founder.