Organizational Design

Reducing Complexity: Products, Processes, Structures

Marin Niehues13 November 202511 min read

A hand pointing at a roadmap on a whiteboard

Complexity falls for good when a company tackles it at the source: in product companies first with the variants in the range, in service firms with customer exceptions and special processes. Processes and structures then follow the streamlined offer. The reverse order brings only short-term relief: anyone who first slims down committees and removes approvals leaves the drivers untouched, and complexity grows back. This article shows how to make complexity costs visible, which methods work and how the executive team steers the reduction with metrics.

Where complexity arises in a company

Complexity arises at the interface between offer and organization. Every additional product variant and every customer exception creates work in several places. The same applies to every new segment: sales gains another configuration case, production another changeover, service another spare part, controlling another reporting line. Each of these decisions seems reasonable on its own. Taken together, they produce an operation that needs more coordination for every order than the year before.

For management purposes the distinction by value is what counts. Value-adding complexity is paid for by the customer because it creates benefit, for example a variant for a distinct market segment. Value-destroying complexity creates cost and waiting time without any customer paying for it, and it arises in the market as well as internally. The literature also distinguishes by origin: external complexity is triggered by the market, for instance through customer requirements or regulation, while internal complexity is created by the company itself through its decisions about offer and processes. A program aims to reduce value-destroying complexity and to keep value-adding complexity deliberately. The article characteristics and metrics of a high-performing organization shows how this reduction fits into organizational design as a whole.

Complexity must be distinguished from complicatedness. A complicated system has many parts but behaves predictably and can be fully understood through analysis, like a clockwork. A complex system changes through the interactions of its parts, so its behavior is only partly predictable. In business practice, reducing complexity means lowering the number of variants and interfaces so that fewer interactions arise that nobody can oversee any longer.

What are complexity costs, and how are they calculated?

Complexity costs are all costs caused by the variety of variants, customer exceptions and special processes that would disappear with a uniform offer. They include one-off costs for development and master data set-up as well as ongoing costs for changeovers and inventory. On top come knock-on costs in the form of longer lead times and more frequent errors.

Conventional overhead-rate costing spreads this effort across all products and so conceals it. A low-volume variant then appears cheaper than it is, because it carries the same overhead rate as the volume product. Activity-based costing makes the effort visible by assigning the cost of activities to the variants that trigger them.

For a first overview, the four to six activities with the highest effort are enough. Full activity-based costing follows only once the decision on individual variants is finely balanced.

Products: pruning the variant portfolio

Variant management is the steering of variety across the entire life cycle of an offer. It pursues three goals: avoiding new variants that add no value, reducing existing variants and handling the remaining variety so that it causes little effort.

The first step creates transparency. For each variant, the contribution margin is determined along with the complexity costs it causes in downstream areas. Together these values form a four-field matrix. Variants with high contribution and low effort stay. Variants with high contribution and high effort are simplified, for example through modularisation or standard configurations. Variants with low contribution and low effort are phased out or offered only to order. Variants with low contribution and high effort are discontinued.

What matters is who decides. A product portfolio that each division maintains for itself grows on its own. It needs one person with overall accountability who introduces and ends variants, and a fixed rule: for every new variant an old one is phased out, or a proven business case is in place. Communication with customers is part of the plan: for every variant being phased out, a successor offer is ready.

In service firms the source lies elsewhere. There, variety arises from individual contract terms and special reports introduced for single customers. The matrix works the same way: each exception is compared with the customer's revenue and the effort it causes.

Which methods reduce complexity?

Five combinable methods do most to reduce complexity. Which one comes first depends on the level at which the drivers sit.

Modularisation breaks a product down into modules with fixed interfaces from which many variants can be assembled. Variety for the customer remains while the number of parts falls. A platform strategy goes a step further and uses a common technical base for several product lines. Late differentiation, also known as postponement, moves the point at which variants diverge as far towards the end of the process as possible, so that planning and production work with uniform preliminary stages for a long time.

Aligning processes and structures with the smaller offer

Once the offer has been streamlined, processes stand out more clearly. Many have grown around exceptions: an approval step was introduced after a single incident and has applied to every case ever since. The clean-up starts with a standard process for the large majority of cases. Exceptions run in a separate, clearly named path. For each step, the question is which error it prevents and how often that error occurs. Steps that prevent a rare error move into the exception path.

