Most projects don’t fail suddenly. They fail predictably. And yet we still act surprised when they do.

Not because the work is impossible but because the warning signs were there from the beginning, quietly accepted as “normal.”

Decades of research show that projects fail in highly repetitive, painfully consistent ways.

The Standish Group’s CHAOS research has repeatedly found that only ~30% of projects are considered successful. The rest are either challenged, over budget, delayed, under-delivering, or fail outright. In this context, failure doesn’t just mean the project was hard or didn’t go exactly as planned. It means the project did not deliver the required outcome.

Project failure is not the anomaly. It is the pattern.

Many of the practices we’ve accepted as “normal” quietly set projects up to struggle from day one. The warning signs appear early, get politely ignored, and are later rewritten as “unexpected challenges.”

Here are seven of them.

1. No One Can Clearly Explain Why the Project Exists

The “why” is your north star.

Why are we doing this?
Why now?
Why this instead of something else?

When the purpose is vague, everything becomes negotiable resulting in scope drifting, priorities shifting and decisions stalling.

Unclear goals, shifting priorities, and lack of alignment with organisational strategy are consistently identified as primary drivers of project failure (PMI, Pulse of the Profession).

A project without a clear why doesn’t explode. It slowly erodes.(PMI; Prosci, 2020).

Clarity of purpose is not a nice-to-have. It is the foundation every future decision should return to.

2. The Solution Was Chosen Before the Problem Was Understood

This is where projects quietly lock in risk before they understand what they are trying to solve. The tool becomes the answer. The organisation bends around it.

When the solution is chosen before the problem is clear, discovery becomes justification. Requirements are written to fit the product. Gaps are labelled “future improvements” instead of signals the solution does not fit.

Projects with unclear early requirements and premature commitment to solutions are more likely to experience scope instability and costly rework (Flyvbjerg & Budzier, 2011). Similarly, initiatives driven primarily by technology, rather than clearly defined business problems with measurable outcomes, frequently underdeliver on value (McKinsey & Company, 2018).

If discovery starts after procurement, you are not designing a solution. You are defending one.

3. The Timeline Was Based on Optimism, Not Reality

When deadlines are locked in early, driven by executive pressure, financial cycles, regulatory commitments, or public announcements, before the work understood.

Political pressure in early forecasting distort initial estimates and contribute to cost overruns and schedule delays (Flyvbjerg & Budzier, 2011). Behavioural science calls this the planning fallacy where teams consistently underestimate effort and complexity even when history tells them otherwise. (Kahneman & Tversky, 1979).

Timelines built around technical readiness rather than organisational readiness can also produce poor outcomes

Essentially, the system might be ready to go live. But the business isn’t. 

When timelines are dictated by technical readiness alone, time for training, process redesign and sensemaking are deferred until after implementation, when change is harder and options are narrower.

Benefits are far more likely to be realised when organisations invest in readiness, capability building, and structured change support before implementation (PMI; Prosci, 2020).

Lock in the deadline too early, and you may overlook the effort, capacity, and readiness required to meet it.

4. Everyone Is Overcommitted

One of the most persistent delivery myths is that people can do project work “on top of their day job.”

They can’t, or at least not sustainably.

Over time, the cost shows up elsewhere, either through slower decisions, rushed outputs, declining quality, or burnout.

Cognitive psychology research shows us that multitasking and constant task switching reduce performance and increase delays (Kahneman, 2011). This persistent priority conflict and unrealistic resourcing assumptions are strongly associated with poor project performance. (PMI, Pulse of the Profession).

If people are not formally allocated to the project, the project is not truly resourced. It is just running on borrowed time.

5. Stakeholder Engagement Happened… Technically

When stakeholders are engaged after the solution is chosen, the plan is built, and the timeline is locked. They are not being engaged. They are being informed. 

Stakeholder involvement during problem definition and decision-making is strongly associated with stronger commitment and improved project outcomes (Beringer, Jonas & Kock, 2013; Yang et al., 2011).

Even when engagement starts early, it must be continuous and meaningful. Sporadic or symbolic engagement does little to improve alignment or decision quality (Freeman, 1984; Bryson, 2004).

People don’t disengage because they dislike change.
They disengage because they were never truly included.

6. Decision-Making and Governance Are Unclear

A project can have weekly steering committees, polished dashboards, and colour-coded RAG statuses and still be unmanaged.

When governance becomes routine instead of a decision-making discipline, problems and risks get raised, but nothing happens. This results in risks not being mitigated and decisions and ownership not being clear. 

Unclear decision rights, slow escalation, and weak accountability are strongly associated with cost overruns and delivery failure (Too & Weaver, 2014).

Meetings do not keep a project on track.
Clear ownership and timely decisions do.

7. Change Management Arrives Late

Adoption failure is one of the quiet killers of projects.

A system can be implemented on time and still fail to deliver benefits if people are not ready to work differently.

Organisational and people-related factors are consistently shown to be dominant drivers of underperformance, even when technical delivery is sound (McKinsey & Company). Projects with effective change management are significantly more likely to meet objectives, stay on schedule, and stay within budget (Prosci, 2020).

When change engagement starts early teams have time to build clarity, capability and confidence before implementation. 

When it starts late, projects enter recovery mode. Workarounds multiply. Confidence drops. Value is delayed.

Psychological safety is also critical for early issue escalation and adaptive decision-making. When people do not feel safe raising concerns, small issues remain hidden until they become expensive problems.

Projects do not fail because change is difficult.
They fail when organisations treat adoption as an afterthought rather than a condition for success.

Final Thought

What makes these signs dangerous is not that they are rare. It’s that they feel normal. Each sign reflects the same pattern we continue to see: we ignore human and organisational realities in favour of tidy plans and optimistic assumptions.

Projects rarely collapse because of a single catastrophic decision. They unravel because small, early signals were tolerated instead of addressed.

The good news? These patterns are predictable. Which means they are preventable.

Confront them early, and you increase your chances of delivering real outcomes and benefits.

References

Beringer, C., Jonas, D., & Kock, A. (2013). Behavior of internal stakeholders in project portfolio management.
Bryson, J. (2004). What to do when stakeholders matter.
Edmondson, A. (2018). The Fearless Organization.
Flyvbjerg, B., & Budzier, A. (2011). Why Your IT Project May Be Riskier Than You Think. Harvard Business Review.
Kahneman, D. (2011). Thinking, Fast and Slow.
Kahneman, D., & Tversky, A. (1979). Intuitive prediction: Biases and corrective procedures.
McKinsey & Company. (2018). Unlocking Success in Digital Transformations.
PMI. Pulse of the Profession Reports.
Prosci. (2020). Best Practices in Change Management.
Standish Group. (2020). CHAOS Report.