Home > Perspectives > Strategy Execution > Leadership Beyond Organisational Charts

Leadership Beyond Organisational Charts

Watch the short film

Play Video
Leadership beyond organisational charts: what a survey of 350 companies says about how decisions actually get made and who makes them.

The finding

Paul Rogers and Marcia Blenko, both then leading Bain & Company’s Global Organization Practice, surveyed executives at more than 350 global companies and published the results in Harvard Business Review. The headline figure is worth sitting with: only around 15% of those surveyed said they worked in an organisation that helps the business outperform its competitors. The other 85% were, in effect, describing organisations whose structure was not actively working in their favour — and in most cases, that structure looked entirely conventional on paper.

The org chart those companies used to explain themselves to new hires, investors and each other told a story of clean lines and clear reporting relationships. What it didn’t capture was where decisions genuinely got made, revisited, or quietly stalled. Rogers and Blenko’s research located decision-making bottlenecks at four recurring points: between global and local levels, between the centre and the business unit, between one function and another, and between internal teams and outside partners. None of those four sits on a reporting line. All of them sit between boxes, in the white space the chart doesn’t draw.

That the figure sits at roughly 15% rather than closer to zero is itself informative. It suggests this isn’t a mark of poorly run organisations specifically — the survey covered large, established global companies, presumably with reasonably competent leadership by most conventional measures. The gap between org chart and decision reality appears to be closer to a default condition of scale than a failure specific to any particular company culture or leadership team.

What it means in practice

Consider an organisation where a team receives seven objectives for the quarter, each one described as critical by a different senior stakeholder. On the org chart, every one of those stakeholders has a legitimate claim — they each head a function the team reports into indirectly, or supports directly. The team has capacity for perhaps four of the seven. When they ask which three should wait, each stakeholder is willing to concede that theirs could — but none of them has the standing to make that call for someone else’s priority.

This is not a resourcing problem in the way it first appears. It is a structural one: the organisation has delegated prioritisation downward, to people without the authority to actually prioritise between claims that sit above their own reporting line. The chart shows who the team reports to. It does not show who has the authority to tell one stakeholder their objective is waiting. In many organisations, nobody formally does — and the org chart’s tidy hierarchy quietly implies that someone must, which is part of why the gap goes unnoticed for so long.

Jay Galbraith’s work on organisation design, published in Interfaces, offers a useful lens on why this happens as organisations grow. His argument was that organisational form should track the amount of uncertainty a task involves — as uncertainty rises, more information has to move sideways between people and functions for decisions to get made well. A hierarchy is efficient at moving information up and down. It was never designed to move it sideways, and most organisations don’t build a deliberate substitute; they let it happen informally, through relationships, until the informal version stops keeping pace with growth.

Looking for your own sector? The Other Sectors page points to the closest match.

Questions worth considering

  1. Where in the organisation does the decision to not do something actually get made — and is that the same place the org chart implies it should be?
  2. When two reasonable priorities compete for the same team’s time, who currently has the standing to choose between them?
  3. How would a leadership team know if that authority had quietly gone missing, rather than simply being hard to find?

This perspective is part of Strategy Execution.

Your team is facing similar challenges?

Why Do We Do It This Way? — leadership alignment beyond the org chart
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

Jay R. Galbraith, “Organization Design: An Information Processing View,” Interfaces, 4(3), 1974, pp. 28–36.

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.

You need a PDF version for a meeting?

Frequently Asked Questions

Not on its own. Research published in Harvard Business Review found decision bottlenecks cluster at points the org chart doesn’t represent — between functions, between centre and business unit, between global and local — regardless of how cleanly reporting lines are drawn.
Because each priority is being judged in isolation by the person who owns it, not against the others competing for the same capacity. Without someone positioned to weigh them against each other, every request can be reasonable and the total still be unworkable.
It tends to become visible with scale, but the underlying issue — lateral coordination not tracking a hierarchy built for vertical reporting — can appear earlier, particularly in organisations that have grown quickly or through acquisition.
A resourcing gap means there isn’t enough capacity for the work. An accountability gap means capacity exists but nobody has the standing to decide how it’s allocated between competing claims — the two can look identical from inside a busy team.
Surveying executives at more than 350 global companies, they found that only around 15% said they worked in an organisation that helps the business outperform its competitors. The page reads the figure as suggesting the gap between chart and decision reality is closer to a default condition of scale than a failing of particular companies, since the survey covered large, established firms. The results were published in Harvard Business Review.
They sit between the boxes rather than on reporting lines. Rogers and Blenko located them between global and local levels, between the centre and the business unit, between one function and another, and between internal teams and outside partners. The chart tells a story of clean reporting relationships but does not draw this white space, where decisions get made, revisited or stall.
A hierarchy is efficient at moving information up and down and was not designed to move it sideways. Galbraith’s work in Interfaces argues that as task uncertainty rises, more information has to move between people and functions for decisions to be made well. Most organisations do not build a deliberate substitute, relying instead on informal relationships until those stop keeping pace with growth.
It can appear as duplicated work, as reasonable requests that together exceed what a team can deliver, or as competing versions of authority after an acquisition. The chart is not wrong so much as answering a different question: it shows who is accountable for a function, not where a cross-cutting decision gets resolved. The cost tends to be cumulative rather than sudden, with senior time spent re-litigating decisions the chart implied were settled.