Home > Perspectives > Leadership > Why Symptoms and Root Causes Get Confused in Growing Organisations

Why Symptoms and Root Causes Get Confused in Growing Organisations

Watch the short film

Play Video
Why symptoms and root causes get confused in growing organisations: what a survey of 350 companies says about diagnosing the real problem.

The finding

Paul Rogers and Marcia Blenko, both partners at Bain & Company, surveyed executives at more than 350 global companies and found that only about 15% described their organisation as one that helps the business outperform competitors. Their research located decision-making stalls at a small number of recurring bottlenecks — between global and local levels, between centre and business unit, between one function and another, and between an organisation and outside partners. What makes this finding useful is not the taxonomy itself, but what it implies: decision-making difficulty in a growing organisation is disproportionately structural, arising at the seams between parts of the organisation, rather than being evenly distributed or primarily a matter of individual capability.

Donald Sull and colleagues at MIT Sloan reached a related conclusion from a different angle. Studying more than 250 companies, they found the central execution problem was not vertical alignment — most organisations’ planning processes are sound — but cross-unit coordination, precisely the kind of seam Rogers and Blenko describe. Two independently conducted, large-sample studies converging on the same structural location is itself a notable pattern: when something goes wrong at the interface between parts of an organisation, the evidence suggests looking at the seam before looking at the people standing on either side of it. Neither study set out to test the other’s claim, and neither team appears to have been aware of the other’s specific finding when publishing; the convergence is a product of two different methodologies arriving independently at a similar structural conclusion, which is a stronger form of evidence than either finding would be alone.

What it looks like in practice

Consider an organisation where two directors, whose functions depend heavily on each other, have almost no regular contact and communicate mainly through their respective teams. The obvious explanation is a personality difficulty — two senior people who simply don’t get on.

Both describe the relationship as fine. Neither has any diary commitment involving the other. There is no shared objective linking their two functions. There is no forum below board level where both of them are ever present at the same time. The absence of relationship, in other words, is not something either of them is choosing. It is a structural fact: the organisation has created no occasion for these two interdependent roles to actually come together, and nothing about how either of them individually behaves would change that — a distinction worth holding onto, because it means the usual remedy of encouraging the two directors to “build a better relationship” addresses a symptom that was never really about the relationship in the first place.

Why this keeps getting misdiagnosed

The tendency to read this kind of gap as personal rather than structural is understandable, because a personal explanation is immediately actionable in a way a structural one is not — it suggests a conversation, a mediator, a relationship-building exercise. A structural explanation requires looking at the organisation’s design, which is a less familiar and less comfortable place to look, particularly for people embedded inside that same design.

Rogers and Blenko’s finding that only 15% of organisations see themselves as structurally set up to outperform suggests this kind of gap is common rather than exceptional — which itself argues against a purely personal explanation in most individual cases, since personality clashes are not that evenly distributed across 85% of large organisations. Where the picture genuinely varies is in how visible the structural gap is before someone looks for it directly: in some organisations, the missing forum is glaringly absent once named; in others, informal workarounds mask it well enough that the underlying structural gap can persist for years without anyone experiencing acute friction — until, as in this scenario, someone finally asks where two interdependent functions are actually supposed to meet, and finds no answer.

The workaround itself is worth noticing, because it is usually what keeps the underlying gap invisible for so long. Teams below the two directors typically develop informal routines to manage the coordination the structure fails to provide — a shared spreadsheet, a habit of copying the right person on emails, a junior staff member who happens to know both sides well enough to translate between them. These routines genuinely work, which is precisely the problem: they absorb the cost of the missing structure well enough that nobody higher up experiences the gap directly, and the two directors themselves can honestly report that things are fine, because from where they sit, they are.

For how this pattern presents in other kinds of organisation, see other sectors.

Questions worth considering

  1. For any two functions that depend heavily on each other, is there an actual forum where both are regularly present — or only an assumption that one exists?
  2. When a working relationship is described as “fine” between two people who rarely interact, what is that assessment actually based on?
  3. Would the seams Rogers and Blenko describe — global/local, centre/unit, function/function — map onto specific, nameable points in this organisation’s structure?
  4. What informal workaround is currently absorbing the cost of a structural gap, and what would happen if the person maintaining it left?

This perspective is part of Leadership.

Your team is facing similar challenges?

Pending Information — root cause
The Riddle Ledger, a brand of Zoom Riddle

Subscribe to The Riddle Ledger

Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.

Sources

Paul Rogers and Marcia W. Blenko, “Who Has the D? How Clear Decision Roles Enhance Organizational Performance,” Harvard Business Review, Vol. 84, No. 1 (January 2006), pp. 52–61.

Donald Sull, Rebecca Homkes and Charles Sull, “Why Strategy Execution Unravels — and What to Do About It,” Harvard Business Review, Vol. 93, No. 3 (March 2015), pp. 57–66.

You need a PDF version for a meeting?

Frequently Asked Questions

Because “fine” in this context often means the absence of overt conflict, not the presence of active coordination. Research on decision bottlenecks suggests structural gaps like this can persist indefinitely without producing visible friction, which is part of why they’re easy to overlook.
It can look identical from the outside. The distinguishing evidence is structural: whether any shared objective, forum, or regular occasion for contact actually exists — not how the individuals describe their relationship, which can be entirely sincere and still miss the underlying gap.
Both examined execution and decision-making across large samples of organisations and located the primary difficulty at the interfaces between parts of the organisation rather than within any single part — a structural rather than individual location, found by two separate research teams using different methods.
That’s outside what this article covers. The aim here is to describe why these gaps form and why they’re commonly misread, not to prescribe a specific response.
Surveying executives at more than 350 global companies, Paul Rogers and Marcia Blenko found that only about 15% described their organisation as one that helps the business outperform competitors. They located decision-making stalls at a small number of recurring bottlenecks, between global and local, centre and business unit, one function and another, and an organisation and outside partners.
Studying more than 250 companies, Sull and colleagues found the central execution problem was not vertical alignment, since planning processes are generally sound, but cross-unit coordination. The page describes this as the same kind of seam that Rogers and Blenko point to, and as a reason to look at the interface between parts of an organisation before the people standing on either side of it.
Because it is immediately actionable in a way a structural one is not, suggesting a conversation, a mediator or a relationship exercise. A structural explanation means looking at the organisation’s design, which is less familiar and less comfortable for people embedded in it. The page also argues that a gap this common is hard to explain through personality clashes, which are not so evenly distributed.
Informal workarounds often absorb the cost. The page mentions routines such as a shared spreadsheet, copying the right person on emails, or a junior colleague who knows both sides, which genuinely work and so keep the gap invisible to those higher up. The two directors can honestly report that things are fine, because from where they sit they are.