Where a process actually loses time is shown by bottleneck analysis. The approach is described in the article on finding bottlenecks in value creation.

Structures follow processes. When a standard process lies in one pair of hands, interfaces disappear. Three questions reveal where the structure creates complexity:

  • Handovers: how often does a case change hands before it is completed?
  • Duplication: which tasks are performed in parallel by several divisions?
  • Decision paths: how many layers does a decision pass through?

The answers show which accountabilities should be pooled. The operating model frames the structural decision because it defines how services are delivered. The article on the operating model explains this sequence.

Sequencing and steering the reduction

A complexity program needs a sequence and a rhythm. A three-wave approach has proved its worth. In the first wave, transparency on complexity costs is created and the portfolio decisions are taken. In the second wave, the processes of the affected value streams follow. In the third wave, those structures are adjusted for which it has by then been shown that the work has gone. Each wave closes with a decision by the executive team before the next begins. This prevents processes from being optimized around products that are later phased out.

Steering relies on a few metrics that measure success in delivery:

  • Active variants per product line
  • Lead time from order to delivery
  • Share of cases in the standard path
  • Handovers per case

If the reduction is run as a pure cost program, the incentive is to cut posts while complexity stays. The result is overload. How overhead can be cut without damaging performance is covered in the article on reducing overhead without loss of performance.

Niehues Consulting as a partner for complexity reduction

Niehues Consulting supports complexity programs from a delivery perspective. Founder Marin Niehues is a management consultant who builds organizations that deliver. His projects range from VC-funded scale-ups to DAX 40 corporations, and he has been deployed in 20+ countries on six continents.

The approach follows the Niehues Delivery Model with its phases Understand, Build and Introduce. In the Understand phase, complexity drivers and current processes are captured, guided by the question of the baseline and how success is measured. In the Build phase, the target picture and standard processes are developed, and the review question is which roles, decision paths and interfaces future operations require. In the Introduce phase, the organization implements until those involved are enabled and processes are adapted. The entry point is a free 30-minute initial consultation: request an initial consultation.

Frequently asked questions

What does complexity mean in a business?

Complexity describes the effort caused by the variety of products and the design of processes and structures. It shows up in rounds of coordination and long lead times. Complexity that customers pay for is benefit, while value-destroying complexity creates cost without return.

What is the difference between complexity and complicatedness?

A complicated system has many parts but behaves predictably and can be fully understood through analysis. A complex system changes through the interactions of its parts and is only partly predictable. Complexity reduction lowers the number of variants and interfaces and with it the interactions.

What are complexity costs and how do you calculate them?

Complexity costs are the costs caused by variety that would disappear with a uniform offer, for example for changeovers and inventory. They are calculated with activity cost rates: the cost of an activity divided by the number of times it is performed, multiplied by how often each variant triggers it. Conventional overhead-rate costing conceals these costs.

What is variant management?

Variant management is the steering of product and service variety across the entire life cycle. It avoids variants without added value, reduces existing ones and handles the remaining variety with as little effort as possible. Its central tool is the assessment of every variant by contribution margin and complexity costs.

What methods are there for reducing complexity?

The most effective methods include the variant matrix and modularisation. Platform strategy and late differentiation add to them, both preserving variety for the customer while reducing the number of parts. In processes, a standard path with a separate exception path is effective.

Where should a company start reducing complexity?

At the source: in product companies with the variants, in service firms with customer exceptions and special processes. Once the offer is smaller, processes and structures can be tailored to what remains. Conversely, new work arises as soon as new variants are added.

How do you measure the success of a complexity program?

With delivery metrics: active variants per product line, lead time from order to delivery, share of cases in the standard path and handovers per case. If these values fall while delivery reliability stays stable or improves, the reduction is working.

Is complexity reduction the same as cost cutting?

Complexity reduction tackles the causes of cost and waiting time, while cost cutting tackles the effect. A cost program without intervention in variants and exceptions brings short-term relief, but the work returns.

Let’s talk about your initiative.

In 30 minutes we clarify where your organization stands and which step will pay off most now.

Request a consultation

30 minutes · free · no obligation