What does it mean that team capacity planning?

When working with others collective capacity must be managed as carefully as individual capacity.

Example: A four-person product team calculates their collective capacity at 160 hours per week — four people times forty hours each. They commit to a project plan built against that number. Six weeks later, the project is three weeks behind schedule. A retrospective audit reveals the real arithmetic. Recurring meetings consume 22 hours per week across the team. Coordination — status updates, dependency handoffs, waiting for code reviews, clarifying requirements — accounts for another 18 hours. Context switching between shared workstreams costs roughly 12 hours in transition overhead. The team's effective collective capacity was never 160 hours. It was 108 hours at best, and on weeks with cross-team dependencies or unplanned incidents, it dropped to 80. They had committed to a plan that assumed twice the capacity they actually possessed. The project was not behind because the team underperformed. It was behind because the plan overestimated what four humans coordinating together could produce.

Try this: 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.