# Breaking Down Silos: Designing the Interfaces between Functions

Author: Marin Niehues, Niehues Consulting · Published: 2024-12-26 · Updated: 2026-11-16 · Organizational Design
Source: https://www.niehuesconsulting.com/blog/breaking-down-silos/

Silos break down when the interfaces between functions share a goal and decision rights as well as handovers are set out in binding terms. Appeals for collaboration do little against a silo mentality while the structure behind it stays the same. This article sets out the causes, a calculation of the cost and a three-step approach.

## What is the silo mentality and where does the term come from?

The silo mentality describes an attitude in which functions pursue their own goals first and let responsibility end at their own boundary. The image comes from the grain silo, in which each type of grain is stored strictly apart from the others. It entered management language through the American industrial manager Phil S. Ensor, who described the "functional silo syndrome" in 1988 in the journal of the Association for Manufacturing Excellence. Since then, the term has stood for organizations whose functions work side by side without jointly owning the result for the customer.

The silo mentality is rarely a question of character. It is the rational response of people to a structure that rewards them for functional results. Anyone who wants to change the behavior therefore changes the structure first.

## Why do silos form?

Silos form through specialization, reinforced by functional targets and a lack of accountability for results across functional boundaries. Each function optimizes what it is measured on. Sales pursues revenue, production pursues utilization, IT pursues system stability. Each of these goals is legitimate. Together they create conflict as soon as a service passes through several functions and nobody owns the result for the customer.

There is also a structural effect, described by the computer scientist Melvin Conway in 1968: organizations design systems whose structure mirrors their own communication structure. Separate functions build separate systems, and separate systems in turn reinforce the separate functions. Silos thus stabilize themselves as long as nobody designs the interfaces deliberately.

## What are the disadvantages of silos?

Silos cost lead time above all and tie up leadership in arbitration. The costs show at the edges of the functions. In processes that span several functions, waiting time at handovers regularly accounts for the larger share of lead time, often a multiple of the actual processing. Information is captured several times because systems and responsibilities do not fit together. Decisions move upwards because nobody at the level below may speak for both sides. Executive management becomes the arbitration body for questions a well-designed handover could resolve itself.

The loss can be made visible with a simple calculation. It sets pure processing time against total lead time, a measure that lean management calls flow efficiency.

**Calculation: flow efficiency of an order**
Worked example for a customer order from sales to delivery:
- Step 1: Record the processing time for each function involved, meaning the time someone actively works on the order. In the example: sales 1 day, order clarification 0.5 days, engineering 2 days, production 1.5 days, 5 days in total.
- Step 2: Measure total lead time from order receipt to delivery. In the example: 25 working days.
- Step 3: Flow efficiency = processing time divided by lead time. In the example: 5 divided by 25, i.e. 20 percent.
- Step 4: Assign the 20 days of waiting time to the handovers. The two handovers with the longest waiting time are the first candidates for an interface agreement.

The calculation shifts the discussion. As long as each function sees only its own processing time, it appears efficient. Only the measured waiting time between functions shows where the service to the customer is lost.

**Silos are a design problem at functional boundaries. They dissolve when every important interface has an accountable owner and a measurable service.**

## Four Interface Types, Four Design Questions

Each interface type needs its own solution. An analysis distinguishes four types, because each raises its own question.

**The four interface types**
- Work handover: one function delivers a result to the next. The design question is what is handed over, in what quality and by when.
- Decision: two functions have legitimate interests in a matter. The question is who decides and who is consulted.
- Information: one function holds knowledge or data that another needs. The question is who maintains the source and who may use it.
- Resource: several functions draw on the same specialists or budgets. The question is which rules govern prioritization.

Most friction arises at work handovers and decisions. Information interfaces can be solved technically once responsibility for the source is settled. Resource conflicts need a prioritization rule that applies above the functions concerned.

## Design Principles for Effective Interfaces

Four principles have proved their worth.

The first principle is a shared goal along the value stream. When several functions contribute to the same customer service, that service needs a metric they all own jointly, such as lead time from order to delivery. Functional targets remain but rank below the shared goal.

The second principle is the interface agreement, known in IT as an internal service level agreement. It records what one function commits to another:

- the service and its quality criteria
- the deadline within which it is delivered
- the contact person on each side
- the procedure if the commitment is not met

Such an agreement replaces the appeal with a verifiable arrangement. It fits on one page, is developed jointly and reviewed at a fixed interval.

The third principle is clear decision rights. Where two functions are affected, the matter needs a decision rule that defines in advance who decides and who must consent. Available models and their limits are shown in [Clarifying decision rights](/blog/decision-rights-raci-rapid/).

The fourth principle concerns incentives and composition. Anyone measured against goals that run counter to collaboration cooperates only as long as it costs nothing. At least part of the goals and the appraisal therefore depends on the shared result. Where collaboration must stay close permanently, a mixed team is the right answer.

