Bent Flyvbjerg analysed 16,000 major projects and found that only 0.5% of them delivered on time, on budget, and to spec. His research identified seven common reasons why projects fail. The patterns reflect what happens on most construction jobs. “Projects often don’t go wrong so much as they start wrong.” In other words, the issues don’t emerge halfway through. They’re there from the beginning. Flyvbjerg’s solution is simple: think slow, act fast. Plan properly upfront, then execute quickly. It sounds obvious, but it works. Most teams do the opposite. They rush into action and spend months firefighting problems they could have spotted early. His recommendations include starting with why, avoiding cognitive bias, testing assumptions, and getting the right people aligned from the start. ❓So how do you make sure everyone understands what they’re trying to achieve? ❓How do you uncover assumptions before they cause problems? ❓How do you get alignment when everyone’s under pressure to start? I’ve put together a workbook that tackles these questions systematically. It supports the “think slow” phase that Flyvbjerg talks about. https://lnkd.in/eEpSzphs Now, the question you have to ask yourself (and your team) is: would you rather start fast, or finish well? Want to know how to do this? Then drop me a message and we can talk it through.
Bent Flyvbjerg's 7 reasons why projects fail, and how to avoid them
More Relevant Posts
-
Managing large construction projects? 🏗️ Say goodbye to headaches with solid timeline strategies! In our latest blog, we share top tips to master project schedules, keep costs in check, and exceed client expectations. Discover the benefits of smarter planning and how to avoid common pitfalls. 🙌 Dive in and transform your approach: [Read Now](https://wix.to/ZWg8wzz)! #ProjectManagement #ArchitecturalInnovation #ConstructionSuccess
To view or add a comment, sign in
-
Built-in project schedule float almost never works. Everyone knows it’s there, and they burn through it right away. A better approach? Publish the most aggressive schedule you can realistically hit, then have honest conversations with stakeholders about the true expected completion date.
To view or add a comment, sign in
-
High-level project schedules are dangerous. They look clean, but they hide what’s actually happening on site. If all you see is “Framing: 3 weeks” on a Gantt chart, you’re blind to the real work, the real pace, and the real risks. That’s the black box trap. And if you combine that with hourly-rate contracts, your costs will quietly spiral until it’s too late to stop them.
To view or add a comment, sign in
-
Bigger projects don’t just multiply budgets — they multiply risks. Without SOPs, schedules, and contracts in place, a $2M project can quickly turn into a $2.5M problem. My rule is simple: foundation first, then scale. I’ve seen too many contractors stretch too fast without the systems to support it. But when the foundation is strong, growth feels natural — and profitable. 👉 Have you ever seen a project grow faster than the systems behind it?
To view or add a comment, sign in
-
In construction, every project comes with its own challenges. Some days run seamlessly, while others require quick problem solving and teamwork. What matters most is finding solutions and moving the project forward. We’d love to hear from you what’s a time you faced a challenge on the job site and overcame it? Share your experience in the comments below. ⬇️ #ConstructionExcellence #ProblemSolving #TeamworkInAction #BuildingSuccess
To view or add a comment, sign in
-
In construction, every project comes with its own challenges. Some days run seamlessly, while others require quick problem solving and teamwork. What matters most is finding solutions and moving the project forward. We’d love to hear from you what’s a time you faced a challenge on the job site and overcame it? Share your experience in the comments below. ⬇️ #ConstructionExcellence #ProblemSolving #TeamworkInAction #BuildingSuccess
To view or add a comment, sign in
-
The ground beneath you can make or break a project. Ground conditions aren’t just a technicality, they’re the foundation of delivery. Here’s one of our most memorable projects that required complex ground works… We were brought in during a stage that was already deep into design. The timeline was tight. And ground investigations had been skipped to “save time.” Everyone had hoped the soil would cooperate. It didn’t. Poor ground conditions added a whopping £1.5 million to the budget; months after initial assumptions had locked in the design. YES……. £1.5 million! A tough lesson. But not an uncommon one. Here’s what we help clients understand: - In fast-tracked builds, time feels like the enemy, but skipping ground investigations is like betting your budget on a blindfolded guess. - Foundation design hinges on what's under your feet. Without proper data, you're exposed to serious financial risk. - If full investigations aren't possible early on, protect the project with smart clauses that flag cost exposure and keep your team aligned. At Legacy Manufacturing Solutions, we don’t just manage your project, we help you de-risk it. That starts with identifying what’s controllable, flagging what’s not and guiding your team through both. Let’s build smarter, together.
To view or add a comment, sign in
-
-
Can you fix it? 🤔 We’ve been asked that question more times than I can count. Usually by a client mid-way through a failing project. Timelines have slipped. Budgets have stretched. Trust is thin. Sometimes it’s the first time they’ve brought in outside help. Sometimes it’s their third attempt to get it over the line. Either way, the brief is always the same: Can you fix it? (I’d love to put a Bob the Builder reference here 👷) Our answer? Only if we can start with the truth. We need to know what’s working, what’s not, and what’s really going on behind the scenes. Because fixing a project isn’t about throwing in more people. It’s about resetting the approach - cutting the noise, getting clear on outcomes, and bringing structure back to delivery. We’ve done it before. We’re doing it now. And if you’re asking the same question, we should talk.
To view or add a comment, sign in
-
I can usually predict project delays 3 months in advance. With startling accuracy. Here are some dead giveaways: Red flag #1: "We'll figure out the requirements as we go" Guaranteed 4-week delay. Red flag #2: "This is just a rough estimate" Add 50% to whatever timeline they give you. Red flag #3: "The stakeholder is traveling but we can start without them" Prepare for complete rework. Red flag #4: "We've done something similar before" No, you haven't. Add 6 weeks. Red flag #5: "We'll just use the existing system" That system doesn't do what you think it does. It's like a demented game of Chutes and Ladders. Most project managers see delays as surprises. I see them as symptoms. Symptoms of poor planning. Unclear requirements. Unrealistic expectations. The delays aren't the problem. The preparation is the problem. Want to avoid delays? Stop starting projects that aren't ready to start. Most "urgent" projects can wait 2 weeks for proper planning. Most projects that are "ready to go!" aren't ready at all.
To view or add a comment, sign in
-
A good breakdown of planning failures that lead to project delays. I'd like to add one more for consideration: "They're all priorities!" If everything is a priority, nothing is a priority, and you spread yourself thin over too many tasks. The hard decisions about what to do now and what to do later are an essential part of project scoping that you can't set aside.
Senior Project Management Professional driving on-time, within-budget & high-quality project closure
I can usually predict project delays 3 months in advance. With startling accuracy. Here are some dead giveaways: Red flag #1: "We'll figure out the requirements as we go" Guaranteed 4-week delay. Red flag #2: "This is just a rough estimate" Add 50% to whatever timeline they give you. Red flag #3: "The stakeholder is traveling but we can start without them" Prepare for complete rework. Red flag #4: "We've done something similar before" No, you haven't. Add 6 weeks. Red flag #5: "We'll just use the existing system" That system doesn't do what you think it does. It's like a demented game of Chutes and Ladders. Most project managers see delays as surprises. I see them as symptoms. Symptoms of poor planning. Unclear requirements. Unrealistic expectations. The delays aren't the problem. The preparation is the problem. Want to avoid delays? Stop starting projects that aren't ready to start. Most "urgent" projects can wait 2 weeks for proper planning. Most projects that are "ready to go!" aren't ready at all.
To view or add a comment, sign in
More from this author
-
The Early Warning Double Standard: Up Good, Down Bad
Colin Tomlinson MBA BEng 👷🏻📝 1w -
Building Psychological Safety on Construction Sites: The Leadership Challenge We Can't Ignore
Colin Tomlinson MBA BEng 👷🏻📝 1mo -
Six Problems That Derail Construction Projects in Week One
Colin Tomlinson MBA BEng 👷🏻📝 2mo
Trailblazer in SaaS, Cloud & Customer Success | Product Innovation | Technical Account Manager | £2M+ Enterprise Portfolios | 400% CSAT Improvement | Cloud Migration & Delivery Expert | PMP & AWS Certified | London
3wColin Tomlinson MBA BEng 👷🏻📝, this framework really highlights how much those early planning decisions ripple through the entire project lifecycle. the connection between thorough preparation and smoother execution makes so much sense.