“We’ll use internal resource” is doing a lot of work in that sentence.
It appears in almost every project governance conversation at some stage. The initiative is approved. The budget is agreed. Someone asks about project leadership. The answer comes quickly, confidently, and with the air of a problem already solved: we’ll use internal resource.
It’s understandable. It sounds responsible – cost-conscious, even. It avoids the conversation about external spend. It signals confidence in the existing team. And it defers the harder question, which is whether the team being referenced has the capacity, experience, and focus to actually deliver what’s being asked of them.
The honest truth is that “we’ll use internal resource” is almost always an optimistic statement dressed up as a practical one. And optimism, in project delivery, has a well-documented track record.
What it usually means in practice
There’s a second honest truth embedded in the internal resource decision, and it’s less about experience than it is about specialist knowledge; having deep expertise in programme delivery, the methodologies, governance structures, and disciplines that comes with doing it as a dedicated craft.
For straightforward, low-risk projects with clear scope and no significant dependencies, this can work. But that description doesn’t cover most of the projects where you actually need strong leadership. The ones that need it most are precisely the ones where the work is complex, the stakes are high, and the margin for error is low. Those are also the ones where a part-time, already-stretched leader is most likely to produce part-time, already-stretched results.
Adding a complex project to someone’s existing workload doesn’t create a project manager. It creates a person who is now managing a project on top of everything else.
The accountability blur
There’s a specific problem with internal resourcing that goes beyond capacity: accountability becomes diffuse. When a dedicated project manager is running a programme, the accountability is clear. There is a person whose primary, ideally sole, professional responsibility is that programme’s success. Their performance is measured against it. Their attention is focused on it.
When internal resource is used, accountability sits alongside everything else the person is doing. The project is one of their responsibilities, not the responsibility. When a conflict arises between the project and something else, and it will, the outcome is predictable. Not because the individual lacks commitment, but because that’s what happens when priorities compete. The urgent beats the important. The visible beats the strategic.
The project slips. A decision is delayed because the person needed to lead it was in a BAU meeting. A risk wasn’t escalated promptly because the window for raising it closed during a period when the project lead was covering for something else. These aren’t failures of character. They’re the natural result of a model that asks one person to serve multiple masters simultaneously.
The knowledge gap
There’s a second honest truth embedded in the internal resource decision, and it’s about specialism rather than capacity. The skills that make someone excellent at their function, deep technical knowledge, strong relationships, institutional credibility, are not the same skills that make someone effective at managing complex delivery at pace.
Experienced project and programme managers have a specific set of hard-won capabilities: they know how to structure a plan that’s actually executable, not just presentable. They know which risks to escalate and which to manage. They know how to have the difficult conversations with sponsors before the problems become crises. They know what good looks like because they’ve seen it, and they’ve seen what the alternatives look like too.
That experience is accumulated over many programmes, in many organisations, under many kinds of pressure. It cannot be improvised by a capable person who is doing this for the first time while also managing their existing responsibilities.
There is a meaningful difference between someone who can talk intelligently about project management and someone who has managed projects professionally for a decade. Organisations routinely treat these as equivalent when the resourcing conversation gets uncomfortable.
The question worth asking first
Before the next project is staffed with internal resource, it’s worth doing something the governance process rarely makes time for: an honest capacity assessment. Not “do we have someone at the right level who could do this?” but “does that person have the dedicated time, the relevant experience, and the organisational mandate to do this well, without it competing with everything else they’re carrying?”
For many organisations, that question has an obvious answer. The person exists. The experience exists. The capacity does not. The decision then is whether to proceed on the basis of optimism or on the basis of what’s actually true.
What the honest version looks like
Organisations that resource their projects honestly, matching delivery capability to delivery requirement, tend to make this decision earlier rather than later. They know that the cost of bringing in the right resource at the start of a project is almost always lower than the cost of correcting the problems that accumulate when the wrong resource is used and the project runs into difficulty.
PMaaS exists for exactly this scenario. It’s not a judgement on the internal team. It’s an acknowledgement that experienced, dedicated delivery resource, available at pace, without a permanent headcount decision, is a legitimate and often more sensible answer to the resourcing question than the comfortable fiction that someone already fully employed will find a way to make it work.
The honest truth is that most organisations already know this. The internal resource answer persists not because it’s the right answer, but because it’s the easier conversation to have.
Capacity doesn’t stretch just because a project is important. Stoneseed PMaaS adds experienced delivery capability exactly when and where it’s needed. If your internal resource is running at full capacity, might be worth a conversation.