Why So Many Well-Run Projects Still Fail to Deliver Value

A project can look healthy, right up until the moment everyone realizes it has failed.

The schedule is green. The budget is under control. The team is closing action items and producing exactly what the plan called for.

Then the product launches... and customers don't use it.

The new process goes live... and employees quietly work around it.

The facility opens... but operating costs erase the expected savings.

The technology performs exactly as designed... and solves the wrong problem.

None of these are failures of execution. They are failures of clarity. The team delivered something. It just wasn't the outcome the organization actually needed. That distinction matters more than ever.

The uncomfortable evidence

A July 1, 2026 article from the Project Management Institute, "What 22,000 Projects Reveal About Success and Failure," summarizes a conversation between PMI President and CEO Pierre Le Manh and Alexander Budzier, a Fellow in Management Practice at Oxford's Saïd Business School.

Budzier's research dataset spans more than 22,000 capital investment projects across 126 countries. Roughly half delivered on budget or better. Only 8 percent delivered on both budget and schedule. Once the promised benefits were factored in, the success rate dropped to about 0.5 percentone, project in every 200 to 250.

That figure shouldn't be applied indiscriminately to every internal initiative or product launch; the dataset skews heavily toward capital investment and major-program environments. But the underlying lesson travels well beyond it.

Completing a project is not the same as creating a successful outcome.

A project can be managed efficiently and still produce little value. It can also blow through its original schedule and budget and end up creating extraordinary value. Scope, schedule, and cost still matter, but they're just not necessarily sufficient on their own.

PMI's broader research backs this up. Its 2024 Maximizing Project Success study, based on a survey of 10,000 project professionals and 150 in-depth interviews defines success as a combination of execution and value. Seventy-four percent of respondents tied success to finishing on time, on budget; and with a valuable outcome. PMI's conclusion is that organizations improve outcomes by strengthening three disciplines: planning more intelligently, building enough clarity to adapt deliberately, and defining success before execution begins.

Better planning doesn't mean predicting everything

Planning is sometimes framed as the opposite of agility. It isn't. Planning is how a team makes its current understanding visible, what the organization is trying to accomplish, what has to be true for the approach to work, where the real uncertainty sits, which decisions are still open, and how the team will know when circumstances have shifted.

A weak plan produces a date. A strong plan produces understanding.

The PMI article reports that most projects spend roughly 3 to 5 percent of total cost on planning, while the strongest performers in Budzier's research invested 20 to 30 percent. His point isn't that every project should mechanically hit the same percentage, it's that organizations routinely create false urgency by rushing through the exact window when decisions are cheapest to get right.

Infrastructure data points the same direction. The UK's former Infrastructure and Projects Authority found that projects with strong front-end planning ran about 20 percent less costly and 10 to 15 percent faster than average. Early planning lets teams catch design changes while those changes are still cheap to make.

None of this is an argument for months of analysis, excessive documentation, or waiting until every uncertainty disappears. That moment never arrives. It's an argument for doing enough thinking upfront to tell the difference between a calculated decision and a hopeful assumption.

Before major execution begins, a team should be able to explain:

• the problem that needs to be solved

• the outcome the organization expects (and needs)

• who must use, support, or benefit from the result (and seeing this through the lens of their experience)

• the assumptions the plan depends on

• the most consequential risks and dependencies

• the evidence behind the estimated cost and duration

• the conditions that would require the plan to change

Planning should make uncertainty easier to discuss not easier to hide.

A good plan makes adaptation possible

Projects don't succeed because the original plan was perfect. They succeed because the team can recognize when the original plan is no longer adequate. That takes clarity.

Without it, a change in direction looks like failure. People protect old commitments, defend outdated assumptions, and keep reporting against targets that no longer reflect reality.

With it, adaptation becomes a deliberate management decision. The team can ask:

What has changed? What have we learned? Which assumptions no longer hold? Does the expected outcome still justify the remaining investment? What should we preserve, stop, accelerate, or redesign?

This holds across methodologies. A predictive project shouldn't treat its approved baseline as a contract with the future. An agile project shouldn't use iteration as an excuse to start without a clear problem, intended outcome, economic rationale, or decision framework. A hybrid project shouldn't become a poorly integrated compromise; some activities rigid, others improvised, nobody clear on how decisions actually get made.

PMI's 2024 research found agile, hybrid, and predictive approaches can all produce similar performance results. Success depends less on loyalty to a methodology and more on choosing an approach that fits the work and giving the team room to use it well. Methodology matters. Context matters more.

A construction project, a software implementation, an organizational transformation, and a community program won't need identical planning practices. But every one of them needs a shared view of the outcome, transparent assumptions, real feedback loops, clear decision authority, and a disciplined way to respond to new information.

