Zero-based budgeting: fund the work that matters.

Before challenging cost packages, agree which capabilities matter to the strategy. In a retailer, product availability, reliable fulfilment and the customer experience may deserve protection even as the organisation reduces complexity elsewhere. A uniform savings percentage across every function cannot express those choices.

Ask business leaders to describe the outcome each activity supports. Then distinguish an essential service from a legacy habit and a differentiating capability from an expensive version of a standard process. The same cost category can contain all three. Marketing, for example, includes work that builds demand and work that exists because the organisation has accumulated overlapping agencies, reports and approval layers.

This discussion should produce explicit guardrails: the customer outcomes, service levels and capabilities that a cost initiative must preserve. It should also identify potential reinvestment priorities. Funding them still requires a business case; calling an activity strategic should not exempt it from scrutiny.

A ledger tells you where expenditure was booked. It rarely explains which business demand created it. Build cost packages that make an activity visible across functions and business units: technology, logistics, facilities or external services, for example. Reconcile those packages to finance, so the programme and the budget start from the same total.

For each package, separate volume, service level, unit cost and capacity. A delivery cost increase might reflect more orders, smaller baskets, additional express deliveries or a higher carrier rate. Each requires a different response. Negotiating the rate alone leaves the other drivers untouched.

Document the assumptions and the data gaps. Use benchmarks to identify questions worth investigating, then adjust for differences in customer proposition, scale and operating model. A peer comparison is a challenge to explain a gap, not sufficient evidence that the same cost level is achievable.

The first opportunity list often follows the chart of accounts: travel, contractors, software and meeting costs. That is a useful entry point, but the larger decision may sit upstream. Travel can be a consequence of where roles are located. Contractor demand can reflect unclear internal ownership. Meeting costs can be a symptom of a decision process that requires too many people.

Develop alternatives at the level of work. Remove activities that no longer serve a clear purpose, simplify what remains, and then assess standardisation, automation, sourcing and commercial terms. Automating a redundant report preserves the wrong activity at a lower unit cost.

Compare alternatives against the agreed guardrails. Include transition effort, implementation cost, dependencies and the effect on customers and employees. A seemingly attractive option may simply transfer cost to another department or push unresolved work onto frontline teams.

ZBB creates a useful tension between the leader responsible for a business result and the owner responsible for a cost package across the enterprise. The business leader understands demand and delivery. The package owner sees common standards, supplier economics and opportunities that disappear inside individual budgets.

The model needs clear decision rights. Specify who proposes a service level, who challenges its economics, who approves exceptions and who resolves a disagreement. Without that clarity, dual ownership becomes a second layer of meetings and neither person feels accountable for the result.

Finance should maintain the common baseline and validate the financial effect, while the operating owner remains responsible for changing the work. Agree a regular review of material deviations and their causes. A review that only reports red or green status does not make a trade-off or remove a delivery obstacle.

An approved initiative is not yet a financial result. Connect it to an owner, a delivery milestone, a budget line and a date when the benefit can start. Contract notice periods, recruitment plans, system changes and operational dependencies can all create a gap between the decision and the result.

Keep different types of benefit separate. Lower supplier expenditure is different from avoided future hiring, and both differ from capacity released for other work. Show gross recurring savings, implementation costs and approved reinvestment separately, with a consistent view of the net effect. This prevents the same benefit being claimed by procurement, a function and a transformation programme.

Then change the mechanisms that could recreate the old cost base. Update approval thresholds, purchasing rules, service agreements, role responsibilities and planning assumptions. Teams need to understand the choices and the reasons behind them. A lower budget without a workable operating model encourages deferral, exceptions or a quiet return to the previous way of working.

Start with a manageable set of cost packages that combine material spend, a credible operational question and an owner able to act. Use the first cycle to prove the connection between the baseline, the operating choice and the budget. Expanding a weak process across the whole company only increases the reporting burden.

The leadership discussion should end with a short decision record. Where evidence is missing, assign the question and a return date. Where a trade-off is accepted, record the service implication as well as the financial target. Where investment is needed, make the dependency explicit before committing to the benefit.

A useful ZBB programme leaves behind more than a smaller spending plan. It establishes a repeatable way to question demand, make resource choices and hold the organisation to them. The enduring result is the ability to fund priorities deliberately, rather than inherit them from last year’s budget.