Illustrative scenario — not a reported case: at a quarterly portfolio review, a PMO director learns that a programme marked green has lost stakeholder alignment weeks earlier. The status report was accurate about the fields it tracked; it did not connect the warning signs soon enough for a decision.
That situation creates a tempting conclusion: a mature PMO must not be mature enough. PMI’s 2026 research supports a narrower and more useful conclusion. Complex projects require organisations to recognise changing interdependencies and respond; a framework alone is not evidence that those conditions have been met.
PMI reports that 31% of complex projects fail to achieve the full scope of their originally intended benefits. That figure is for complex projects in the research, not for organisations with a PMO. The PMO comparison is encouraging but limited: it is a self-reported association, not proof that a PMO causes a project to succeed. The practical task is to use governance to surface evidence and make decisions before risks compound.
What PMI’s 2026 data actually says
The scope matters. PMI defines complexity as the dynamic, often unpredictable interaction of interdependent tasks, stakeholders, technologies and external influences. The report therefore distinguishes a complex-project finding from a claim about every project or every PMO.
| Official finding | What it measures | How to interpret it |
|---|---|---|
| 31% | Complex projects that fail to achieve the full scope of their originally intended benefits. | A complex-project result (PMI 2026, p. 5), not a rate for PMO-equipped organisations. |
| 12% | Failure rate for projects overall in PMI’s 2024 Maximizing Project Success research. | Useful context for the 31% figure, but not a before/after test of PMO impact. |
| 63% vs. 57% | Professionals saying they were very or extremely successful at managing complexity in organisations with a PMO versus without one. | A self-reported association (PMI 2026, p. 23), not an objective success rate or causal estimate. |
PMI’s accompanying release gives the same practical warning: complexity is not a problem to eliminate. Treat the figures as a prompt to inspect how a programme senses change and responds, not as a promise that any structure removes delivery risk.
What a PMO changes — and what it does not
The 63% versus 57% comparison says that respondents in organisations with a PMO were more likely to rate their management of complexity highly. It does not tell us that the PMO alone produced the difference, nor that 63% of projects succeeded. Differences in portfolio type, capability, sponsorship or measurement may also matter.
That limitation is useful rather than disappointing. It moves the management question away from “Do we need another governance layer?” and toward “Which evidence reaches a named decision-maker early enough to change the outcome?”
Why a fixed plan is not enough for complex work
A baseline can make assumptions explicit, but it cannot freeze their relationships. A supplier delay, a stakeholder’s reduced engagement and a budget variance may each be manageable in isolation. In combination, they can alter the decision that is now needed. PMI’s description of complexity calls for sensing, experimentation and adjustment rather than relying only on a fixed plan.
Simulated R&D programme: combining weak signals — Simulated scenario
Working hypothesis, not a real case. For eight weeks, an R&D programme is marked on track. A supplier misses two non-critical hand-offs, the scientific sponsor misses working sessions, and contingency absorbs a small variance. None crosses its own escalation threshold. In week nine, the combined effect threatens a decision gate. A weekly cross-signal review would not guarantee recovery; it would make the trade-off visible before the committee meeting.
Turn the finding into a decision loop
Start with a short cross-signal review: choose the schedule, cost, risk and stakeholder signals that may interact; give each an owner; define the decision that follows when a threshold is crossed; and record why the decision was made. For a related way to connect measures to actions, use decision and quality metrics rather than an ever-larger dashboard.
In R&D, the definition of progress should also reflect technical uncertainty, not only milestones consumed or budget spent. The guide to assessing the progress of an innovation project offers a complementary, R&D-specific framing for that review.
Trade-off
- Benefit: A cross-signal review can make dependencies and decisions visible earlier than a monthly or quarterly status pack.
- Cost: It requires more disciplined ownership of schedule, cost, risk and stakeholder evidence.
- Risk: More signals can create noise or escalation fatigue when thresholds and decision rights are unclear.
- Prerequisite: Teams need sufficiently current, comparable inputs and a named person who can act on the review.
- Limit: Earlier visibility does not eliminate uncertainty or ensure recovery; it only creates a better-timed opportunity for human judgment.
Questions for the next steering committee
- Which three signals could interact before the next reporting cycle?
- Who owns the decision when those signals cross a combined threshold?
- What evidence would change the committee’s current decision?
- Where do schedule, cost, risk and stakeholder data disagree in cadence or definition?
- Which risk remains explicitly outside the PMO’s ability to control?
The useful interpretation of the 31% finding
The evidence does not support saying that a mature PMO should prevent complex-project failure, or that the 31% figure applies to PMO organisations. It supports a more practical conclusion: in complex work, governance has value when it helps people detect interdependencies, test assumptions and make accountable decisions as conditions change.