Ask any PMO Manager who's overloaded on their team, and they'll tell you — instantly, without checking a single report. Ask them to prove it to the board, and the certainty disappears into a spreadsheet nobody trusts.
That's the resourcing problem hiding inside most portfolios: everyone knows it exists, and nobody can see it clearly enough to act.
The wrong question
Most project tools answer "who's assigned to what?" That's a task-management question. It tells you names against tickets. It does not tell you whether the person behind those tickets is running at 60% capacity or 160%.
The better question is quieter, and it's the one boards never get asked: is our best talent being spent, or being spent down?
Why over-allocation stays invisible
Resourcing usually lives in three places at once — a project plan here, a spreadsheet there, a manager's memory everywhere else. Add up the hours a senior delivery lead is committed across four projects, and the total often exceeds what a week actually holds. Nobody added it up on purpose. Nobody had a single place to add it up at all.
The result: over-allocation isn't rare. It's the default state of anyone good enough to be trusted with more than one thing.
What it costs
Seventy percent of large-scale digital transformations fail — not because the plan was wrong, but because the people executing the plan were stretched across too many of them at once. Burnout doesn't show up as a red status. It shows up eighteen months later, as a resignation letter and a knowledge gap nobody budgeted for.
The cost here isn't abstract: budget wasted, headcount churn, the same senior person re-hired at a premium eight months after they left.
What good visibility actually looks like
A resourcing view that matters needs three things a spreadsheet can't hold at once:
- Every allocation, across every project, in one place — not one plan at a time.
- A rolling forward view, not a snapshot. Over-allocation next quarter is still a today problem.
- A clear threshold. Not "she looks busy," but a number: 80–100% is healthy, above 100% is a flag, and someone owns the flag.
This is what Project Director's Resource Capacity view is built to surface — total utilisation, over-allocation counts, and a 12-month rolling timeline, filterable by role, so the constraint shows up before it becomes a resignation.
The reframe
You don't have a resourcing problem because your team isn't working hard enough. You have one because nobody can see the total. Fix the visibility, and the burnout risk stops being a surprise.
See who's over-allocated before they hand in their notice.
