When to centralize and when to federate

A recurring organizational question: do we centralize a function — one team owns it for everyone — or federate it, letting each team handle its own? Both have failure modes. Centralize the wrong thing and it becomes a bottleneck. Federate the wrong thing and you get chaos and duplication.

Centralize for consistency, federate for speed

Centralization wins where consistency and standards matter more than local speed — think security, core data, brand. Federation wins where local context and responsiveness matter more than uniformity. The mistake is applying one model everywhere out of habit.

A practical test

• Does this need to be consistent across the whole org? Lean central.
• Does local context change the right answer a lot? Lean federated.
• Is the central team becoming everyone's bottleneck? Federate with guardrails.
• Is federation causing five incompatible versions? Centralize the standard.

Centralize what must be consistent. Federate what must be fast. Most pain comes from getting these backwards.