Most organisations budget the lazy way. They take last year’s numbers, add a percentage for inflation or growth, and call it done. Zero Based Budgeting (ZBB) throws that habit out. Every activity, every rupee, and every department has to earn its funding all over again, as if the organisation were starting from scratch. For commerce students, ZBB is worth understanding closely because it is not just a textbook technique. It has shaped how state governments in India plan spending and how global corporations chase cost efficiency during downturns.
Table of Contents
- What zero based budgeting actually means
- Where the idea came from
- What the Georgia experiment actually showed
- How the zero based budgeting process actually works
- Step 1: Define decision units
- Step 2: Build decision packages
- Step 3: Rank by cost-benefit analysis
- Step 4: Allocate resources and finalise the budget
- Traditional budgeting versus zero based budgeting
- Zero based budgeting in India
- Why organisations still turn to zero based budgeting
- The real challenges of implementing zero based budgeting
- When zero based budgeting is worth the effort
What zero based budgeting actually means
Zero Based Budgeting is a budgeting and planning process where every activity is justified from the ground up before each new budget cycle, instead of being carried forward simply because it was funded last year. A Texas Instruments accounting manager, Peter Pyhrr, first built this approach during the 1960s to make scarce resources stretch further toward defined objectives. The core shift is where the “burden of proof” sits. Under conventional budgeting, only new proposals get scrutinised while the existing base of spending is assumed to be justified. Under ZBB, the entire budget, base and increment together, has to be defended fresh every year.
This is also why ZBB is described as decision oriented rather than accounting oriented. A conventional budget only puts new spending requests under the microscope, whereas a zero based one holds every rupee to the same standard, old commitments included. Nothing is grandfathered in.
Where the idea came from
Peter Pyhrr was an accounting manager, not a professor, which is part of why ZBB reads more like a working manager’s tool than an abstract theory. He built the system inside Texas Instruments to tie spending decisions directly to strategic goals. His approach caught the attention of Jimmy Carter, who was then governor of Georgia. Carter hired Pyhrr directly to build a ZBB system for the state, and Georgia went on to become the first US state to adopt the technique across its entire executive budget, with Pyhrr personally running the programme. When Carter became President of the United States, he pushed for ZBB to be adopted across federal agencies, which is what took the technique from a corporate cost-control tool to a genuine public finance movement.
What the Georgia experiment actually showed
It is tempting to treat ZBB as a guaranteed fix, but the Georgia case is a useful reality check. A later academic review of the state’s experience credited the system with three real gains: a dedicated financial planning stage ahead of the actual budget draft, sharper management data, and more involvement from junior staff in shaping spending decisions. But that same review pointed to a heavy cost too, describing widespread frustration among department-level staff over how much extra effort the new process demanded. The lesson carries forward into every modern implementation: ZBB can sharpen decision-making, but it is never free.
How the zero based budgeting process actually works
Strip away the jargon, and ZBB follows a fairly logical sequence. It just demands far more documentation and discipline than incremental budgeting.
Step 1: Define decision units
A decision unit is any activity, programme, or department for which a manager will build a case. Getting this first step right matters more than any other part of the process, and it usually means working at the smallest budgeted unit within the organisation, not the department as a whole. Get this wrong, and every step after it becomes harder to compare and rank fairly.
Step 2: Build decision packages
For each decision unit, the manager responsible prepares a decision package. This is a document describing the purpose of the activity, what happens if it is not funded at all, the alternative ways of carrying it out, and the costs and benefits attached to each option. Packages are typically built in layers: a bare minimum level that keeps the activity alive, and then incremental packages on top of that minimum for enhanced levels of service. The manager closest to the activity writes the package because they understand its priorities and trade-offs best.
Step 3: Rank by cost-benefit analysis
Once packages exist, they are ranked in order of benefit to the organisation. This ranking answers two blunt questions: how much should we spend, and where should we spend it. Every level of ranked spending shows management exactly what gets funded and what gets left out if the budget stops at that point.
Step 4: Allocate resources and finalise the budget
Management works down the ranked list until the available budget is exhausted. Packages above the cut-off line get funded; everything below it does not, at least not this cycle. This is very different from an across-the-board percentage cut, because it protects high-value activities even while trimming weaker ones entirely.
Traditional budgeting versus zero based budgeting
| Aspect | Traditional budgeting | Zero based budgeting |
|---|---|---|
| Starting point | Previous year’s budget | Zero, every activity rebuilt from scratch |
| Focus | Increase or decrease over the past | Cost-benefit analysis of current needs |
| Approach | Accounting oriented | Decision oriented |
| Justification required | Only for new or incremental spending | For every rupee, old and new |
| Time and effort | Relatively low | Significantly higher |
Zero based budgeting in India
ZBB is not a purely academic import in India. It has actual policy history. A pilot at the Department of Science and Technology in 1983 came first, and a few years later, in 1986, the finance ministry formally brought the technique into the country’s public budgeting system. Central ministries were asked to review their programmes and prepare expenditure estimates on a zero base rather than simply extending the previous year’s numbers. A handful of state governments took the idea further into their own departments, and a research paper tracing this history notes that Karnataka, Andhra Pradesh, and Rajasthan were among the states that ran their own versions of the exercise. Early experience showed the technique’s potential to trim redundant schemes and direct spending more precisely, even though the government did not sustain a pure, full-scale version of ZBB across every ministry.
That mixed record is not unique to India. Full-scale, government-wide ZBB has struggled everywhere it has been attempted at that scale, largely because reviewing every single programme every year is an enormous administrative undertaking. What has endured instead is the logic of ZBB, informing how budgets get scrutinised even under other frameworks. The same research paper argues that this way of thinking, justifying spending, ranking options, and weighing alternatives, still has a role to play in India’s public finances today, and could help trim unnecessary running costs in government departments and bring more scrutiny to how welfare and development schemes are funded. In other words, even where India does not run textbook ZBB anymore, the questions it forces, such as whether a scheme still earns its allocation, keep showing up in budget reform conversations.
Why organisations still turn to zero based budgeting
Despite the effort involved, ZBB keeps resurfacing whenever organisations face real cost pressure. A few reasons explain why.
It exposes spending nobody questions. Costs that have quietly been renewed year after year get put back on the table. Reviewing each cost individually, rather than as part of a bigger lump sum, makes it far harder for wasteful or duplicated spending to slip through unnoticed.
It ties spending directly to strategy. A decision package that cannot show how it serves a business objective struggles to get funded, which pushes departments to think about value rather than habit.
It builds organisational discipline around ownership. Larger companies running ZBB programmes often appoint dedicated cost category owners to manage specific pools of spending. Having a named individual accountable for a spending category tends to shift meetings away from routine percentage adjustments and toward a genuine debate on what the work in front of them really requires.
It can produce real savings. Deloitte’s review of corporate cost practices found that companies stop budgets from creeping up automatically each year, and questioning long-standing assumptions tends to make operations noticeably more efficient over time.
The real challenges of implementing zero based budgeting
ZBB is not a free upgrade. The same congressional review that documented Georgia’s gains also flagged the practical obstacles that show up almost everywhere it is tried.
It is genuinely time-consuming. Building every decision package from scratch, every year, for every activity, creates a workload that can overwhelm the very managers who are supposed to be running operations rather than writing budget documents.
It invites resistance. Departments that benefit from routine, unquestioned funding rarely welcome a system built to interrogate exactly that funding. Deloitte’s analysis notes that expected savings are not always guaranteed, which makes the exercise a genuine gamble, and running it properly usually calls for people with specific training that many finance teams do not already have on hand.
Ranking is harder than it sounds. Comparing a marketing decision package against an IT infrastructure package on the same ranked list is not straightforward, since the two rarely share comparable units of benefit.
It can quietly turn back into incremental budgeting. Under time pressure, managers often default to justifying what already exists rather than genuinely rebuilding from zero, which defeats the purpose of the exercise entirely.
When zero based budgeting is worth the effort
Given the workload involved, few organisations run ZBB on every line item, every year, forever. It tends to work best where costs are discretionary and outcomes are measurable, such as administrative overheads, training budgets, marketing spend, and support functions, rather than statutory obligations or fixed contractual commitments. Many organisations run it selectively: applying full zero based scrutiny to a few high-spend or high-friction categories in a given year, while other categories follow a lighter, incremental review. This selective approach captures much of ZBB’s discipline without the administrative overload of rebuilding an entire organisation’s budget from nothing every twelve months.
What do you think? If your college or department had to justify every rupee of its budget from zero this year, which activities do you think would survive the cost-benefit test, and which ones might not?
References
- https://abacus.bates.edu/muskie-archives/ajcr/1977/ZBB.html
- https://corporatefinanceinstitute.com/resources/fpa/zero-based-budgeting/
- https://www.allstudyjournal.com/article/1614/7-8-23-647.pdf
- https://www.ibm.com/ae-ar/think/topics/zero-based-budgeting
- https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/zero-based-budgeting-gets-a-second-look
- https://www.deloitte.com/tz/en/services/consulting/perspectives/gx-zero-based-budgeting.html
Leave a Reply