# Cutting bureaucracy in companies: Streamlining rules and approvals

Author: Marin Niehues, Niehues Consulting · Published: 2025-11-20 · Updated: 2026-11-16 · Delivery & Steering
Source: https://www.niehuesconsulting.com/blog/reducing-bureaucracy-in-companies/

You cut bureaucracy in a company by assessing rules and approvals by risk and impact and assigning a clear decision-maker to every approval that remains. Rules almost always arise from a specific trigger, such as an error or a growth spurt. Over time the trigger is forgotten while the rule remains. This article shows how to recognize costs and causes and how a reduction succeeds with a screening grid and four levers.

The focus is internal bureaucracy: approvals, forms, reports and coordination rounds that a company imposes on itself. Statutory obligations remain; what is simplified is the internal route to meeting them. This article provides an overview and does not constitute legal advice. How the reduction fits into organizational design as a whole is described in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/).

## How do you recognize unnecessary bureaucracy?

You recognize unnecessary bureaucracy when a case waits far longer than it is worked on, and when an approval hardly ever changes the outcome. A case that takes one hour to process takes two weeks because it waits for signatures. The ratio of processing time to lead time is therefore the first metric. It can be collected per process with little effort and shows what share of the time is waiting.

A second indicator is queries. If cases regularly go back for clarification, the rule is unclear or responsibility is open. A third indicator is the rejection rate of an approval. A body that approves almost everything creates waiting time. Whether it reduces risk is shown by the counter-test: if the error or loss rate does not rise after delegation, the approval was dispensable. How lead times and bottlenecks can be found systematically is described in [Finding bottlenecks in value creation](/blog/finding-bottlenecks-in-the-value-chain/).

Three examples appear in almost every company with a few hundred employees or more:

- **Travel expense approval:** a train journey to a client needs the manager's signature and then a second check by controlling, although the travel policy and booking portal already set the limits.
- **Purchase approval below a threshold:** consumables worth a few hundred euros go through the same approval route as a capital investment, because there is no threshold.
- **Multiple signatures:** a contract or concept has five signatures, of which only one person owns the outcome. The rest confirm they have seen it.

**Every rule and every approval needs a nameable purpose, an owner and a metric. If any of these is missing, it is a candidate for review.**

## Typical causes of internal bureaucracy

Internal bureaucracy arises mainly from four causes that reinforce each other. The first is the single incident: after an error, a rule is created for everyone, including the many cases in which the error could never occur. The second is growth. Each new layer adds an approval stage that rarely disappears again. The third is unclear decision rights. Where no one decides unambiguously, everyone involved protects themselves by co-signing. The fourth is the missing expiry date. Rules are introduced and never reviewed, so the stock only grows.

How decision rights can be clarified is set out in [Clarifying decision rights](/blog/decision-rights-raci-rapid/), which compares the RACI and RAPID methods.

## How much does bureaucracy cost a company?

Bureaucracy costs a company the working time spent on approvals and reports, plus the value of the delay caused by waiting. A survey of more than 7,000 Harvard Business Review readers found that respondents spend an average of 28 percent of their working time on bureaucratic tasks, more than one day a week. The survey is not representative, but it shows the order of magnitude decision-makers are dealing with.

For your own company, a calculation replaces the estimate:

**Calculating the cost of an approval**
1. Count the cases per year that pass through the approval.
2. Measure the working time per case for request, review and queries, across everyone involved.
3. Multiply by the fully loaded hourly cost rate: this gives the direct cost.
4. Record the waiting time per case in days and value it, for example as deferred revenue, contractual penalties or downtime.
5. Add both and compare the total with the damage the approval demonstrably prevents.

An example shows the order of magnitude. A purchase approval runs 4,000 times a year, and each case ties up 30 minutes across all participants. At a fully loaded rate of 70 euros per hour, the direct cost is 140,000 euros a year before waiting time is valued. If the damage the approval demonstrably prevented in that period is lower, it costs more than it protects.

## A screening grid for rules and approvals

The grid consists of four questions answered for every rule and every approval. First: which risk does it cover, and how large is the potential damage? Second: how often does it actually lead to a correction or rejection? Third: who owns the outcome, and could that person take the decision themselves? Fourth: what does the waiting time cost, measured in delay and tied-up working time?

The answers produce a classification. High risk and frequent corrections argue for keeping the rule. Low risk and hardly any corrections argue for removal or delegation. Rules that originate in law, standards or customer requirements remain at their core; only the internal route to compliance is simplified.

**The rejection rate as a test**
Count for each approval, over a fixed period, how many requests were changed or rejected. An approval that remains unchanged across many cases is a candidate for delegation to the operational level or for removal. An approval with frequent changes shows that the requirements need to be stated more clearly in advance.

## Can you abolish the four-eyes principle?

You can abolish the four-eyes principle where it arose from internal habit, and keep it where it stems from supervisory law, internal audit or the internal control system. In regulated sectors such as banking and insurance, supervisors require segregation of duties for certain transactions. The internal control system assessed by statutory auditors also relies on separate approvals for payments and postings. A low rejection rate is intended here, because the control works by existing.

Outside these areas, the screening grid applies. A second signature on an 80-euro travel claim covers no risk that a sample check would not capture equally well. A proven substitute is the retrospective sample: cases below a threshold run without a second approval, and a fixed share is checked afterwards. Which obligations apply in a given case should be clarified with your legal department or internal audit.

## Four levers for leaner approvals

The first lever is removal. Rules without a recognizable purpose or current trigger are dropped before anyone works on their design. The second lever is delegation: decisions move to the level that has the knowledge and owns the outcome.

