# Zero-based Organization: Justifying Structures from Scratch

Author: Marin Niehues, Niehues Consulting · Published: 2025-12-04 · Updated: 2026-11-16 · Organizational Design
Source: https://www.niehuesconsulting.com/blog/zero-based-organisation/

A zero-based organization justifies every unit, role and position afresh from the company's mandate, independent of the existing set-up. The approach transfers the logic of zero-based budgeting to the organization: every unit justifies its existence by the contribution it makes to delivery.

For the executive team it is an instrument for situations in which adjustments to the existing structure no longer suffice. A redesign usually changes positions and responsibilities and therefore touches the participation rights of employee representatives. This article provides an overview and does not constitute legal advice.

**Zero-based means that the company's mandate is settled before the structure is designed. Every unit and every role is assigned to a delivery outcome required by a customer or an internal objective.**

## What is zero-based budgeting in simple terms?

Zero-based budgeting is a budgeting method in which every expense is justified from zero in each budget cycle instead of rolling forward the prior-year figure. Traditional budgeting asks how much a line item should change compared with last year. Zero-based budgeting asks which activities are needed in the coming period and what they cost.

Peter Pyhrr developed the method at Texas Instruments and presented it in 1970 in an article in the Harvard Business Review. Jimmy Carter introduced it as governor in the budget of the state of Georgia and later as president in the US federal administration. In business, the approach became known above all through consumer goods groups that applied it to overheads in marketing and administration.

Zero-based organization transfers this logic from costs to structure. Instead of budgets, units and layers are justified afresh, down to the individual role. Both methods can be combined: the structural design provides the basis on which the units' budgets are built.

## The principle: from mandate to structure

In organizations that have grown over time, structures arise from specific occasions: an acquisition, a manager the company wants to retain, a project that became permanent. Each of these decisions made sense on its own. Taken together, they rarely produce what a design on a blank sheet would deliver.

Zero-based reverses the order. First the mandate is described: which services the company provides for which customers. The delivery processes follow from this, the tasks from the processes, and the roles and units from the tasks. Only at the end comes the comparison with the existing set-up, and every deviation receives a decision between adopting, adapting or dissolving. The article [Operating model](/blog/operating-model-before-structure/) describes which decisions precede the structural design. How the approach fits into organizational design as a whole is set out in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/).

## When is a zero-based organization worthwhile?

A zero-based organization is worthwhile when the company's mandate has changed and earlier adjustments to the existing structure have not improved delivery performance. Typical triggers are a new business model, an integration after an acquisition or the use of AI in core processes. A further signal: the structure can no longer be explained internally in one sentence, and coordination takes longer than the task itself.

A design from zero requires time and leadership attention. Where the mandate is unchanged and there are isolated bottlenecks, a targeted intervention at the bottleneck is the more economical choice. The article [Organizational design: when a restructuring pays off](/blog/organisation-design-when-restructuring-pays-off/) weighs it against smaller interventions.

**Checklist: signals for a zero-based redesign**
If at least three of the following statements apply, a redesign from zero is the right method. With one or two, a targeted intervention suffices.

- The company's mandate has changed significantly since the last structural decision.
- The same tasks are carried out in parallel in several places.
- Decisions pass through more layers than the task requires.
- Earlier adjustments have not improved delivery performance.
- The share of overheads has grown without delivery performance growing with it.

## Pros and cons of a zero-based organization

The greatest advantage of a zero-based organization is the obligation to justify: every unit must demonstrate its contribution to delivery, and duplication that has built up over time becomes visible. In addition, costs are clearly assigned to outputs, and the structure reflects today's mandate while taking future changes such as the use of AI into account from the outset.

The disadvantages are just as clear. The effort is high, because managers have to describe processes and tasks they never had to justify before. The method unsettles employees as long as the goal is unclear. The weightiest criticism concerns short-termism: if zero-based is run purely as a cost program, spending whose benefit only becomes visible later disappears, such as investment in brands, capabilities or innovation. This very objection was discussed publicly in the case of consumer goods groups that applied zero-based budgeting with particular rigour.

The answer to this criticism lies in the yardstick. Every unit is justified against the company's mandate including its growth targets, beyond today's costs alone. Units that build future performance receive their own mandate with their own indicator in the design.

**Pros and cons compared**
Criterion | Zero-based as a cost program | Rolling forward the existing set-up | With Niehues Consulting
Justification | Every unit by its costs | Existing units are taken as given | Every unit by the mandate including growth targets
Effort | High, especially for management | Low | Focused on mandate, delivery processes and target structure with clear results
Risk | Short-term savings at the expense of future performance | Duplication remains | Future tasks with their own mandate and indicator
Acceptance | Low, as it is experienced as a cost-cutting round | High, but without effect | Managers help shape the design
Result | Lower costs for one cycle | Minor corrections | Implemented structure with delivery indicators

## The approach in four steps

In the first step, the executive team formulates the mandate: for which customers does the company provide which services, and which objectives apply for the coming years? This answer is the criterion for all further decisions. It also covers the question of which services will be delivered with AI in the future.

In the second step, the delivery processes are mapped from request to service. For each process, it is defined which tasks arise and what effort they require. The measure is delivery capability, meaning lead time and schedule reliability with assured quality.