**Which instrument for which situation**
Criterion | Interface agreement | Cross-functional team | With Niehues Consulting
Suited to | few, clearly delimited handovers | permanently close coordination on one customer service | choice per interface based on measured waiting time
Intervention in structure | low, reporting lines stay | medium, people change assignment | as little as possible, as deep as necessary
Time to effect | a few weeks | one to two planning cycles | first effect at two visible interfaces
Anchoring | periodic review of the agreement | shared goals and leadership | metrics in reporting, agreements in target agreements

## What role does leadership play in breaking down silos?

Leadership decides whether silos break down, because only leadership can change goals and decision rights across functional boundaries. Executive management has three tasks. It sets a shared goal for every cross-functional customer service and tracks it in reporting. It declines to arbitrate individual cases for which an interface agreement provides a rule and refers them back to the rule. And it composes the leadership team so that functional heads are also measured on the overall result.

Functional heads in turn negotiate the interface agreements themselves and stand by their commitments. A leadership team that sees itself as a round of functional representatives reproduces silos at the top.

## The Approach: From Interface Map to Operation

A project to dissolve silos runs in three consecutive steps.

The first step is the interface map. For two or three core services it shows which functions are involved, where handovers occur and how long they take. The map is built together with those involved and draws on measured lead times and the number of escalations. It directs attention to the points of greatest loss.

The second step redesigns the most important interfaces. For each, the type is determined and an interface agreement drafted. A decision rule and a shared metric are added. Starting with two interfaces whose effect is visible to everyone, and evaluating the results after one cycle, has proved effective.

The third step anchors the solution in operation. The metrics go into regular executive reporting, the interface agreements into the target agreements of functional heads. A named person maintains the interface map and convenes a review every six months. Without this anchoring, the old patterns return, at the latest in the next target-setting cycle. How interfaces fit into organization design as a whole is shown in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/).

## Niehues Consulting as Partner for Breaking Down Silos

Breaking down silos is a delivery project with a clear goal: services should cross functional boundaries faster and more reliably. [Niehues Consulting](/) supports executive and business-unit leaders in this project. In delivery management and organization design, roles and decision paths are created that make interface agreements binding. Marin Niehues steers the work as delivery manager, project manager or product owner and reports measured results to executive management. For AI projects that touch several functions, AI management together with operationalisation and implementation ensures that applications arrive in operation across functional boundaries.

The approach follows the Niehues Delivery Model with the phases Understand, Build and Implement. Three review questions matter most for silos. In Understand: who decides, who delivers, who uses? Also in Understand: what is the baseline, and how do we measure success? In Build: which roles, decision paths and interfaces does operation require? The experience comes from projects at VC-funded scale-ups and DAX 40 groups in 20+ countries on six continents. The entry point is a free 30-minute initial consultation via [the contact page](/#kontakt).

**What decision-makers should define**
Anyone who wants to dissolve silos starts where services cross functional boundaries and measures the waiting time there. Every important interface gets a shared goal and an interface agreement with a decision rule. The metrics belong in executive reporting so that the solution outlasts the first cycle.

**Sources**
- Conway, Melvin E.: How Do Committees Invent?, Datamation, 1968
- Ensor, Phil S.: The Functional Silo Syndrome, AME Target, Association for Manufacturing Excellence, 1988

## Frequently asked questions

### What are silos in an organization?

Silos are functions that pursue their own goals first and work with other functions only through loosely regulated handovers. They arise through specialization and functional targets as well as a lack of accountability for services that pass through several functions.

### How do you recognize silos in a company?

Executive management recognizes silos by long waiting times at handovers and by decisions that escalate regularly. A revealing measure is the lead time of a service across several functions compared with pure processing time.

### How do you break down silos?

Silos break down when interfaces are designed. This includes a shared goal along the value stream and an interface agreement between functions, together with clear decision rights. The solution holds when metrics and target agreements are adjusted.

### What is an interface agreement between departments?

An interface agreement is a written arrangement between two functions on the service and deadline of a handover. It names contact persons on both sides and the procedure for deviations. In IT, the same instrument is called an internal service level agreement.

### Do cross-functional teams help against silos?

Cross-functional teams help where several functions work closely and permanently on the same customer service. For few, clearly delimited handovers, an interface agreement is sufficient. The team needs a shared goal and a lead with decision rights, otherwise it becomes a new silo.

### Does a matrix organization help against silos?

A matrix organization helps against silos when decision rights between the axes are clearly regulated. Without that rule, the matrix merely moves the conflict into every single decision. When the matrix works is described in [Matrix organization: when it works and when it paralyses](/blog/matrix-organisation-when-it-works/).

### How long does it take to break down silos?

The first interfaces can be redesigned within a few weeks if the project starts with two services whose effect is visible to everyone. Anchoring in reporting and goals takes at least one planning cycle.
