ORGANIZATION & GROWTH
Hiring is one of the most intuitive responses to overload. Sometimes additional headcount gives the existing problem more room to survive.
By Jeff Watt, SPHR
REAL
SITUATIONS.
BRIGHTER
OUTCOMES.
Hiring is one of the most intuitive responses to overload. The team is stretched. Work is late. Managers are doing too much. Customers are waiting. The obvious conclusion is that the organization needs more people. Sometimes it does. Sometimes the additional headcount gives the existing problem more room to survive.
Not all overload is the same. Volume overload: There is simply more necessary work than the current capacity can reasonably perform. Priority overload: The organization is trying to do too many things at once.
Role overload: Responsibilities accumulated around a person or function without being redesigned. Process overload: Too many steps, approvals, meetings, or handoffs consume capacity. Decision overload: Work waits because decisions are unclear, centralized, or repeatedly reopened.
These conditions can feel identical to the person experiencing them. The solution is not identical.
If a team has a clear process, clear roles, clear priorities, and enough demand to exceed capacity, additional staff can be exactly right. If the work is ambiguous, adding people creates more interfaces around the ambiguity. A manager who spends ten hours a week coordinating unclear handoffs may spend twelve after the team grows. A CEO who approves too many decisions may gain another person whose decisions also need approval.
The organization becomes larger without becoming easier to operate.
Busyness is evidence. It is not diagnosis. Before adding a role, look at the work itself. What work increased? What work should stop? What work is being repeated? What work is happening because another part of the organization is unclear? Where does work wait?
A surprising amount of overload is created by the architecture around the work rather than the amount of work.
A team grows around the way work has always been done. Nobody asks whether the workflow should still exist. The new role inherits tasks because somebody needs to do them, not because those tasks are the best use of the new capacity.
Six months later, the organization has another full-time position and the original bottleneck still exists. Redesign can feel disruptive. Hiring feels additive. But additions create their own complexity.
Before approving a new position, ask the leader to identify:
The goal is not to force a staffing reduction. It is to make sure the new role changes the system. If nothing moves, stops, or becomes clearer, the company may simply be layering capacity onto the current design.
Sometimes the organization truly lacks a capability: a controller, a sales leader, an experienced operations manager, a technical specialist. That is a capability decision. The business should be explicit about that because the role should then be designed around the capability it adds, not around the list of tasks nobody else has time to do.
The best new roles do more than absorb work. They change where decisions happen. They improve the quality or speed of execution. They let senior leaders stop doing lower-value work. They reduce dependence on informal heroics. They add a capability the strategy requires. If the new hire does none of those things, the organization should question whether it is adding capacity or merely distributing complexity across one more person.
More people can absolutely be the answer. But "we are busy" is not enough evidence to know that.
━━━━
CAPACITY & STRUCTURE IMPLICATIONS
◉ Identify the overload type
Volume, priority, role, process, and decision overload require different responses.
◉ Remove before adding
Clarify what stops, moves, simplifies, or changes before creating another position.
◉ Test the operating constraint
Ask whether the real bottleneck is headcount, role design, process, authority, or escalation.
◉ Price the complexity
Every new role adds interfaces, coordination, and management load along with capacity.
━━━━
RELATED ADVISORY
For organizations where rising workload may reflect real capacity needs, structural friction, poor role design, or decision bottlenecks.
A HIGHER CONVERSATION
A confidential conversation can help you gain clarity, test your thinking, and explore what’s possible.