In the third step, the target structure is designed. Tasks form roles, roles form teams, and teams are grouped into units whose shape follows the flow of delivery. For every unit it is settled which decisions it takes and which it escalates. Span of control and number of layers are derived from the task instead of being set as a number in advance.

In the fourth step, the design is compared with the existing set-up. Every deviation leads to a decision with a rationale and a timetable. This shows which parts of the design can be implemented immediately and which need a transition phase, for example because key knowledge rests with individuals or systems must first be adapted.

For a business unit, the path from diagnosis to completed detailed design takes four to six months. Implementation follows, and its duration is determined by the number of employees affected and the consultations with employee representatives.

## How much can a zero-based organization save?

The savings of a zero-based organization result from the difference between the effort the mandate requires and the effort the existing set-up ties up today. A robust figure therefore only emerges after the second step, once processes and tasks have been described. Blanket percentages before this step are expectations, not planning values.

The calculation follows three quantities: the effort per task from the design, today's effort for the same task in the existing set-up, and the one-off costs of the transition.

**Worked calculation: savings potential of a unit**
Example: an administrative unit currently ties up 60 full-time positions. The design derived from the mandate shows a need for 51 full-time positions, because three tasks are carried out in two places in parallel.

The difference is nine full-time positions or 15 percent of the unit. Part of this is reallocated to tasks the mandate newly requires, such as reviewing AI results.

Question for the executive team: which share of the difference should be saved, and which should flow into tasks that build future performance?

Whether the difference leads to savings or to a reallocation into growth areas is decided by the executive team on the basis of strategy. A business case sets the cost of change against the expected benefit, including productivity losses during the transition. The article [Reducing overhead without loss of performance](/blog/reduce-overhead-without-losing-performance/) shows how overheads can be cut without weakening delivery.

AI shifts the starting point further. When assistants or agents take over activities, roles and spans of control change. A design from zero takes this into account from the start, whereas rolling forward the existing set-up only reveals the shift once it shows up in costs and utilization.

## Typical obstacles in implementation

Three obstacles determine whether implementation succeeds.

The first obstacle is personalization. If the discussion starts with names, it ends in negotiations over vested interests. The target structure is therefore designed first for tasks and roles, and staffing follows in a separate step with its own criteria.

The second obstacle is a missing transition plan. Without one, the design remains a document. Every change needs an accountable person with a deadline. An indicator shows whether it works.

The third obstacle is how proven elements are treated. The design often confirms part of the existing set-up. These parts remain unchanged and count as justified, so that change concentrates on the places where it has an effect.

## Niehues Consulting as partner for the redesign

[Niehues Consulting](/) supports executive teams and heads of business units in redesigns from analysis to effective implementation. Marin Niehues works as a management consultant from a delivery perspective and builds organizations that deliver. His projects range from VC-funded scale-ups to DAX 40 corporations, with assignments in 20+ countries across six continents.

The approach follows the Niehues Delivery Model with the phases Understand, Build and Implement. For a redesign from zero, three of its review questions matter most. Which business outcome should change measurably? Which roles, decision paths and interfaces does operation require? Who owns operations from day one? Design and transition plan thus come from a single source, and Niehues Consulting steers implementation as delivery manager or project manager until the new structures work in day-to-day business.

The starting point is the free 30-minute initial consultation: [Book an initial consultation](/#kontakt).

**Recommendation for the executive team**
First check whether the company's mandate has changed. If it has, a design from zero provides the clearest basis, from the mandate via the processes to the structure. Measure every unit against the mandate including growth targets, so that today's savings do not weaken tomorrow's performance.

**Sources**
- Pyhrr: Zero-base Budgeting, Harvard Business Review, 1970

## Frequently asked questions

### What does zero-based mean for an organization?

Zero-based means that every structure down to the individual position is justified afresh from the company's mandate. The existing set-up serves as a benchmark, but it does not dictate the design.

### What is zero-based budgeting in simple terms?

Zero-based budgeting justifies budgets from zero in each budget cycle based on planned activities rather than the prior-year figure. Every expense must show which objective it serves. The method dates from the 1970s and is used today mainly for overheads.

### What is the difference between zero-based budgeting and zero-based organization?

Zero-based budgeting justifies spending afresh, while zero-based organization justifies structures and roles afresh. The two can be combined, because the structural design provides the basis for budgeting the units.

### What are the pros and cons of zero-based organization?

The main advantage is the obligation to justify every unit, which exposes duplication. The disadvantages are high effort for management and the risk of short-term savings at the expense of future performance. Measuring every unit against the mandate including growth targets limits this risk.

### How much can be saved with zero-based organization?

The savings potential results from the difference between the effort the mandate requires and today's effort in the existing set-up. A robust figure is available once processes and tasks have been described. Part of the difference usually flows into new tasks rather than into savings.

### Which companies have used zero-based approaches?

In business, zero-based budgeting became known above all through large consumer goods groups that applied it to overheads. In the public sector, Jimmy Carter introduced the method in the state of Georgia and later in the US federal administration. Companies of every size apply the transfer to organizational structure, often limited to one business unit.

### How long does an organizational redesign take?

For a business unit, the path from diagnosis to completed detailed design takes four to six months. Implementation follows and is determined by the number of employees affected and the consultations with employee representatives.

### Which companies is a zero-based design suitable for?

A zero-based design suits companies whose mandate has changed, for example through growth, integration or AI in core processes. In mid-sized companies as in large groups, the design can be limited to one area, such as a function or a site.