The third lever is standardization with thresholds. Up to a defined amount, the business unit decides itself; above it, the next level steps in. A threshold of this kind replaces many individual approvals with one rule. The fourth lever is automation. Where review steps follow fixed criteria, workflows and increasingly AI take over the pre-check, and people review the exceptions. [Process automation with AI](/blog/process-automation-with-ai/) shows where this lever is greatest.

The sequence follows impact. A step that is no longer needed is removed before anyone invests effort in automating it.

Cutting bureaucracy is not cost-cutting in the narrow sense. It reduces waiting and tied-up working time, and jobs rarely disappear as a result. Anyone who also wants to simplify products and structures will find the broader approach in [Reducing complexity](/blog/reducing-organisational-complexity/).

**Routes to streamlining compared**
Criterion | Across-the-board cut | Single rule reform | With Niehues Consulting
Starting point | Cost target | Complaints from individual units | Inventory with lead time and rejection rate
Selection | Same cut everywhere | Loudest voice | Prioritized by impact and risk
Decision paths | Unchanged | Unchanged | Decision rights and thresholds reordered
Durability | Stock grows back | Stock grows back | Grid also applies to new rules
Embedding | Instruction | Single project | Rollout with roles and ongoing measurement

## How long does a bureaucracy reduction program take?

A bureaucracy reduction takes three to four months for a defined unit and nine to twelve months for the whole company. It succeeds when run as an initiative with a target metric and timeline under a named owner, in three phases.

In the Understand phase, an inventory of a unit's rules and approvals is built within four to six weeks, with lead time and rejection rate as well as an owner for each entry. In the Build phase, the levers are applied to the entries with the greatest impact, first as a pilot in a defined unit over two to three months. In the Roll-out phase, the result is transferred to further units, with adjusted roles and a scheduled review of the thresholds. Lead times are measured continuously.

Two decisions determine success. The first concerns risk: leadership decides which risk it deliberately moves to a lower level and communicates this explicitly. The second concerns durability: new rules pass through the same grid as existing ones and receive a review date, otherwise the stock grows again.

## Niehues Consulting as a partner for leaner processes

[Niehues Consulting](/) in Düsseldorf runs streamlining initiatives from the delivery perspective. Founder Marin Niehues is a management consultant who builds organizations that deliver, in projects ranging from VC-funded scale-ups to DAX 40 groups and in 20+ countries on six continents, with his home base in the DACH region.

The approach follows the Niehues Delivery Model with the phases Understand, Build and Roll out. Three of its review questions matter most for cutting bureaucracy. In Understand: who decides, who delivers, who uses? Also in Understand: what is the baseline, and how do we measure success? In Roll out: are users enabled and processes adapted?

In delivery management and organizational design, Marin Niehues steers the initiative as delivery manager, project manager or product owner and reorders roles and decision paths. Where AI is to take over the pre-check, AI management supports the choice of application, and AI prototypes prove the value in the real workflow. The entry point is a free 30-minute initial consultation that places the lead times and approval routes of your unit in context: [Contact](/#kontakt).

**What decision-makers should retain**
Assess rules and approvals with a fixed grid by risk and impact, and calculate the cost of the largest approvals. Apply the four levers first to the entries with the greatest loss of time, and assign an owner to every remaining approval. Run the initiative in three phases and measure lead time continuously.

**Sources**
- Hamel, Zanini: What We Learned About Bureaucracy from 7,000 HBR Readers, Harvard Business Review, 2017

## Frequently asked questions

### How do you reduce bureaucracy in a company?

You record a unit's rules and approvals with lead time and rejection rate and assess them by risk and impact. Then you apply four levers: removal, delegation, standardization with thresholds and automation. A pilot in a defined unit shows the effect before the result is transferred.

### How much does bureaucracy cost a company?

In a survey of more than 7,000 Harvard Business Review readers, respondents reported spending an average of 28 percent of their working time on bureaucratic tasks. For your own company, multiply per approval the cases per year by the working time per case and the fully loaded cost rate. The value of waiting time comes on top.

### What are the typical causes of internal bureaucracy?

Typical causes are rules created after a single incident that apply to everyone, extra approval stages added through growth and unclear decision rights. Rules also lack an expiry date, so the stock is never reviewed.

### What are examples of unnecessary bureaucracy in a company?

Common examples are double approvals for travel expenses within the travel policy and purchase approvals for small amounts without a threshold. Multiple signatures where only one person owns the outcome are equally widespread, as are regular reports that no one uses for a decision.

### Can the four-eyes principle be abolished?

The four-eyes principle can go where it arose from internal habit, and stays where supervisory law, internal audit or the internal control system require it. A proven substitute below a threshold is the retrospective sample check. Clarify the applicable obligations with your legal department or internal audit.

### Which approvals can be removed or delegated?

Suitable candidates are low-risk approvals that rarely lead to changes across many cases. They move to the operational level that has the knowledge and owns the outcome, or are replaced by a threshold.

### How long does a bureaucracy reduction program take?

A bureaucracy reduction program takes three to four months for a defined unit and nine to twelve months for the whole company. The inventory is ready after four to six weeks, and the pilot runs for two to three months.

### How do you measure the success of cutting bureaucracy?

The key metric is the lead time of the affected processes relative to processing time. Added to this are the number of approval stages per case and the rate of queries. If these values fall without the error rate rising, the reduction has the intended effect.

### Is cutting bureaucracy the same as cutting costs?

Cutting bureaucracy mainly reduces waiting and tied-up working time, and jobs rarely disappear as a result. The time gained only turns into money when the organization uses it for more cases or better work.
