Every project manager has a failure story. The smartest ones also collect other people’s. Here are five famous project failures, what went wrong, and the habit that would have saved each one.
1. The Sydney Opera House: building before the design was finished
Today it is one of the most recognisable buildings on Earth. But construction began in 1959 with a budget of roughly A$7 million and a target of about four years. It opened in 1973 at a cost of around A$102 million. The root problem was simple: building started before anyone had worked out how to construct the famous roof shells, so parts of the work had to be redone.
The lesson: Don’t break ground on a plan with a giant unanswered question inside it. Solve, or at least test, your riskiest unknown first.
2. Denver Airport’s baggage system: too clever, too late
Denver International Airport planned a fully automated baggage system that would whisk luggage around on its own. The airport’s opening slipped by about 16 months while engineers struggled to make it work, and the delays were reported to cost millions. Test runs famously produced jammed and damaged bags. The system was eventually switched off in 2005 and replaced with conventional handling.
The lesson: An ambitious scope, a tight schedule and late testing make a dangerous combination. Test early, and always keep a fallback plan.
3. Healthcare.gov: nobody owned the whole picture
When the US health insurance website launched in October 2013, it buckled almost immediately. It was widely reported that only a handful of people managed to complete enrolment on day one. Many contractors had built separate pieces, but end-to-end testing came late and no single party was clearly responsible for how everything worked together.
The lesson: Someone must own the integrated whole, not just the parts. And a launch date should be a decision based on readiness, not a promise made in advance.
4. Berlin Brandenburg Airport: the date that kept moving
Berlin’s new airport was first planned to open in 2011. It finally opened in October 2020, roughly nine years late, with costs well above the original estimate. One of its most notorious problems was a fire-safety system that did not work as designed. Several opening dates were announced and then cancelled along the way.
The lesson: If you keep announcing new dates, you are guessing. Define what “ready” actually means, track the defects against it, and tell stakeholders the truth early.
5. The Vasa: a change request nobody dared question
In 1628 the Swedish warship Vasa sank on her maiden voyage after sailing little more than a kilometre. Historians point to late changes in what the ship was meant to carry, including extra guns and a heavier upper structure, which made her unstable. Those changes came from the very top, and apparently nobody felt able to push back.
The lesson: Every change has a cost. A project manager’s job includes saying so out loud, even to the most senior person in the room.
The common thread
Look closely and these five stories share one pattern: decisions were made before the facts were in.
Before your next project gets going, ask yourself four questions:
• What is our biggest unknown, and have we tested it yet?
• If our riskiest piece fails, what is Plan B?
• Who owns the whole result, not just their own part?
• Who is allowed to say no, and will we listen when they do?
Which of these failures feels most familiar from your own experience? Share your story with us. And if you want to build habits like these into your team, explore the project management training at PME Academy.