The goal isn't to prevent change. It's to prevent drift change that happens without a conscious decision about what it does to value, risk, cost, schedule, or stakeholder expectations.

Define success before you measure progress

Many projects launch with an approved solution and an incomplete definition of success.

"Install the system." "Open the facility." "Redesign the process." "Launch the program." "Complete the transformation."

These are outputs. They don't explain why the work matters.

A stronger definition of success answers at least four questions:

• What measurable condition should improve? Cycle time, customer experience, revenue, cost, safety, quality, access, compliance, employee capability, mission performance, pick the one that actually matters here.

• Who has to experience the benefit? A technically sound solution that users reject rarely produces lasting value.

• What constraints matter? Schedule, affordability, quality, risk exposure, regulatory obligations, and operational disruption still require disciplined management.

• When will success actually be evaluated? Some benefits show up at delivery. Others don't become visible until months or years after the project team has moved on.

This doesn't abandon the traditional project-management (iron) triangle, it puts it in context. Cost and schedule tell you whether the organization delivered efficiently. Benefits and outcomes tell you whether it delivered wisely.

PMI's research encourages project professionals to stay accountable for value, reassess project parameters as needs and technologies shift, and continually realign stakeholders around measurable outcomes. That accountability shouldn't end at handover. Someone has to stay responsible for adoption, operational integration, benefits measurement, and corrective action after the project's outputs land in the organization. Otherwise, the project gets declared complete exactly when the hard work of realizing value begins.

Look outside the project before looking deeper inside it

One of the more interesting findings in the PMI article is what Budzier calls the uniqueness trap.

When people convince themselves their project is unlike anything attempted before, they stop looking for useful comparisons. They discount historical evidence, lean too heavily on internal assumptions, and talk themselves into believing that other teams' difficulties don't apply to them.

Research by Bent Flyvbjerg, Alexander Budzier, M.D. Christodoulou, and M. Zottoli found a statistically significant link between perceived project uniqueness and underperformance. Their recommendation: reference-class forecasting, premortems, similarity-based forecasting, and other forms of "decision hygiene" to counter the bias.

Every project has distinctive features. Very few are genuinely unprecedented. This is why recognizing common patterns across seemingly unrelated fields can help teams uncover solutions that might otherwise remain hidden. A hospital system and a financial platform look nothing alike on the surface, but both involve data conversion, user adoption, workflow redesign, training, security, and operational transition. A public infrastructure project and a corporate transformation look nothing alike either, but both involve uncertain requirements, multiple stakeholders, scarce expertise, governance delays, and optimistic forecasts.

Good planning asks two questions, not one. "What's special about this project?" helps you tailor the approach. "What is this project similar to, and what happened when others attempted comparable work?" keeps you honest.

The discipline beneath every methodology

Project success is sometimes discussed as though the answer is finding the right framework. Adopt agile. Strengthen governance. Improve scheduling. Use artificial intelligence. Create a PMO. Each of these can help. None of them substitutes for clarity.

Regardless of methodology, successful projects tend to share the same underlying disciplines. They invest enough thought to understand the work before accelerating it. They define success in terms of outcomes, not just outputs. They make assumptions, risks, and dependencies visible instead of implicit. They use evidence from comparable efforts rather than treating the project as exempt from history. They build feedback loops that let the plan evolve without letting the project drift. And they keep someone accountable for value long after the deliverable is done.

The purpose of planning was never to create the illusion that the future is controllable. It's to help people see clearly enough to make better decisions as the future unfolds.

That may be the most transferable lesson in the research PMI highlighted. Successful projects aren't defined by the absence of surprises. They're defined by an organization's ability to recognize what matters, learn faster than conditions change, and keep directing its resources toward an outcome worth achieving.

At your next project review, the most useful question probably isn't "Are we following the plan?"

It's this: Are we still solving the right problem, for the right people, with a plan that reflects what we now know?

This is the gap I spend most of my time closing with clients, not writing better plans on paper, but building the discipline that lets teams tell the difference between progress and drift before it causes them pain, or costs them a program. If your organization is delivering on schedule but not on outcome, that's usually a clarity problem, not an execution problem, and it's solvable.

Sources:

• Project Management Institute. "What 22,000 Projects Reveal About Success and Failure." July 1, 2026.

• Project Management Institute. Maximizing Project Success: What Is Project Success? November 2024.

• Project Management Institute. "Essential 2024 Insights for Project Professionals." December 19, 2024.

• Infrastructure and Projects Authority. "Setting Up for Success: The Importance of Front-End Loading." September 9, 2020.

• Flyvbjerg, Bent; Alexander Budzier; M.D. Christodoulou; and M. Zottoli. "Uniqueness Bias: Why It Matters, How to Curb It." Saïd Business School Working Paper, 2024.