How zero-based budgeting rebuilds a spending plan
In a conventional budget, last year’s spending is often the starting point: teams adjust it up or down, then defend the changes. Zero-based budgeting flips that sequence. A manager begins with no spending automatically carried forward and must explain what each proposed activity costs and what the organization gets in return.
That explanation may be organized into “decision packages”—small proposals that describe a service or activity, its cost, and the consequences of funding it at different levels. Leaders compare the packages against priorities and decide which to fund, reduce, postpone, or drop. The aim is to make the reasons for spending visible, not merely to produce a spreadsheet that adds up.
The tradeoff: clearer choices, more work
The method can expose expenses that have persisted mainly because they were already in the budget. It can also help leaders shift money toward current priorities instead of treating every department’s past allocation as a permanent entitlement.
But rebuilding the case takes time. Managers must gather cost and performance information, and senior leaders must review many proposals. If the process is rushed or judged only by immediate savings, teams may cut useful work whose benefits are hard to measure—such as training or maintenance. For that reason, zero-based budgeting is often most useful when applied selectively or periodically, with clear priorities for judging proposals.
Its practical consequence is a different conversation: instead of asking how much more a team needs than last year, leaders ask which activities are worth paying for now.
