Why Projects Still Fail and How to Prevent It

If you have spent any time in project management, you've probably heard these statistics. Depending on the study, a significant percentage of projects fail to meet their original objectives. They finish late and over budget or do not deliver on all expectations. The surprising part is that we've known why they fail for decades.

Research from industry organizations, academic institutions, and professional associations has consistently identified many of the same root causes. The top causes gravitate around disengaged executive sponsors, uninvolved users, poorly defined requirements, and communication breakdowns, with many organizations repeating the same mistakes.

While there have been some modest improvements, the pace of improvement has been frustratingly slow. That raises an important question: If we already know the leading causes of project failure, why do so many organizations continue to struggle? The answer has less to do with project management techniques than with organizational priorities and culture, which can make the audience feel empowered to influence change.

The Research Has Been Consistent

Over the years, I have shared findings from organizations such as the Standish Group, Meta Group, the Project Management Institute (PMI), and numerous academic researchers with hundreds of project management students. While each study uses different methods and measurements, the themes remain consistent. Projects fail because organizations neglect the fundamentals, which remain relevant today.

None of these findings are particularly surprising. In fact, most experienced project managers recognize them immediately. The challenge is convincing organizations to address them consistently.

Executive Sponsorship Is More Than Budget Approval

One of the biggest misconceptions about project sponsorship is that sponsors approve funding and attend the kickoff meeting. Successful sponsors do much more. Their leadership and involvement are visible throughout the project, and it demonstrates to the organization that the project matters.

Unfortunately, many sponsors disappear after the project begins. They become occupied with other responsibilities, leaving project managers without the authority needed to resolve conflicts or obtain critical decisions.

When executive sponsorship weakens, projects drift. Decisions are delayed, priorities become unclear, and team members receive conflicting direction. Before long, schedules slip, and costs rise. A committed sponsor cannot guarantee project success, but the absence of one dramatically increases the likelihood of failure.

Users Are Partners, Not Spectators

Projects are built for users, yet users are often involved only at the beginning and the end. At the beginning, if they are lucky, they are invited to attend a few requirements meetings. Yet many large organizations that should know better still dictate requirements without user input. At the end, users are asked to test the finished product. Everything else is frequently handled without meaningful user participation.

That approach almost guarantees disappointment. Users possess knowledge that project teams do not have. They understand daily workflows, customer needs, operational challenges, and practical constraints. When users remain engaged throughout the project, they help identify issues before they become expensive problems. When they don't, assumptions replace facts. The result is often a technically successful project that fails to solve the original business problem, or a solution that users fail to embrace.

Requirements Are the Foundation

Poor requirements continue to be one of the leading causes of project failure because every decision made later depends upon them. Incomplete and unclear requirements lead to scope changes and misunderstandings. Conflicting requirements create frustration. Missing requirements remain hidden until testing or implementation, when correcting them is significantly more expensive.

Requirements management is not a one-time event completed during project initiation. It is an ongoing process of validating assumptions, clarifying expectations, managing changes, and ensuring that everyone continues working toward the same objectives. Organizations that invest sufficient time defining requirements spend far less time fixing mistakes later.

A Classroom Discussion

Several years ago, I was teaching a corporate project management class for UC San Diego Extended Studies at a major defense contractor. On the final day, the students were completing their examination, so instead of introducing new material, I presented several industry studies and research findings to stimulate discussion.

We reviewed project management research spanning more than two decades. Although the studies came from different organizations and researchers, the conclusions were again similar.

After reviewing the findings, I asked a simple question. "If we've known the leading causes of project failure for over twenty years, why haven't we solved the problem?"

The discussion that followed was one of the most engaging conversations I've had in a classroom. The students, many of whom were experienced professionals, identified several organizational issues such as misaligned priorities and lack of stakeholder engagement that continue to undermine project success. Their observations closely matched what I have seen throughout my own career.

Too Much Focus on Certification

Professional certifications have elevated the project management profession, and they provide valuable evidence of knowledge and commitment. However, certifications are only part of the solution.

The body of knowledge supporting project management has arguably expanded by a factor of 10 over the years. At the same time, training programs continue to devote roughly the same number of instructional hours as they did when the knowledge base was smaller. We ask students to learn considerably more material without giving them additional time to develop practical skills.

