- By Admin
- 08/14/2026 12:44:47
ALL
Project Management Talent Gap: 29.8M Short by 2035
29.8 Million Project Professionals Short: How to Do More With the Delivery Team You Already Have
The project management talent gap is now large enough that hiring cannot be the answer for most organisations. PMI's Global Project Management Talent Gap research puts the current worldwide population of project professionals at 39.6 million and projects demand growth of up to 30 million more by 2035 — implying a shortfall of as many as 29.8 million qualified people, and putting transformation programmes at genuine delivery risk.
Numbers at that scale can feel abstract, so here is the operational translation. Every one of the markets Arcprojects.io serves — the United States, South Africa, Canada, Australia and India — is drawing on the same constrained pool, at the same time, for the same senior delivery capability. A firm in Toronto competing for an experienced programme manager is competing with a firm in Sydney and one in Bengaluru, often for the same remote-capable individual.
Which means the practical lever is not recruitment. It is making sure the delivery people you already have are working on the right things, at a sustainable load, with visible capacity — because the fastest way to widen your own talent gap is to burn out the professionals already on your payroll.
Key takeaways
- PMI puts the current global population of project professionals at 39.6 million.
- Demand is forecast to grow by up to 30 million by 2035, implying a shortfall of as many as 29.8 million qualified people.
- All five of Arcprojects.io's target markets compete for the same constrained talent pool, so local hiring strategies offer little relief.
- Attrition is a talent-gap multiplier: replacing an experienced project manager costs far more in delivery disruption than in recruitment fees.
- The most available capacity in most firms is not a new hire — it is the over-allocation and hidden non-project load nobody is currently measuring.
Why this matters right now across the five target markets
In the United States and Canada, the pressure is concentrated in complex programme delivery. Organisations that expanded PMO capability through the last decade are now discovering that the senior people who hold institutional delivery knowledge are the ones with the most external options, and that a mid-level project manager promoted into a programme role without support tends to leave within eighteen months. The gap is not in bodies; it is in the specific tier of experience that makes complex delivery predictable.
In Australia and South Africa, the constraint compounds with an infrastructure and public-programme pipeline that assumes a delivery workforce which does not exist locally at the required scale. Firms in both markets increasingly staff programmes with a thinner senior layer supervising more junior delivery staff, which works until something goes wrong and there is nobody with the bandwidth to intervene. In India, the picture inverts: the supply of project professionals is growing fast, but so is domestic demand and the pull of global delivery centres, so retention rather than recruitment is the binding constraint for mid-sized consultancies.
What unites all five is a measurement failure that most organisations would recognise if they looked. Almost every project-based firm can tell you its headcount and its revenue. Very few can tell you, for a named individual, how many concurrent projects they are carrying, what proportion of their week is consumed by internal and administrative work, and how that has trended over six months. That is the data on which retention decisions actually depend, and it is usually absent. A project professional does not resign because of one bad quarter; they resign after four quarters of quiet over-allocation that nobody could see because nobody was measuring it.
What it means for managing directors, HR and resourcing leaders
If you lead a project-based professional services firm or its people and resourcing function, three things follow from the talent gap forecast.
First, treat capacity as a real number rather than a headcount proxy. A team of twelve project managers is not twelve project managers' worth of capacity. Subtract leave, public holidays, training, internal initiatives, bid support and the administrative overhead of running the practice, and the realistic delivery capacity is frequently 60 to 70% of the nominal figure. Firms that plan against nominal headcount systematically over-commit, and the gap is absorbed by the individuals rather than surfaced as a resourcing decision.
Second, make concurrent project load visible and cap it deliberately. The single most reliable predictor of project manager burnout in the organisations we see is not total hours — it is the number of simultaneous projects with distinct clients, governance cycles and stakeholder groups. Someone running six concurrent engagements at 30% each is carrying six status meetings, six risk registers and six sets of client relationships, which is a materially heavier cognitive load than two engagements at 90%. Very few firms track this at all, and almost none set a cap.
Third, accept that retention is largely a workload conversation. Project team retention research repeatedly lands in the same place: people leave because of unsustainable load, unclear priorities and the sense that nobody noticed. Salary is a threshold rather than a lever — underpay and you lose people, but overpaying does not retain someone who is over-allocated for a year. The organisations holding onto senior delivery talent in a tight market are the ones that can show an individual their forward load, adjust it before it becomes untenable, and demonstrate that the adjustment was made deliberately.
Three practical implications for your resourcing model
Plan against real available hours
Capacity net of leave, holidays, training and internal work — not nominal headcount. Over-commitment almost always begins with a resource plan built on a number nobody net-adjusted.
Cap concurrent engagements
Track how many distinct projects each person carries, not just their utilisation percentage. Fragmentation across clients is what exhausts senior delivery staff long before total hours do.
Make leave visible in the plan
A resource plan that ignores approved leave will quietly reassign that time to a project. Leave-aware scheduling is both a retention control and a delivery accuracy control.
Spreadsheets, point tools or workload balancing software
| Capability | Spreadsheets | Point tools | Arcprojects.io |
|---|---|---|---|
| Forward capacity view | Static, stale within days | Often an add-on module | Rolling forward plan across every live project |
| Leave-aware scheduling | Leave held in a separate sheet | Separate leave product required | Approved leave removed from available capacity automatically |
| Concurrent project load per person | Not tracked | Rarely surfaced | Visible per individual alongside allocation |
| Over-allocation alerts | Discovered when someone complains | Limited thresholds | Flagged before the allocation is committed |
| Actual versus planned effort | Compared at project closure, if at all | Time tracking without a plan to compare to | Approved timesheets measured against the resource plan |
| Non-project work visibility | Invisible, absorbed silently | Usually excluded | Captured, coded and reported like any other load |
| Portfolio-level resourcing decisions | Manual consolidation across files | Project-level only | Dashboards across teams, practices and the portfolio |
How Arcprojects.io helps you protect the delivery team you already have
Arcprojects.io brings Resource Planning & Utilisation, Timesheets, Dashboards and Holidays & Leave into one platform, which reframes the talent gap as something a managing director can actually act on: a workload visibility problem rather than a recruitment problem. Forward resource plans built on realistic capacity baselines, leave-aware scheduling and over-allocation alerts protect the delivery professionals a firm already has — which, in a market short of up to 29.8 million people, is the most valuable asset on the balance sheet.
- Build a capacity baseline you would defendModel each person's genuinely available hours net of approved leave, public holidays, training and committed internal work, rather than planning against nominal headcount. Most firms find their real delivery capacity is 25 to 40% below the number they have been using, which explains a great deal about why plans slip and people are tired.
- Schedule forward and alert on over-allocationLoad confirmed and probable work against that baseline so a resourcing lead can see six to twelve weeks ahead. Over-allocation is flagged before it is committed, and concurrent project load per individual is visible alongside the allocation percentage — which is what catches the fragmentation that percentage figures hide.
- Close the loop with actual effortUse approved timesheets to compare planned effort against actual, by person and by project. That comparison is what turns workload balancing from an intention into a discipline: it shows which engagements systematically consume more than they were planned to, and which individuals are absorbing the difference quietly.
See your real delivery capacity
Walk through forward resource plans, leave-aware capacity baselines, over-allocation alerts and utilisation dashboards with a specialist who works with project-based firms.
"In a market short of tens of millions of project professionals, the cheapest recruitment strategy available to any firm is not losing the ones it already employs."
"We lost two senior project managers in a quarter and assumed it was about pay. When we finally looked at the allocation data, both had been carrying five or six concurrent engagements for nearly a year. Nobody had decided that — it just accumulated. We now cap concurrent projects and review it monthly, and we have not lost anyone at that level since."
Resourcing leader's workload balancing checklist
- Recalculate capacity per person net of leave, holidays, training and internal commitments.
- Compare that figure to the headcount number your resource plan currently assumes.
- Track concurrent project count per individual, not just allocation percentage.
- Set a maximum number of simultaneous engagements by role and enforce it.
- Make approved leave automatically reduce available capacity in the forward plan.
- Alert on over-allocation before the assignment is committed, not after the person raises it.
- Give internal, bid and administrative work a code and a budget so it stops being invisible.
- Compare planned against actual effort monthly to find engagements that consistently overrun.
- Review each senior individual's twelve-month load trend in retention conversations, with the data in front of you.
Frequently asked questions
How big is the global project management skills shortage?
PMI's research puts the current worldwide population of project professionals at 39.6 million, with demand growing by as much as 30 million by 2035 — a potential shortfall of up to 29.8 million qualified people. The figure is best read as a demand signal rather than a precise forecast: it reflects the volume of project-oriented work being created by infrastructure investment, digital transformation and organisational change, against a profession that cannot expand at anything like that rate. The full methodology and regional breakdown are published in the PMI global talent gap research.
How do firms retain project managers without raising salaries?
By fixing the conditions people actually leave over. Pay operates as a threshold — below market, you lose people regardless of anything else; above it, a further increase rarely retains someone who is over-allocated. What does retain experienced project professionals is a visible and sustainable forward load, a defensible cap on concurrent engagements, clarity about which of their commitments matters most this month, and evidence that the organisation notices and adjusts. Practically, that means the resourcing conversation has to happen with real allocation data in front of both parties, several weeks before the load becomes untenable, rather than as an exit interview.
How do you balance workload to prevent project manager burnout?
Measure three things most firms do not: real available capacity net of leave and internal commitments, concurrent project count per person, and planned versus actual effort by engagement. The first tells you whether the plan was ever achievable, the second catches the fragmentation that utilisation percentages hide, and the third shows which projects quietly consume more than they were sized for. Then act on them in the forward plan rather than in retrospect — an over-allocation flagged six weeks ahead is a resourcing decision, while the same over-allocation discovered in week one of delivery is simply an individual absorbing it. Wider context on why this matters at industry scale is set out in the PMI talent gap report.
The capacity you are looking for is already on your payroll
A shortfall of up to 29.8 million project professionals is not a problem any single organisation can hire its way out of, and the firms that try will spend the next decade paying escalating salaries for people who leave for the same reasons the previous ones did. The alternative is unglamorous and effective: know what your real capacity is, know what each person is actually carrying, and make workload a decision rather than an accumulation.
Arcprojects.io was built to make that visible without adding administrative load to the people you are trying to protect. Explore how the resource planning, timesheet, leave and dashboard modules work together on the features and benefits page, see the kinds of firms already running on it at who uses Arcprojects, or review pricing. You can also start a 30-day free trial and compare your nominal headcount capacity against your real one before changing anything else.