Coordination Neglect
The tendency to underestimate the time and effort required for coordination when planning multi-person projects.
Also known as: Collaboration overhead bias, Integration neglect
Category: Cognitive Biases
Tags: cognitive-biases, planning, collaboration, project-management, teams
Explanation
Coordination Neglect is a cognitive bias where people systematically underestimate the overhead required to coordinate work across multiple people, teams, or organizations. When planning projects, we tend to estimate task durations as if each person works independently, forgetting the significant time consumed by communication, synchronization, conflict resolution, and handoffs.
## How it manifests
- A manager estimates a project by summing individual task durations without accounting for meetings, email chains, and alignment sessions
- A team leader adds more people to a late project, not realizing the coordination costs will initially slow things down (Brooks's Law)
- Planning assumes smooth handoffs between teams when real handoffs require extensive communication
- Estimates treat parallel work as truly parallel, ignoring dependencies and blocking waits
## Why we fall for it
- **Task focus**: we think in terms of individual tasks, not the glue between them
- **Invisible work**: coordination activities feel like overhead, not 'real work', so they get omitted from plans
- **Small team experience**: our intuitions about coordination come from small groups where it's cheap, but costs grow nonlinearly with team size
- **Component bias**: we estimate components in isolation, then sum them without integration costs
## The math behind it
Brooks observed that communication channels grow as n(n-1)/2 where n is the number of people. A team of 5 has 10 channels; a team of 10 has 45; a team of 20 has 190. Each channel represents potential coordination cost.
## Countermeasures
- **Explicitly budget coordination time**: add 15-30% for multi-person projects
- **Reduce coordination needs**: design work to minimize dependencies through modular architecture and clear interfaces
- **Track coordination costs**: measure time spent in meetings, on email, and waiting for others
- **Small, autonomous teams**: keep teams small to limit communication channels
- **Clear ownership**: reduce ambiguity about who decides what
Related Concepts
← Back to all concepts