Collaboration is useful when it moves a decision or unblocks work. It becomes overload when people spend more time keeping one another informed than delivering the outcome.
A 2021 Harvard Business Review report reported that collaborative work had risen by 50% or more over the preceding decade and occupied 85% or more of most people's workweeks. Those figures describe that report's findings, not a universal measure of every team today.
Brooks' Law is a coordination-risk heuristic: adding people to a late or complex project can add communication cost faster than it adds capacity. A group of 50 people has 1,225 potential communication pairs, so a staffing decision needs a clear coordination design behind it.
Identify the real constraint
Start with the work that is late, error-prone, or repeatedly escalated. Is the constraint a missing skill, an unclear decision, an overloaded system, or a handoff that no one owns? Hiring more people before answering that question can make the bottleneck harder to see.
Assign decision ownership and a written record
Name the person accountable for each consequential decision, then record the context, decision, and next action where affected people can find it. A written record turns repeated status conversations into a reference point and gives teams room to act without waiting for another meeting.
Remove or automate work before hiring
Eliminate approvals, reports, and handoffs that do not change an outcome. Automate the repetitive work that remains. This protects the team from coordination debt and makes any true capacity gap easier to quantify.
Define interfaces and escalation paths
Before adding people, a new team, or another coordination layer, define what each group owns, the inputs and outputs it provides, and when an issue should escalate. Clear interfaces let teams coordinate intentionally instead of pulling everyone into every decision.
Read next
- When headcount seems like the answer, read Why Hiring Should Be Your Last Growth Lever.
- To replace constant status chasing with better systems, read Stop Managing Async Teams Like They're In the Office.
- To give teams enough authority to use those interfaces, read Decentralization Isn't Autonomy Without Power.