Introduction
I once sat in a project meeting where delivery was slipping, and tension was starting to build. The conversation moved quickly from missed milestones to a familiar conclusion.
“We just need a few more resources, and we’ll be fine.”
No one pushed back. Timelines were extended. Tasks were reassigned. On paper, it looked like progress. In reality, nothing had really changed.
That’s one of the most common traps in project management. When delivery starts to break down, the first instinct is often to add people. The assumption is simple: more people + more capacity = better outcomes. That’s not always how it works.
Adding people may close a staffing gap on paper, but it won’t fix unclear priorities, overloaded subject matter experts, decision bottlenecks, or a project system already strained before the new resources arrived.
Project managers don’t just manage tasks. We manage the conditions that allow work to move. When those conditions are broken, more people won’t automatically fix the project. They may simply inherit the same problems faster.
When Projects Expand, Work Multiplies
Most projects don’t fail because of one major issue. They drift. Scope expands, priorities shift, and new requests get layered on top of existing commitments. A stakeholder asks for “just one more thing.” A deadline moves. A dependency gets missed. A decision takes longer than expected.
Rarely does something get removed to make space.
The project plan may still look reasonable. The resource plan may still show coverage, and the status report may even stay green for a while. The people doing the work know the truth.
Attention starts to fragment. Meetings increase. Follow-ups multiply. Rework becomes normal, and key resources get pulled into too many conversations. The work’s technically moving, but it’s moving with more friction than the plan shows.
That’s where project managers have to pay attention. The plan tells one story. The behaviour of the team often tells the real one.
More People Can Increase Complexity
Adding resources can help when the work is clear, the process is stable, and the team truly doesn’t have enough capacity. Adding people to a messy system can make the problem worse.
New team members need onboarding, context, access, direction, decisions, and support. Someone still has to explain the history, risks, dependencies, tools, and workarounds that didn’t make it into the documentation. That takes time.
Every additional person also brings more communication paths, more handoffs, more meetings, more coordination, and more chances for misalignment. Before assuming the project needs more people, project managers should ask a better question: Is this a true capacity issue, or is the project system getting in the way of the work?
That distinction matters. A true capacity issue means the work is clear, the priorities are stable, decisions are moving, and the team still doesn’t have enough people to complete the work. A system issue means the work isn’t clear, priorities are competing, decisions are delayed, scope keeps shifting, or the same few people are carrying most of the unresolved work.
Those aren’t the same problem, and they shouldn’t receive the same solution.
High Performers Often Hide the Real Problem
One reason broken systems survive so long is that high performers keep them moving. They stay late, follow up, remember what others forget, connect dots across teams, and solve problems before they become visible. They quietly absorb pressure so the project doesn’t fall apart.
From the outside, this can look like resilience. In reality, it may be a warning sign.
If the same people are always saving the project, the project may be relying too heavily on individual effort to compensate for weak structure. That’s risky. When high performers become the safety net, leaders can mistake strain for stability. Status reports stay positive longer than they should, risks stay informal, and decisions get made in side conversations.
The project may appear to be under control, but that control is often being held together by people carrying more than their role reflects.
Eventually, that invisible load shows up as missed details, disengagement, frustration, turnover, quiet resistance, or burnout. By the time it becomes obvious, the project has already been absorbing the cost for a while.
Capacity Is More Than Headcount
In project management, capacity is often treated like math. How many people do we have? How many hours are available? How many tasks are assigned? Those questions matter, but they’re not enough.
Real capacity includes focus, decision speed, role clarity, stakeholder availability, subject matter expert bandwidth, and the ability to do thoughtful work without constant interruption. A team can be fully staffed and still overloaded. A project can have enough names on the resource plan and still be under-resourced in the areas that matter most.
For example, you may have enough analysts assigned, but only one SME can answer the critical workflow questions. You may have enough project team members, but decisions are stuck with one executive sponsor. You may have enough technical resources, but testing is delayed because the business team doesn’t have time to validate the work.
That’s why staffing alone isn’t the answer. Project managers have to look beyond the number of people assigned and ask where the work is actually slowing down.
Delivery Problems Are Often System Problems
When projects struggle, the response is often tactical: update the timeline, add resources, schedule more meetings, increase reporting, create another spreadsheet, or escalate the issue.
Those actions may be necessary, but they don’t always address the root cause. Sometimes the last thing the project needs is one more tracker or dashboard. It needs someone to step back and ask why the work isn’t moving.
A broken project system often looks like this:
- Scope keeps changing, but the timeline does not.
- Priorities compete, but no one decides what comes first.
- Decisions are needed, but decision-makers are unavailable.
- Key resources are overused because they know the most.
- Processes create extra steps instead of removing friction.
- Documentation increases, but understanding does not.
- Risks are discussed informally but not managed directly.
- Everyone is busy, but the most important work is still delayed.
That isn’t just a staffing issue. That’s a system issue. As project managers, we are often in the best position to see it.
Key Points for Project Managers
This is where experience matters. When a project begins slipping, the project manager should not jump straight to “we need more resources.” That may be part of the answer, but it shouldn’t be the first diagnosis. Strong project managers do more than report slippage. They diagnose what’s driving it.
1. Don’t Assume Staffing Is the Real Issue
Before asking for more people, review the work itself. Is the scope clear? Are decisions moving? Are priorities stable? Are current resources being used well? Sometimes teams are not understaffed. They are overcommitted, misaligned, or stuck waiting on decisions.
2. Look for the Work Behind the Work
Project plans rarely show the full load. They show tasks, milestones, owners, and dates. They do not always show the meetings, follow-ups, rework, approvals, vendor coordination, testing issues, stakeholder management, and emotional labour required to keep work moving. That hidden work consumes capacity, and a task that looks simple on paper may carry a heavy coordination load in reality.
3. Find the Bottleneck Before Adding People
Adding people will not help if the delay is caused by one unavailable decision-maker, one overloaded SME, one unclear workflow, or one unresolved dependency. Before adding resources, look at where work stops, waits, loops back, or depends on the same person repeatedly. That is usually where the real issue is hiding.
4. Reduce Before You Resource
Before asking for more staff, ask what can be paused, simplified, removed, or delayed. Sometimes the best project management move is not adding more. Sometimes it is removing what should not be there. That may mean narrowing scope, delaying a lower-priority deliverable, reducing unnecessary meetings, simplifying approvals, or challenging work that no longer supports the project outcome.
5. Protect Your High Performers
If the same people are always absorbing the extra work, pay attention. That is not a long-term strategy. That is a risk. High performers can keep a project moving, but they should not become the workaround for poor planning, unclear ownership, or weak decision-making. When the project depends on heroics, the system is already fragile.
6. Use Data and Observation
Do not rely only on the resource plan. Look at meeting volume, delayed decisions, late approvals, repeated escalations, rework, defect trends, open risks, and how often work is waiting on the same person or group. The resource plan may say the team has capacity. The project behaviour may say otherwise.
7. Escalate the System Issue, Not Just the Schedule Issue
Instead of only saying, “We are behind,” be specific: “We are behind because scope has expanded, decisions are delayed, and the same three people are carrying most of the unresolved work.” That changes the conversation. Now leadership is not just reacting to a missed date. They are looking at the conditions causing the missed date.
Wrapping Up
You can’t staff your way out of a broken system.
More people can help when capacity is truly the issue. When the real problem is unclear scope, slow decisions, competing priorities, overloaded key resources, or poor work design, adding people will not fix the project. It will just spread the strain.
From my experience, the strongest project managers are not the ones who simply ask for more people. They are the ones who can diagnose whether the project needs more capacity, better decisions, clearer priorities, or a cleaner system.
Before adding resources, project managers should ask a different question: Are we solving a staffing problem, or asking people to work inside a system that was never designed to support the work?
IPM CPM Level 1
IPM-AI
