Zero-Based Budgeting (ZBB)
Zero-based budgeting rebuilds next year's budget from nothing, forcing every activity to justify its cost and value again rather than inheriting last year's number plus a bit.
Steps loop back on themselves: each activity is costed afresh, compared to the others, then funded or dropped before starting over.
Reach for this when…
- Budgets keep growing a few percent a year with nobody able to say why.
- You suspect legacy programmes survive on habit, not merit.
- You need to fund something new and there's no obvious slack to cut.
How to run it
- Break the organisation's spending into discrete decision packages, by activity, not by department.
- For each package, state what it costs, what it delivers, and what happens if it's cut entirely.
- Rank all packages by value to the organisation's current priorities, not by history.
- Allocate available funds down the ranked list until the money runs out.
- Fund the packages above the line; cut or shrink the ones below it.
- Repeat next cycle from zero, not from this year's approved number.
A worked example
Situation. Eleni Papadopoulou ran finance at Ygeia Miteras Trust, a maternal-health NGO based in Thessaloniki, Greece, working across underserved rural areas, where the annual budget had crept upward for years on the same line items regardless of shifting donor priorities.
Applied. She split the year's spending into around forty decision packages - each clinic outreach route, training programme, and admin function costed and justified on its own - and had programme leads rank them against current donor priorities rather than last year's total.
Result. Three long-running outreach routes with falling attendance were cut or merged, freeing enough budget to fund two new routes in an underserved district without asking donors for more money.
The catch
ZBB is genuinely slow and heavy - building and justifying packages from scratch every cycle is a real cost, which is why most organisations that adopt it don't repeat it fully every year. It's easy to game: packages get written to look essential rather than honestly ranked. And it favours activities with countable output over ones with real but hard-to-measure value, like relationship-building or long-term capability.
If the same packages top the ranking every year with no real challenge, you're doing incremental budgeting with extra paperwork.
Origin: Peter Pyhrr