Why Projects Fail and What to Do About It | Capability @ Lunch Recap

Most of us have been part of a project that felt shaky from the start. Deadlines shift, expectations evolve, and despite everyone’s best efforts, the final result does not quite deliver what was intended. The good news is that failure is not inevitable. With a few practical steps, projects can be set up to succeed.

In this month’s Capability @ Lunch session, project management consultant Sean Whitaker explored the common patterns behind project failure and the practical steps teams can take to improve their odds of success.

---

Sean kicked off the session by sharing what successful organisations do differently. In these organisations, project success is the expectation, not the exception. Leaders have clear visibility of what is underway, teams feel supported, and projects are treated as a core way to deliver on strategy, not just a side effort.

From there, he outlined seven reasons projects commonly fail.

The 7 Reasons Projects Fail

1. No fit-for-purpose methodology
Without a clear way of working, teams approach projects inconsistently. But forcing every project into one rigid methodology is just as ineffective. What matters is an approach that flexes to suit the type, size, and complexity of the work, and ideally one your own team has helped build, since nobody understands how you work better than you do.

2. Losing sight of benefits
Projects are usually approved because of the outcomes they promise to deliver, not the thing being built. Over time, focus can drift toward the output itself rather than what it was meant to achieve. Without tracking benefits throughout and after delivery, it is hard to know whether a project has actually succeeded, sometimes for months or years after delivery.

3. Treating estimates as certainty
Cost, time, and resource estimates often get presented as fixed numbers, when in reality they are assumptions about an uncertain future. Organisations that do this well use techniques like reference class forecasting, drawing on real historical data, and ask for a range rather than a single figure.

4. Not capturing lessons learned
Without a consistent way to gather and apply lessons, teams end up repeating the same mistakes. Capturing what worked, what didn’t, and storing it centrally so others can find it builds capability over time. Sean shared an example of one organisation that lifted its project success rate from 40-50% to over 90% simply by consistently gathering and using lessons learned.

5. Overreliance on tools
Project management software can support visibility and consistency, but it is no substitute for good practice. Sean noted that software problems usually come down to training, not the tool itself. Investing in proper training, and having someone in-house who knows the software well, makes far more difference than the price tag of the software.

6. Choosing the wrong projects
Some projects are approved on gut feel or political pressure, with cost and time estimates that were never realistic to begin with. Even a strong team will struggle if the project itself was not viable from the start. Clear selection and prioritisation matters, and so does being willing to cancel a project that is no longer worth pursuing.

7. Limited investment in people
Project success comes back to capability. Sean was direct on this point: New Zealand is one of the only countries that does not require project managers to be certified. Experience matters, but experience paired with training and credentials beats experience alone every time.

From the Q&A

A few themes stood out in the discussion that followed:

On AI, Sean was equally direct: using it is no longer optional, but a human still needs to check everything it produces before it goes out the door.

On pushback and “courageous conversations,” Sean’s advice was to be upfront when a project has been set up to fail, whether that is unrealistic cost estimates, timeframes, or a lack of real authority to deliver. Building a culture where project managers feel supported to raise these concerns has to come from the top.

On change requests, Sean was clear: no verbal changes, ever. Every change should go through a documented process, even a lightweight one, so that the consequences of saying yes are visible before anyone commits to them.

On governance, Sean offered a sharper view than most expect: he estimates around 90 percent of project governance is theatre. Good governance should be held to the same standard as any other part of project management. If you cannot draw a direct line between a governance activity and project success, it is probably not adding value.

Practical takeaways

Across all seven pitfalls, one pattern stood out: organisations that deliver well are deliberate in how they work. A few simple actions to take away:

• Fit your approach to the project, rather than forcing the project into a fixed method
• Stay focused on what the work is meant to achieve, not just what is being delivered
• Use ranges and historical data when estimating, rather than single figures
• Put in place a simple, shared way to capture and access lessons learned
• Ensure all changes go through a clear, documented process
• Be prepared to have honest conversations when expectations are unrealistic

---

If you are keen to build your project management skills further, Sean runs two courses with us. Project Management Fundamentals is a one-day introduction to the essentials, while Practical Project Management is a two-day course for those looking to build deeper confidence and capability across the full project lifecycle. Use code CAL10 to save 10% on either course.

The Capability @ Lunch series is brought to you in partnership by Kāpuhipuhi Wellington Uni-Professional and Hāpai Public. Browse our upcoming events here.