Knowledge
Knowledge HubConcepts and strategic researchGlossaryDefinitions across six domainsFrameworksStructured strategy methodsTopicsConnected subject areasLibrary
PlaybooksPractical strategy guidesBooksBooks and long-form researchOperator VaultMember resources and toolkits
Explore Discover, the Knowledge Hub, playbooks, and the Operator Vault.
Glossary
Coordination costs
Coordination costs are the time, attention, error, and delay incurred when organizational actors align interdependent work — meetings, handoffs, rework, waiting, and governance overhead inside a firm or collaborative network. They arise from interdependence among people and teams, not only from buying something in a market.
Why it matters
Strategy and architecture choices reshape who must coordinate with whom. Digital tools and AI can lower some coordination costs for cognitive work while raising others (more stakeholders, more parallel streams, more exception handling). Capability-oriented firm design treats coordination costs as a first-class design variable.
Distinguish coordination costs from transaction costs. Transaction-cost economics focuses on the costs of defining, negotiating, monitoring, and enforcing exchanges — especially across firm boundaries — and on make-versus-buy. Coordination costs emphasize getting interdependent actors to act coherently. The concepts overlap (internal transfer pricing, supplier integration), but they are not interchangeable labels.
Example (enterprise): A global manufacturer centralizes pricing analytics in a shared center of excellence. Transaction costs with external data vendors fall, but coordination costs rise as regional teams wait on a queue and renegotiate exceptions weekly. Leadership redesigns service levels and local decision bands so coordination load matches the interdependence that actually requires a central team.
Mechanisms
- Map critical interdependencies and the meetings, queues, and handoffs they generate.
- Reduce unnecessary interdependence (interfaces, modularity, clearer decision rights) before adding coordination rituals.
- Invest in shared standards, platforms, and agent/tooling where they measurably cut alignment delay — and measure the new exception load they create.
Boundaries
- Coordination costs ≠ transaction costs; the former center on aligning interdependent actors, the latter on arranging and governing exchanges (often across boundaries).
- Lower tooling cost ≠ automatically lower coordination cost if interdependence and exception volume rise.
- Coordination cost is not only “too many meetings”; waiting, rework, and unclear ownership are coordination costs too.
Related topics
None linked yet.