Organizations sometimes compound the problem by assuming certifications prepare someone to manage complex projects. Successful project managers continue learning throughout their careers. They develop communication and decision-making skills through experience. Those capabilities grow through learning and practical application, not through passing an exam.

The Accidental Project Manager

One of the most common situations I encounter is the accidental project manager. These are people who excel in their technical roles. As a reward, management places that individual in charge of a project. Unfortunately, technical expertise and project leadership require very different skill sets.

Many accidental project managers suddenly find themselves responsible for planning, scheduling, budgeting, stakeholder communication, conflict resolution, and leadership with little or no formal preparation.

Neither the PMBOK® Guide nor a software manual is designed to teach someone how to manage projects. They are valuable references, but they cannot replace structured education, coaching, and experience. Without proper preparation, even talented professionals struggle.

When Project Managers Invest More

One observation has stayed with me throughout years of teaching continuing education. Many of my students pay for their own education. After working a full day, they attend evening classes because they recognize that stronger skills will help them succeed. Some are preparing for certification while others want to be better project leaders. Too often, however, their employers provide little financial support.

That should give every organization pause. If project success is truly important, why are so many aspiring project managers investing in themselves while their organizations invest elsewhere? Organizations spend millions of dollars on technology, equipment, and facilities while dedicating comparatively little to developing the people responsible for delivering strategic initiatives. That imbalance is difficult to justify.

Waste Is A Big Problem

Long before Lean, Agile, and Six Sigma became familiar terms, I learned to look for waste. When I first learned computer programming, we worked with systems that offered only 8K of usable memory. Every byte mattered. In the evenings, my classmates and I challenged one another to make our programs smaller, faster, and more efficient. We celebrated every improvement because better programming required careful thinking rather than additional resources.

Later, I earned my first professional income helping professors reorganize programs originally written for much larger computer systems so they could operate efficiently on our college equipment. Those lessons stayed with me throughout a twenty-year career at GE and every project I have managed since.

Today, organizations possess computing power we could only imagine back then. Yet many still tolerate enormous amounts of waste. Projects routinely experience unnecessary meetings, duplicated work, poor communication, repeated mistakes, delayed decisions, and costly rework. Across an entire project portfolio, these inefficiencies consume millions of dollars while reducing customer satisfaction and delaying strategic objectives. Technology alone cannot eliminate waste. Organizational discipline does.

Too Busy to Improve

Perhaps the most common explanation I hear is that organizations are too busy. Ironically, these are often the organizations that would benefit most from stronger project management. The most successful organizations I've worked with maintain both short-term and long-term strategic plans. They understand that investing time in planning, developing people, and improving processes ultimately allows them to respond more effectively to change.

Organizations that postpone improvement because they are too busy frequently remain trapped in a cycle of constant firefighting. Being too busy to improve guarantees that tomorrow will look much like today.

A Culture of Continuous Improvement

Every project provides valuable lessons. Unfortunately, many organizations hold lessons learned meetings simply because their methodology requires them. Notes are documented, archived, and rarely consulted again. The same mistakes appear on future projects.

Successful organizations approach lessons learned differently. They look for recurring patterns, identify opportunities for improvement, update their processes, and share knowledge across the organization. Continuous improvement is not an annual initiative. It is an ongoing commitment to becoming better with every project. Organizations that consistently learn from experience gradually improve project outcomes while reducing waste, increasing quality, and building stronger project teams.

We Already Know the Answers

The project management profession does not need another study to tell us why projects fail. The evidence has been remarkably consistent for years. The organizations that achieve the greatest success are not those with the newest software or the most sophisticated methodologies. They are the organizations that invest in their people, engage their sponsors, involve their users, manage requirements effectively, reduce waste, and continually improve their processes.

Perhaps the better question is no longer why projects fail. We should be asking why so many organizations continue to ignore what decades of research have already taught us. When organizations commit to applying those lessons consistently, project success becomes less dependent on luck and more capable of producing expected outcomes.

Related Articles:

Why Communications Separates Certified PMs From the Rest

Avoiding Common Project Management Mistakes

How to Succeed as an Accidental Project Manager

Additional Resources:

Why do Projects Really Fail?

Avoiding Project Failure and Ensuring Success