A PMO leader is closing out the draft capacity plan for the 2027-2028 budget — the same carenza talenti project management capacity planning 2026 problem now facing PMOs everywhere. On the sheet, two columns don't reconcile. On one side, the board is asking to support more parallel projects with the same project manager headcount. On the other, three senior positions have been open for over four months, and in the meantime two experienced PMs have resigned for a higher offer elsewhere. The current draft of the plan assumes that increasing the recruiting budget in 2027 will fill positions within the usual timeframe. But time-to-fill isn't returning to normal — it's stretching out.
During budget season, the temptation is to treat the PM shortage as a temporary labor-market problem: a few rough months, solvable with more competitive salaries or a more aggressive recruiting budget. But if the scarcity of qualified project managers is structural and spans multiple years, a capacity plan built only on linear-hiring scenarios risks looking realistic to the board when it isn't. It's the PMO leader, not the board, who discovers this first, when positions stay unfilled.
Many PMOs treat the project manager shortage as a recruiting problem that budget can solve. Available data instead points to a structural, multi-year supply shortage. Demand for PM talent is growing faster than the pipeline of professionals the market can train. If this holds, a 3-5 year capacity plan cannot rely solely on "how many more PMs will we hire." It must include, by default, a stable-headcount scenario, with a different model for distributing and supporting PM work.
What this article does not cover (and why the distinction matters)
This article does not address day-to-day resource allocation conflicts between parallel projects. That topic — who works on what this week, how to arbitrate conflicting priorities among project managers — is covered elsewhere, in a piece dedicated to multi-project capacity planning. Nor does it address, except incidentally, the substantive reasons complex projects fail (scope, governance, stakeholders): that topic has its own dedicated treatment. Here, the angle is different and precedes both: it concerns how many qualified people a PMO can reasonably plan to have available over the next 2-5 years. This holds regardless of how it later allocates them day to day, or of what causes any single project to fail. It's a market-supply problem, not an internal-process one.
Where the shortage comes from: demand is growing faster than the pipeline
PMI describes the project professional shortage as a global, multi-year phenomenon, not a temporary recruiting difficulty tied to a single economic cycle. The central point isn't that candidates are absent in absolute terms. It's that the pace at which qualified new professionals enter the market isn't keeping up with the growth in demand for project management roles, particularly at senior level.
To give the phenomenon scale, PMI currently puts the global base of project professionals at approximately 39.6 million. Demand, according to its projections, could grow by up to 64% between 2025 and 2035. It's in this context, not in isolation, that the most-cited figure should be read: a PMI projection for 2035, based on analysis from LinkedIn Talent Insights and the global workforce. According to that projection, the number of missing project professionals could reach up to 29.8 million — a figure often rounded to 30 million. It should be treated for what it is: a projective estimate over a ten-year horizon, not a verifiable actual figure today.
The practical consequence for capacity planners isn't that a precise number of PMs will be missing ten years from now — no PMO needs that figure to decide its 2027-2028 budget. The consequence is more immediate: if aggregate demand grows faster than supply at the global level, competing solely by raising salaries doesn't add new PMs to the market. It only redistributes them from one PMO to another. The problem stays on the market as a whole; it only shifts from one organization to another.
Why more recruiting budget doesn't create more qualified PMs
The mechanism behind the shortage isn't salary-based, it's time-based. A senior project manager isn't formed in a few months. The competence required — managing complex budgets, risk portfolios, multiple stakeholders — is typically built over years of exposure to real projects, not through an accelerated certification course. A PMO can raise a salary and attract an already-trained senior PM. But this doesn't increase the total number of senior PMs available in the market: it simply moves one from another organization to its own. This is exactly the point PMI makes when it frames the shortage as a structural imbalance between growing demand and the pipeline's capacity to train new professionals at the same pace.
This also explains why time-to-fill for senior PM roles keeps lengthening instead of normalizing. If the number of fully qualified candidates grows more slowly than the number of open positions across the market, every additional recruiting cycle competes for the same narrow pool, not a pool that replenishes proportionally. A PMO planning for 2027-2028 on the assumption that recruiting budget will solve coverage within a few months is implicitly assuming that pool widens in time — an assumption the multi-year demand data doesn't support.
What practice shows: more forecasting is happening, but perceived effectiveness stays low
A second piece of evidence concerns not PM availability, but PMOs' ability to plan capacity with current tools. According to the Runn 2026 survey, 86% of organizations surveyed report doing capacity forecasting regularly or occasionally. That's up from 81% in 2025. The figure applies to that survey's sample, not to universal adoption certified by a third party. So the practice is spreading.
But in the same survey, only 6% of organizations describe their forecasting capabilities as "extremely effective." The gap between growing adoption and low perceived effectiveness fits the structural reading of the shortage. More forecasting processes don't offset a scarcity of qualified people upstream. A PMO can improve how well it estimates capacity needs. But if the estimated need systematically exceeds available market supply, forecasting only flags the problem more precisely. It doesn't solve it.
Simulation: R&D PMO, 12 PMs across 30 active projects — Simulated scenario
An R&D PMO with 12 project managers across 30 active projects applies the demand growth trend described by PMI to its own portfolio. It estimates it will need to fill 4 additional positions by 2028 to support the board's projected growth in parallel projects. Over the same period, the average time-to-fill for a senior PM role in the organization has already risen to 5-6 months, up from a typical 2-3 months a few years earlier. If the capacity plan is limited to a linear hiring scenario — 4 open positions, recruiting budget allocated, coverage expected within the year — it carries a risk. The PMO risks presenting the board a plan that assumes a fill rate inconsistent with the trend observed internally. A more realistic plan includes a flat-headcount scenario alongside the headcount-growth scenario. In it, the same 12 PMs sustain a growing number of projects through stronger support for reporting and data-aggregation processes — not through a simply higher individual workload.
What changes in practice for the 3-5 year capacity plan
If the shortage is structural, the capacity plan cannot include only a linear headcount growth scenario. By default it must also include a stable-headcount scenario, in which the portfolio grows not because new PMs join, but because PM work is redistributed and supported differently. This means putting three levers on the table alongside the recruiting budget — levers that remain marginal in many PMOs today. The first is internal upskilling paths to move junior project leads or coordinators into full PM roles faster than the external market allows. The second is shifting low-value-add activities — data aggregation, status reporting, administrative follow-up — to dedicated processes or tools, freeing senior PM time for decisions and stakeholder management. The third is an explicit review of how many projects a PM can support in parallel before the load becomes an operational risk. Otherwise, that number grows implicitly every time the board asks for more projects.
- Include a stable-headcount scenario in the capacity plan, not only linear PM team growth scenarios
- Estimate the actual time-to-fill for senior PM roles observed internally over the last 12-24 months, not a historical pre-shortage figure
- Map which activities of current PMs are repetitive aggregation/reporting and which require judgment and experience
- Evaluate internal upskilling paths on a 12-18 month horizon as a partial alternative to external recruiting
- Explicitly state to the board which part of the plan depends on hiring and which on redesigning existing work
ControlRoom's role: it reduces operational load, not the PM shortage
Trade-off
- Benefit: ControlRoom deterministically aggregates EVM, budget, and risk data already present in the PMO, using AI only as a synthesis and evidence-linking layer — not to calculate KPIs. This reduces the time each PM spends manually building reports and status updates, leaving more room for active project management.
- Cost: It requires that project data (progress, costs, risks) already be tracked in a structured way: the benefit is proportional to the quality of the input data, not to any AI capability to "guess" missing information.
- Risk: A PMO that treats a tool like this as a substitute for hiring new PMs, rather than as a load reduction for existing PMs, risks overestimating how many additional projects its current headcount can support. It may assume that volume can grow without a corresponding increase in the risk of error.
- Prerequisite: Minimal EVM, budget, and risk management processes already in place in the PMO, even if not yet centralized.
- Limit: ControlRoom does not increase the supply of qualified project managers in the market, and it does not reduce the shortage described by PMI. It only acts on the operational load distributed among PMs already in the organization.
This distinction should be stated to the board in the same way the structural nature of the shortage should be stated. A tool that reduces load per PM allows a bit more project volume with the same headcount. It does not replace the need to hire, train, or redistribute roles once the portfolio grows past a certain threshold. Presenting it as the sole solution to a capacity problem would be as risky as assuming the PM market will normalize on its own.
The 2027-2028 capacity plan a PMO leader brings to the board should not, then, choose between "hire" and "optimize." It should show both levers together, with realistic weights based on observed time-to-fill and multi-year demand projections. For day-to-day management of who works on what across competing projects, the next topic — multi-project allocation and conflicts — is addressed in a dedicated article within this same editorial cluster. That article assumes the available headcount for each scenario has already been set.