Organization Design

Centralization versus Local Knowledge

Get a working rule for which decisions belong in the middle and which belong at the edge, then learn why the honest unit of that choice is almost never a whole function, but one specific step inside it.

  • Advanced
  • 13 min total
  • 14 chapters

What decision this helps you make: Whether to hold a given call once for the whole company or many times near the work, and how to split it so you capture the scale without destroying the fit.

What this topic is

Centralization means holding a decision once, in one place, for the whole organization. Decentralization means holding it many times, close to the work. Both buy something real: the centre buys scale, consistency and bargaining power, and the edge buys knowledge that cannot survive the trip to the middle. The design question is never which is better in general. It is which specific decisions belong where, and the answer differs inside a single function.

Why it matters

This is the argument that recurs in every business every three years, usually framed as a values question about trust and empowerment, and it is not one. It is a comparison between the scale a central decision captures and the fit a local decision preserves, both of which can be estimated with numbers you already have. Companies that argue it as a philosophy oscillate: centralize, suffer the misfit, decentralize, suffer the fragmentation, and repeat, paying the transition cost each time.

Who should learn it

Operators running multi-site, multi-region or multi-product businesses, anyone building a shared function, and any founder deciding what the centre should be as the company grows past the point where they are the centre.

What you will understand

  • The four properties of a decision that determine where it belongs, and the two people use instead
  • Why local knowledge is often destroyed rather than transmitted by the act of reporting it[1]
  • How to compute the trade for a real decision, and why splitting the decision usually beats choosing a side
  • Why technology has no fixed direction here: some of it decentralizes and some centralizes[8]

Prerequisites

Common misconception

"Decentralized companies are faster and more entrepreneurial; centralized ones are slower and safer." Both halves are wrong often enough to be dangerous. A decentralized company can be extremely slow if every unit has to build its own version of a capability before it can act, and a centralized one can be very fast when the decision is made once by someone who does nothing else. The deeper misconception is that the choice is made at the level of a function. "Should purchasing be central?" has no answer. "Should the supplier negotiation be central while the item selection stays local?" has a good one, and it is usually yes.