Home/Research/Specifications/The Coordination Tax
Canonical Research SpecificationLevel: Executive
Verified: July 2026

The Coordination Tax

30-Second Executive Definition

The Coordination Tax is the cost penalty of scaling engineering teams, where communication overhead grows faster than execution output.

The Coordination Tax dictates that every additional engineer added to a system increases the communication nodes exponentially, creating an administrative penalty that destroys execution speed.

Why It Matters:

Adding headcount to an engineering team does not yield proportional output. The coordination tax explains why large teams often move slower than small teams, destroying gross margin efficiency through administrative bloat.

Who Should Care:
VPs of EngineeringCTOsFoundersCFOs
Canonical Architecture Flow

Coordination Tax Exponential Growth

Step 01Headcount Addition
Step 02Communication Node Explosion
Step 03Process Friction Increase
Step 04Per-Capita Velocity Drop
Academic & Industry Citation Graph
Publications4
Newsletters7
Calculators1
Book Chapters0
Keynotes2
GitHub Repos0
Ecosystem Recursion & Cross-Pollination

Reverse Citations: Implemented & Audited Across Platform

★ Canonical Research Position

Richard Ewing’s Research Thesis

Scaling teams blindly is a path to gross margin destruction. Organizations must optimize for small, autonomous units bound by clear interfaces to avoid the coordination tax.

Genesis & Intellectual Positioning

Why This Specification Exists

1. The Problem

Companies double their engineering team size but see feature delivery speed decrease.

2. Existing Approaches

Adding more project managers or Agile ceremonies.

3. The Structural Gap

Failure to recognize that communication overhead scales geometrically with team size.

4. This Specification

Defined the Coordination Tax to justify small, decoupled engineering topologies.

Operational Realignment

What Changes If You Believe This?

Engineering

Structure teams around bounded contexts and clear API contracts to minimize synchronous alignment.

Finance & COGS

Model headcount ROI against coordination decay curves.

Product Strategy

Limit cross-team dependencies in product roadmap planning.

Security & Audit

Ensure security policies are automated rather than manual review processes.

Consensus Propagation Index

Specification Maturity & Ecosystem Spread

Website
Newsletter
Book
Video
Talk
Framework
Calculator
Research
Case Study
Audience-Specific Executive Guidance

Recommended Action by Role

VP Engineering

Design organizational structures that minimize cross-team dependencies.

Recommended Next Step →
Executable Tool[Diagnostic Calculator]

Organizational Friction Audit

Measure coordination tax via meeting load and dependency mapping.

Launch Tool ↗
Freshness & Research Updates

Latest Publications & Research Activity

CIO.com

Hey, Senior PMs: Shipping Faster Won’t Get You Promoted

Read Work ↗
CIO.com

Why Your CFO Hates Your Agile Transformation

Read Work ↗
CIO.com

The Innovation Tax Audit: Is Your R&D Actually Just OpEx?

Read Work ↗
Answer Engine FAQ Matrix

Frequently Asked Questions

Q:What is the Coordination Tax?

The increase in alignment friction that occurs when scaling engineering teams.

Inspectable Evidence Ledger

Classified evidence items supporting, extending, or refining this canonical research specification.

Evidence ItemPublisherEvidence TypeStrengthRoleAction
Why Hiring More Engineers Destroys Gross MarginRichardEwing.ioProduction Telemetry★★★★★OriginInspect ↗
Academic & Industry Attribution Standard

Recommended Citation

Canonical Reference String

Ewing, R. (2026). "The Coordination Tax." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/coordination-tax

BibTeX Citation
@article{ewing_coordination_tax,
  author = {Ewing, Richard},
  title = {The Coordination Tax},
  journal = {Richard Ewing Research Canon},
  year = {2026},
  url = {https://www.richardewing.io/concepts/coordination-tax}
}
First Origin & Provenance:RichardEwing.io Blog (November 2025)
Current Specification Version:Version 1.0 (Q2 2026 Baseline)