Definition
Zero-based budgeting, often shortened to ZBB, is a budgeting method that starts every period from zero rather than from last year's spending. Instead of taking last year's marketing budget and adjusting it up or down, ZBB requires the marketing team to build the case for every dollar as if the department had no budget at all, justifying each expense against what it actually accomplishes for the business today. Nothing carries forward automatically. A cost that existed for the last five years still has to earn its place in this year's budget on its own merits, not on the strength of having been funded before.
ZBB exists to fight a problem that incremental budgeting almost guarantees over time: baseline creep, where spending that made sense years ago keeps getting funded simply because it was funded last year and nobody stopped to ask whether it still should be. A traditional budget process asks 'how much more or less should this line get,' which quietly assumes the existing spend is the correct starting point. That assumption is often wrong, and it compounds year after year as nobody revisits it. Zero-based budgeting was built specifically to interrupt that pattern by forcing every expense to be re-argued rather than inherited.
A shallow version of zero-based budgeting is just an across-the-board budget cut with a fancier name, telling every department to trim 10 percent regardless of what that spending actually does. Real ZBB is different and considerably more work: it requires ranking spending by the value it delivers, understanding what would actually happen if a given cost were removed, and funding the highest-value activities first rather than cutting evenly across the board. Done properly, ZBB can end up increasing spending in some areas that are proven to work while cutting deeply in areas that turn out not to justify their cost, which a flat percentage cut would never surface.
By 2026, zero-based budgeting shows up in waves rather than as a permanent fixture at most companies, often adopted during a period of cost pressure or after a leadership change, then relaxed back toward incremental adjustments once the initial reset is done. The reason is straightforward: doing ZBB properly every single year is exhausting, and the returns diminish once the obvious inefficiencies have already been found and removed. Many companies now treat it as a periodic reset tool, run every few years or triggered by a specific business event, rather than the default budgeting method used every cycle.
This page covers how zero-based budgeting actually works, how it compares to traditional incremental budgeting, how it differs from driver-based planning, where the intensity of ZBB is worth it and where it is not, and how to run a ZBB exercise that produces real insight rather than just pain. The idea worth keeping is that ZBB is a forcing function for justification, not a cost-cutting trick on its own. It is valuable because it makes an organization defend spending it has stopped questioning, and that value shows up whether the final budget goes up, down, or stays roughly the same.
Key Takeaways
- Zero-based budgeting builds each period's budget from zero, requiring every expense to be justified fresh rather than assumed as a continuation of last year's spending.
- It exists to counter baseline creep, where incremental budgeting keeps funding old spending simply because it was funded before, without anyone revisiting whether it should be.
- Real ZBB ranks spending by the value it delivers rather than cutting evenly across the board, and can increase funding for proven activities while cutting unproven ones.
- By 2026 most companies use ZBB periodically or during cost pressure rather than every single cycle, since doing it properly every year is demanding.
- ZBB's core value is forcing justification of spending, which matters regardless of whether the resulting budget ends up larger, smaller, or about the same.
How Zero-Based Budgeting Works
A ZBB exercise usually starts by breaking spending into decision units, discrete packages of activity like 'customer support team' or 'trade show program' rather than looking at broad expense categories. Each decision unit owner has to build a case from scratch: what does this activity cost, what does it produce, and what happens if it is not funded at all. That last question, framed honestly, is what separates ZBB from a normal budget request, since it forces someone to articulate the actual consequence of zero funding rather than simply asking for a number.
Once every decision unit has a justification and a cost, the packages get ranked by the value they deliver relative to their cost, ideally across the whole organization rather than department by department, since a low-value package in one team might rank below a high-value package in another. This cross-department ranking is one of the harder parts logistically, because it requires a shared way of comparing value across very different kinds of spending, marketing programs against engineering headcount against facilities costs, which do not naturally sit on the same scale.
Leadership then draws a funding line based on the total budget available, funding decision units from the top of the ranked list down until the money runs out. Anything that falls below the line either gets cut entirely or funded at a reduced level, and that decision is now tied to an explicit tradeoff, funding this activity meant not funding that one, rather than an arbitrary percentage applied without a clear sense of what was actually being given up.
In practice this process rarely runs as cleanly as the framework suggests. Ranking dozens or hundreds of decision units consistently is genuinely hard, some justifications are stronger on paper than the underlying reality, and political pressure to protect certain budgets does not disappear just because the process is called zero-based. Most organizations that run ZBB well treat the first pass as a rough cut, then spend real time interrogating the packages near the funding line, since that is where the actual tradeoffs and the most useful decisions live.
Zero-Based Budgeting Compared to Incremental Budgeting
Incremental budgeting takes last year's number as the baseline and adjusts it up or down, which is fast, familiar, and easy for department heads to plan around since they mostly know what to expect. It works fine as long as the underlying activities still deserve their funding, and it fails quietly when they do not, since nothing in the process ever asks that question directly. That ease is exactly what makes it attractive to organizations that value calm planning over hard scrutiny.
Zero-based budgeting asks that question directly, at the cost of a dramatically heavier process. Building a justification from scratch for every decision unit, then ranking them all against each other, takes far more time and organizational energy than adjusting last year's figures, and it tends to generate more internal friction, since people naturally feel more exposed defending a budget from zero than negotiating a modest increase from an accepted baseline.
The two methods also surface different problems. Incremental budgeting is good at controlling the pace of change, preventing wild swings from one year to the next, but it is bad at catching spend that has quietly stopped earning its keep. Zero-based budgeting is very good at catching exactly that, since every expense has to be re-justified, but it is a blunt instrument for managing steady, predictable change, since it is not really built to answer 'how much should this grow' so much as 'should this exist at all.'
For that reason a lot of organizations that have tried full ZBB every year eventually settle into a hybrid, running incremental budgeting most years for the sake of sanity and predictability, and running a full zero-based exercise periodically, say every three to five years or after a major strategic shift, to catch whatever has drifted in the meantime. That combination tends to capture most of ZBB's benefit without the annual toll of rebuilding every justification from scratch.
What Makes Zero-Based Budgeting Different From Driver-Based Planning
Driver-based planning and zero-based budgeting are both reactions against a stale, incremental budget, which is why they sometimes get lumped together, but they attack the problem from different angles. Driver-based planning asks 'what operational metric explains this cost, and how should the number change as that metric changes.' Zero-based budgeting asks a more fundamental question: 'does this cost deserve to exist at all, and at what level.' One is about connecting spend to a formula, the other is about justifying spend against its value.
The two are not mutually exclusive, and in fact work well together. A ZBB exercise can decide that a customer support team's headcount should be funded at a certain level, and then a driver-based model can determine how that headcount should scale with ticket volume or customer count going forward. ZBB sets the initial justified baseline, driver-based planning governs how that baseline flexes afterward, and combining them avoids both a stale baseline and a formula-driven budget built on an unquestioned starting point.
They also differ in how often they are practically run. Driver-based planning is meant to be a recurring structure, updated every forecast cycle as part of normal operations. Zero-based budgeting is usually episodic, a heavier exercise run occasionally precisely because rebuilding every justification from scratch every single cycle is not sustainable for most organizations, in a way that updating driver formulas month to month generally is. A company that tried to run full ZBB that often would burn out its finance team quickly.
Confusing the two leads to real mistakes. Treating driver-based planning as sufficient justification, on the theory that a formula-driven number must be correct, misses that a driver relationship can be validated mathematically while still being connected to a cost that should not exist at all. Treating ZBB as a substitute for ongoing driver-based forecasting misses that a one-time justification exercise does not tell you how a cost should flex with the business between now and the next ZBB cycle.
Where Zero-Based Budgeting Fits and Where It Does Not
ZBB fits well where a cost structure has been left unexamined for a long time and leadership suspects real inefficiency has built up, which is common after a company has grown quickly through acquisitions, or gone through several years of incremental budgeting without a serious reset. It also fits well during a genuine turnaround, where the organization needs to make hard, well-reasoned tradeoffs quickly and cannot afford to let political inertia protect spending that is not earning its place.
It fits especially well on discretionary and overhead spending, marketing programs, travel, software licenses, professional services, categories where the link between spend and outcome is often weaker than anyone assumed and rarely gets scrutinized once a budget line is established. These are the areas where a fresh justification exercise most often finds real savings, since incremental budgeting tends to let this kind of spend drift upward quietly for years. A subscription nobody uses anymore tends to surface here first.
It fits poorly on costs that are largely fixed by contract, regulation, or physical necessity, a long-term facilities lease, statutory compliance spending, or the baseline headcount needed to keep the lights on. Forcing a from-scratch justification on costs that cannot realistically change much in the short term burns a lot of organizational energy for very little insight, since the answer to 'should this exist' is effectively predetermined. Re-litigating a lease with eight years left produces a report, not a decision.
It also fits poorly as an annual ritual, since the effort required to do ZBB properly does not scale down well and running it every year tends to produce diminishing returns after the first pass finds the obvious problems. And it fits poorly when it is really being used as cover for a predetermined headcount cut dressed up in the language of justification, since employees quickly sense when the zero-based framing is theater around a decision that was already made, which damages trust in the process for the next time it is actually needed.
How to Run Zero-Based Budgeting Well
Define decision units at a granularity that is meaningful but not overwhelming, big enough that reviewing hundreds of them is not itself a full-time job, small enough that each one represents a genuinely separable activity someone could actually choose to fund or not. Getting this wrong in either direction, too coarse and the justification becomes vague, too fine and the process drowns in volume, is one of the most common reasons a ZBB effort stalls before it produces anything useful.
Push every decision unit owner to genuinely answer what happens at zero funding, not a softened version of the answer. It is easy to write a justification that assumes some funding is a given and describes only the downside of losing the marginal dollar. The more useful exercise, even if the final decision funds the activity fully, is understanding the real consequence of eliminating it entirely, since that is what actually reveals whether the spend is essential or just habitual.
Use a consistent framework for ranking value across very different kinds of spending, rather than letting each department argue its case in its own terms. Without a shared basis for comparison, a marketing team's justification and an engineering team's justification are not really comparable, and the ranking step turns political rather than analytical. Even an imperfect common framework, tied to revenue impact, risk reduction, or a defined set of strategic priorities, works better than leaving the comparison to whoever argues most persuasively in the room.
Concentrate the real scrutiny on the decision units near the funding line rather than spreading equal attention across everything. The packages clearly above the line and clearly below it rarely need much debate, the interesting tradeoffs and the most useful decisions live in the middle, where a modest change in ranking criteria could shift a package from funded to cut. Spending disproportionate time there produces far better decisions than a uniform review of every single item.
Resist running a full ZBB exercise every single budget cycle. The heavy justification work finds most of its value in the first pass and the occasional reset after that, and repeating the full exercise annually tends to exhaust the organization for diminishing returns. A more sustainable pattern is a full ZBB reset every few years, or when triggered by a specific event like a merger or a real cost pressure, with lighter incremental budgeting in the years between.
Best Practices
- Define decision units at a granularity that is meaningful without making the review process unmanageable.
- Require an honest answer to what happens at zero funding for each activity, not a softened version that assumes some funding is a given.
- Use a consistent ranking framework across departments so spending in very different categories can actually be compared on the same basis.
- Concentrate scrutiny on the decision units near the funding line, where the real tradeoffs and most useful decisions live.
- Run a full zero-based exercise periodically rather than every budget cycle, since the effort produces diminishing returns after the first pass.
Common Misconceptions
- Zero-based budgeting is not the same as an across-the-board percentage cut; it ranks spending by justified value, which can increase some budgets while cutting others.
- It is not meant to be run every single year at most companies; the effort is usually worth it as a periodic reset, not an annual ritual.
- ZBB is not primarily a headcount-cutting tool; using it mainly as cover for a predetermined cut undermines the honest justification the process depends on.
- It does not replace ongoing forecasting; a ZBB exercise sets a justified baseline, but something else still has to govern how spending flexes afterward.
- Zero-based budgeting is not a purely financial exercise; it depends heavily on operational judgment about what each activity actually produces.
