Zero-Based Budgeting (ZBB)

Zero-based budgeting, or ZBB, builds the budget from scratch each cycle. Instead of taking last year's spending as a starting point and adding or subtracting a percentage, managers must justify every cost as if it were new. Each activity is examined to decide whether it is needed, how much it should cost and whether there is a cheaper way to achieve the same result. Spending that cannot be justified is removed.

ZBB was developed in the 1970s, notably by Peter Pyhrr at Texas Instruments, and was later adopted by some governments and large companies. It gained renewed attention in the 2010s when several consumer goods companies used it to make large, lasting cost reductions. For IT financial management, ZBB is a powerful way to challenge technology costs that have built up over years of incremental budgeting, although its effort means it is often applied selectively.

Definition of Zero-Based Budgeting (ZBB)

Zero-based budgeting is a method of budgeting in which all expenses must be justified for each new period, starting from a base of zero. Every function and activity within the organization is analyzed for its needs and costs, and budgets are built around what is needed for the coming period.

ZBB contrasts with incremental budgeting, which takes the previous period's budget as a starting point and adjusts it for expected changes.

How ZBB Works

In a traditional ZBB process, activities are grouped into decision units, such as teams, services or cost categories. Each decision unit prepares decision packages that describe its activities, costs, benefits and the consequences of not funding them, often at several levels of service.

Decision packages are then ranked by priority, and funding is allocated from the top down until the budget is exhausted. Lower-priority activities that fall below the line are reduced, redesigned or eliminated.

Modern versions often focus on cost categories rather than organizational units, examining, for example, all spending on software or travel across the whole organization at once.

Variations of ZBB

Full ZBB, applied to the entire budget every year, is rare because of the effort it requires. Many organizations use variations, such as applying ZBB to selected cost categories, rotating it across functions over several years, or using it to reset the baseline once and then budgeting incrementally.

Some organizations apply zero-based thinking to specific categories that tend to grow unchecked, such as software subscriptions, consultants or travel, while using simpler methods for stable costs.

The common principle is that spending is not assumed to continue just because it existed last year. Every cost must earn its place in the budget each time it is reviewed.

Importance of Zero-Based Budgeting in IT Financial Management

Technology budgets often grow through incremental additions, with old costs rarely removed. ZBB is one of the most effective ways to challenge this pattern and reset the cost base.

It also encourages closer links between spending and business priorities.

For technology leaders asked to fund new initiatives without increasing the budget, ZBB can identify the savings that make that possible.

Uncovering Legacy Costs

Over time, technology budgets accumulate costs that no longer deliver value: licenses for retired applications, maintenance on unused hardware, duplicate tools and services kept running out of habit. Incremental budgeting carries these costs forward year after year.

ZBB requires each cost to be justified, which brings these legacy costs to the surface. Software, infrastructure and contractor spending are common areas where ZBB finds significant savings.

The process also clarifies ownership, since each cost must have someone willing to justify it.

Aligning Spending With Priorities

By ranking activities and funding the most important first, ZBB connects technology spending directly to business priorities. Activities that support strategic goals receive funding, while those that do not are reduced.

This can help shift spending from running existing systems toward growth and transformation, changing the balance in the run, grow, transform model.

It also makes trade-offs explicit, since leaders can see exactly which activities fall below the funding line.