Complex stopped being a category and became the working condition. PMI's 2026 data on what that does to delivery, and to your record.
In the 2024 Maximizing Project Success research, PMI measured how often projects fail to achieve the full scope of their originally intended benefits. The number was 12%.
The 2026 Pulse of the Profession asked the same thing about complex projects specifically. The failure rate jumped to 31%. More than double.
My first reaction was to distrust the number. Different studies, different questions, and different data slices usually have a methodology story sitting quietly behind them.
Then I kept reading, and the report closes that escape route firmly.
A massive 97% of project professionals say they managed at least one complex project in the past year.
Over half classify those projects as significantly complex.
Even more telling, 81% say projects have become more complex, and 37% describe the increase as significant.
So the number that matters is not the failure rate... It is the population.
Complex stopped being a category of project you get handed once every few years. It became the ordinary condition of our work. This means 31% is not describing some exotic subset of megaprojects in another industry. It is describing the environment where your delivery record is being written right now.
After years of using the word in status meetings, what does PMI actually mean by complex?
Complicated Is a Problem You Solve.
Complex Is a Problem You Keep Answering.
A complicated problem has many elements, and the relationships between those elements are knowable. You can map it out. Given enough expertise, effort, and the right resources, it resolves. A refinery turnaround with 4,000 activities is complicated. It is hard and exhausting, but knowable.
A complex problem also has many elements, but the relationships between them are unpredictable. Complex systems evolve through their own interactions. Working through one calls for sensing, experimenting, and adjusting rather than just executing a fixed plan.
PMI defines the difficulty not by effort or expertise, but by adaptation, emergence, and interdependence.
- Work breakdown structure decomposes.
- Critical path assumes the sequence holds long enough to be worth calculating.
- Change control assumes change arrives as a discrete request from a named person at a moment when somebody can approve it.
- Earned value assumes the baseline still describes the same project.
Complexity Is Not Risk, and This Confusion Is Expensive
Complexity describes the conditions that make the project hard to predict, control, and stabilize in the first place.
Complexity is a source of risk. Risks are the consequences that come out of it. They are not two names for the same discomfort.
This explains something I have watched happen more than once, and have been on the wrong side of myself. You keep a genuinely good risk register. It is reviewed, owned, dated, and scored. And the project still gets taken apart by something that was never on it.
In complex environments, risks are more interconnected and more likely to emerge over time. Organizational structures, human dynamics, and external forces interact in ways that amplify small issues into large ones.
You cannot register a risk that does not exist yet as an identifiable event. You can only recognize the conditions that manufacture them.
When the thing that hits you was never on the register, the conversation afterwards is almost never about the conditions. It is about your register.
It is about whether you should have seen it coming. You lose that conversation every time, because you are defending an artifact that was built to answer a different question.
Where the Friction Actually Comes From
Organizational: The internal friction. Unclear decision-making authority, siloed teams, competing priorities, and misaligned objectives. Escalations take longer than they used to. Approvals stall in layers you did not know existed, and the question “who owns this?” keeps coming up. This scales with size. A large 91% of professionals in organizations of 100,000 or more report increasing complexity, against 78% in organizations under 500 people.
Environmental: The external forces. Technology cycles, digital transformation, AI adoption, regulatory movement, geopolitical shifts, and supply chains. Requirements keep changing while everybody is still deciding. The world around the project simply moves faster than the plan does. Emerging technology resets what stakeholders consider reasonable on speed or cost, and a market event quietly changes what the word value means to your sponsor.
Human: The social and cognitive layer. Competing incentives, politics, and relationship dynamics. Decision makers avoid committing. Teams second-guess a direction that was already given. Psychological safety becomes something you aspire to rather than something you have. This dimension requires emotional intelligence, influence, and coalition building (capabilities no methodology installs for you automatically).
These dimensions interact. A regulatory shift (environmental) triggers new internal approvals (organizational), which increases anxiety and micromanagement (human). One force moves through three dimensions. By the time it reaches your team, it has stopped looking like regulation and started looking like a morale problem.
Nearly half of project professionals name faster technology and tool cycles as a driver of complexity.
But if you only treat the technology, you will keep treating the symptom three steps upstream from where your team is actually bleeding.
The Finding That Should Change How You Spend Your Week
High performers (professionals whose complex projects perform above average) do not face less complexity. The report is explicit about this. They face the exact same conditions but respond to them differently, using intention and foresight.
The difference is massive. A full 88% of projects were rated extremely or very successful when teams were highly effective at managing complexity. Compare that with just 14% when teams were only slightly effective or ineffective.
Projects that handle complexity well are five times more likely to succeed.
This is not a resourcing story. It is a capability story, and capability is the one variable you personally control.
You do not need a new instrument to start. You need one simple discipline, and it costs you about 90 seconds. The next time something goes wrong on your project, before you write the escalation, classify it.
- Is this complicated? The relationships are knowable, and it resolves with expertise, effort, and the right people.
- Is this complex? The relationships are shifting, and no amount of expertise will hold them still.
A complicated problem gets escalated with a solution attached and a request for resources or a decision.
A complex one gets escalated with the conditions named and a request for a different operating agreement.
You might need more frequent checkpoints, a decision right moved closer to the work, or a scope boundary that can flex on purpose instead of by accident.
Most of the escalations I have seen fail happened because a complex condition was presented as a complicated problem. The sponsor gave a complicated answer: push harder, add a resource, tighten the plan. Nothing moved, because nothing in that answer touched the thing generating the trouble.
You can name it now. That is real progress, and most people never get that far.
What you still cannot do is measure it. That gap keeps this whole thing stuck at the level of a feeling.
Feelings do not survive contact with a steering committee, but evidence does.
In the next piece, I will hand you an actual diagnostic. It covers 15 items across the three dimensions.
Each one is scored against something observable rather than against your mood on the day. You will be able to put a number and a profile in front of your sponsor and have a completely different conversation.
Posted on: September 28, 2026 01:00 AM |
Permalink
