What goes wrong when you ignore that team capacity planning?

The most common reason fails: Planning team output by summing individual capacities without accounting for coordination costs. This is the most common failure in team capacity planning and it is nearly universal. The math feels correct — four people, forty hours each, 160 hours total. But the math ignores the fact that coordination is not free. Every person added to a team adds not just capacity but communication overhead, dependency chains, and synchronization costs. The resulting plan looks reasonable on paper and fails reliably in practice, leading teams to blame execution when the problem was estimation.

The fix: Identify a team you currently work with — a project team, a department, a household managing shared responsibilities, or any group that coordinates to produce output. List every person and their estimated individual weekly capacity (use the measurement from L-0962 if available, or a conservative estimate). Sum those numbers. Now subtract: total hours in recurring meetings, estimated hours spent on coordination and communication per person per week, average hours waiting for dependency handoffs, and context-switching overhead for shared work. Write the resulting number down. Compare it to the theoretical sum. Calculate the coordination tax as a percentage. If the tax is below 20%, you are probably underestimating. If it is above 50%, you have a structural problem worth examining.

The underlying principle is straightforward: When working with others collective capacity must be managed as carefully as individual capacity.