10 reasons why projects fail - and what to do about it

A few months ago, I found myself sitting in a meeting room with a whiteboard full of arrows, milestones, and optimistic deadlines. It was one of those sessions where everything looked aligned. The plan was tight. The team was motivated. The logic made sense. And still, I remember thinking: This is probably not how it’s going to play out. Not because the people in the room weren’t capable. Quite the opposite. But because I’ve seen enough projects - big and small - to know that failure rarely comes from a lack of intelligence or effort. It comes from something more subtle. Something harder to spot.

#projectmanagement

Before diving into the reasons, it’s worth briefly pausing on the person behind the research.

Bent Flyvbjerg is a Danish professor at Oxford University and one of the world’s leading experts on megaprojects and decision-making. Over decades, he has studied thousands of projects - across infrastructure, IT, policy, and business - and consistently found the same pattern: Projects don’t fail randomly. They fail in predictable ways.

What makes his work powerful is that it doesn’t blame complexity alone. It points to us - our psychology, our incentives, and the way we make decisions under uncertainty.

Below are 10 of the most common reasons projects fail, reframed in a way I’ve found useful in practice - along with what you can actually do about them.

1. Over-optimism

We don’t just hope things will go well - we expect it. Especially when we’re close to the project.

In practice, this shows up as timelines that assume everything runs smoothly. Stakeholders respond quickly. Dependencies align. Nothing unexpected happens.

In one project, we assumed a key partner would move at our pace because they had verbally committed. They didn’t. Not out of bad intent, but because they had other priorities. Our optimism wasn’t malicious - it was just detached from reality.

What to do:

Actively separate intention from probability. Ask: If everything doesn’t go to plan (which it won’t), where do we slip first?

2. Planning fallacy

Even when we know similar projects took longer, we believe this one will be different.

This often happens because we focus on tasks we can see, not the ones that emerge along the way - alignment meetings, rework, waiting time, small misunderstandings that compound.

I’ve noticed this especially in cross-functional work. The actual execution is rarely the bottleneck. Coordination is.

What to do:

Add a “coordination buffer” to your plan. Not just for tasks, but for people.

3. Anchoring

The first number mentioned in a project - deadline, budget, scope - tends to stick.

Even if everyone intellectually knows it’s a rough estimate, it becomes a reference point that’s hard to move away from. Suddenly, the conversation shifts from what is realistic to how do we make this fit?

I’ve seen teams spend weeks trying to “optimize” a fundamentally unrealistic timeline instead of challenging it.

What to do:

Start with ranges, not fixed numbers. And revisit them explicitly before committing.

4. Confirmation bias

Once we believe in a plan, we start filtering reality to support it.

We highlight progress and downplay risks. We interpret ambiguous signals as positive. We selectively hear what confirms our direction.

In meetings, this often shows up as subtle alignment: people nodding along, building on the same narrative, rarely challenging assumptions.

What to do:

Make it someone’s job to disagree. Not personally - but structurally.

5. Strategic misrepresentation

Sometimes projects look better on paper than they actually are.

Not necessarily because people are dishonest, but because there’s pressure to get approval, secure funding, or show momentum. So risks are softened. Upsides are emphasized.

I’ve felt this tension myself: how do you stay realistic without killing energy?

What to do:

Be explicit about uncertainty. Instead of hiding it, frame it as something you actively manage.

6. Groupthink

High-performing teams are particularly vulnerable here.

When trust is strong and people are aligned, disagreement can feel unnecessary - or even uncomfortable. So teams converge quickly around a shared story.

But fast alignment often comes at the cost of depth.

I’ve been in rooms where everything felt “easy” - and that should have been a warning sign.

What to do:

Slow down moments of agreement. Ask: What are we not seeing?

7. Underestimating complexity

We simplify reality to make it manageable.

But projects - especially those involving multiple stakeholders - are rarely linear. They behave more like systems. One delay creates another. One misalignment spreads.

In one case, we underestimated how one small dependency (legal approval) would cascade into multiple delays across teams.

What to do:

Map second-order effects. Not just what happens next - but what happens after that.

8. Escalation of commitment

Once we’ve invested time, energy, and reputation, it becomes harder to stop.

So we continue. We justify. We reframe.

I’ve seen projects continue long after it was clear they wouldn’t deliver the intended value - simply because stopping felt like failure.

What to do:

Define success and failure upfront. And agree on when to pivot or stop - before emotions get involved.

9. Availability bias

We rely on what’s top of mind.

If we recently had a successful launch, we assume we can replicate it. If we’ve worked with a certain type of partner before, we expect similar behavior.

But our memory is selective - and often misleading.

What to do:

Look beyond your own experience. Use data, not just anecdotes.

10. Incentive misalignment

This is often the most underestimated factor.

Different stakeholders have different goals - some want speed, others want quality, some want visibility, others want control.

If this isn’t surfaced early, it creates friction later.

I’ve experienced projects where everyone was “aligned” - until execution started. Then priorities diverged.

What to do:

Have the uncomfortable conversation early: What does success look like for you? And what are you optimizing for?

The uncomfortable part

None of these reasons are about lack of intelligence.

They’re about being human.

And that’s what makes project leadership difficult. It’s not just about structure, timelines, and execution. It’s about navigating your own thinking - and the thinking of others.

In my own work, I’ve started to notice that the biggest risks rarely sit in the plan itself. They sit in the assumptions behind it. The things we don’t question because they feel “obvious.”

A few practical shifts that have helped me

If I had to boil this down into a few repeatable habits:

• I try to spend more time looking backward (what actually happened before) than forward (what we hope will happen)

• I deliberately introduce friction in key decisions

• I separate ambition from realistic probability

None of this removes uncertainty. But it changes how you engage with it.

A final reflection

Project management is often treated as a technical discipline.

But in reality, it’s deeply psychological.

And maybe that’s why it’s so easy to underestimate - and so hard to master.

So the next time you’re working on something that matters, it might be worth asking:

Which of these 10 traps am I most likely falling into right now?

And more importantly:

Do I actually want to know the answer?