The hidden causes of project failure and how to overcome them

The world continues to move at pace, and business conditions are more volatile. Projects now operate in a constant VUCA environment: volatile, uncertain, complex and ambiguous. That means plans can be overtaken by events, assumptions can quickly become outdated, and a project that once made sense may stop being the right use of time, money or people. Any organisation waiting for certainty before acting risks stagnating, because certainty is rarely available.

Why stopping a project can be the smartest decision

Stopping a project is not automatically a failure. Sometimes the best decision is to stop a project, learn from it and move resources to an initiative that creates more value. A project-driven business should be comfortable making that call when the evidence supports it. Procter & Gamble’s portfolio simplification is a useful example: the company chose to focus on the brands that created most of its sales and profit, rather than spread effort too thinly. The lesson is simple. Stopping lower-value project work can be a disciplined business decision, which improves project output where Return-on-Investment is greatest.

If we accept that the world is changing at pace, we also need to accept the pressure this places on strategy, projects and decision-making. Projects rarely fail because of one issue alone. More often, failure builds through many factors: poor clarity of the project story, weak benefits understanding, too many competing priorities, overloaded resources, slow decisions, or stakeholder conflict that is left unresolved at the start. In a fast-moving environment, even a good project can drift if its purpose is not regularly tested against the wider business needs.

Common causes of project failure in fast-moving organisations

All of this creates noise. That noise impacts delivery teams, sponsors, stakeholders and the board. If it is not managed, it can slow progress, damage end benefits and increase costs. The question is not whether volatility exists. It does. The real question is how leaders respond to it. Having someone at board level who understands transformation and project delivery can help, especially when quick judgement is needed. But this alone will not fix the wider causes of project failure.

The role of leadership in managing project uncertainty

Culture and framework matter just as much. Leaders need to ask whether they are creating a fixed mindset, where challenge is treated as resistance, or an open learning mindset, where reality can be discussed honestly. Avoiding difficult truths may feel easier in the short term, especially where reputation, incentives or internal politics are involved. But it rarely protects the project, the business or the individuals involved. It usually increases stress, encourages defensive behaviour and makes poor decisions more likely.

Stress builds in a fixed mindset. When people feel under threat, they are less likely to raise concerns, challenge assumptions or suggest better options. Communication narrows, trust drops and the project loses access to the full intelligence of the team. That makes it harder to deliver on time, on budget and with the expected benefits. Meaning it costs a business financially, damages confidence both internally and externally and reduces competitive advantage.

Why mental health matters for project delivery performance

This is why mental health should not be seen only as a well-being issue. It is also a delivery issue. Poor mental health costs UK employers billions each year, while investment in workforce wellbeing has been shown to deliver a positive return. For project-led organisations, the wider benefit is clear: healthier teams are more likely to communicate well, solve problems early and deliver strategic goals. In practical terms, it creates a stronger environment for delivery because teams are more confident to speak early, before risks escalate.

There are many ways to create better conditions for project success, and three areas deserve particular attention.

Three ways to build better conditions for project success

First, project leaders should build a sense of fairness. Fairness is not always easy because it is shaped by individual, team and organisational perceptions. Even so, people are more likely to stay engaged when decisions feel transparent, proportionate and consistent. This becomes especially important during difficult phases of delivery, when pressure rises and trust can be tested.

Second, leaders should encourage an open mindset. Projects need an evolving cycle: listen, test, discuss, adjust and improve. Challenge should not be treated as negativity. Used well, it improves delivery and helps avoid bigger problems later. Honest, timely feedback can prevent financial loss, reputational damage, operational disruption and weak benefits realisation. Human communication still needs a human touch, even when the tools around us are becoming more technically intelligent.

This links directly to psychological safety. People should be able to raise issues and propose solutions without fear of blame, ridicule or exclusion. A project team needs all its brainpower, artificial and human, to succeed. Psychological safety can be damaged quickly by blame culture or by consultation that looks good on paper but does not genuinely listen or explain the reason behind a decision.

Businesses can check mindset through anonymous feedback, pulse surveys and regular team health checks. Used properly, these tools help leaders understand the health of the project culture. Culture must start at the top and then stretch out through the organisation.

Lastly, diversity helps because it brings different views, experience and judgement into the room. Diversity is many things. It is not just sex or ethnicity, although these are important. It is also age, work and life experience, learned skills, background, personality and many other factors that influence how people see problems and make decisions.

Technology can support this, but it cannot replace it. AI can help with risk analysis, milestone tracking, or comparison of delivery milestones against business requirements. What it cannot do is build trust, handle emotion, resolve conflict or bring people with the project and ultimately the business. These will always be leadership skills, developed through experience, education and reflection.

In conclusion, being a project manager is often like being a mini-CEO. A project manager must understand business and project strategy, consider costs, mitigate risks, motivate people to deliver, and keep project benefits to the fore. The more autonomy available, and the flatter and more responsive the organisation is around them, the greater the chance of success. A successful project-driven business is not one that simply runs more projects. It is one that focuses on the projects that matter most, then creates the culture and conditions for those projects to deliver.