Why Every Project Runs Late, Over Budget, and Slightly Off the Rails

You said it would take a weekend. It took three. The kitchen renovation quoted at £8,000 is now £14,500 and there's a man named Dave living in your hallway. Welcome to the planning fallacy, the cognitive glitch that has been quietly ruining humanity's schedules since we first tried to build a pyramid "by Tuesday."

Whether it's a loft conversion, a wedding, a side hustle, or the Sydney Opera House (famously: ten years late, fourteen times over budget, but it does look smashing in photos), almost every project we attempt ends up later, pricier, and weirder than planned. The question isn't whether yours will. It's by how much.

Let's unpack why our brains are spectacularly bad at this — and what to do about it before you, too, are eating instant noodles in a half-tiled bathroom.

The Planning Fallacy: Your Brain Is an Optimist With a Spreadsheet

In 1979, Daniel Kahneman and Amos Tversky gave a name to something humans had been doing for millennia: confidently predicting timelines we have no business confidently predicting. The planning fallacy is our tendency to underestimate how long things will take, even when we know from past experience that we always underestimate how long things will take.

The classic study? Students were asked to predict when they'd finish their thesis. Their best guess: 34 days. Their worst-case, "if everything goes wrong" estimate: 49 days. The actual average? 56 days. Their "doomsday" scenario wasn't pessimistic enough to match reality.

The cruel twist is that this isn't fixed by experience. Veteran builders, seasoned project managers, NASA engineers — all of them blow through their own deadlines. Knowing the bias exists doesn't make you immune. It just makes you aware of how doomed you are, which is at least a start.

The reason is brutally simple: when planning, we picture the ideal path. Not the path with food poisoning, supplier strikes, surprise asbestos, and your partner deciding mid-project that actually they hate the grey.

Reference Class Forgetting: "But Mine Will Be Different"

Here's the magic phrase that derails every estimate: "This time it'll be different."

It won't. Statistically, almost never. Yet we ignore the base rate — what similar projects actually took — and focus on the specifics of our own brilliant, well-planned, definitely-on-time situation. Researchers call this taking the inside view instead of the outside view.

The outside view says: "Kitchen renovations like this typically run 40% over budget and 6 weeks late." The inside view says: "Yes, but I've got a really good contractor and I've made a spreadsheet."

Spoiler: the spreadsheet does not protect you.

The fix is humbling but effective: before estimating, look at five comparable projects and find out what they actually cost and how long they actually took. Not what the people running them claimed at the start. What happened by the end.

Then use that number. Even if it makes you wince. Especially if it makes you wince.

Scope Creep: The Silent Budget Assassin

You started with a fresh coat of paint. Then you thought, while we're at it, let's redo the skirting boards. And honestly that carpet has seen things. And shouldn't we just knock through to the dining room? It would be silly not to.

Congratulations. You have invented scope creep, the gentlest, most reasonable-sounding form of financial self-harm.

Every "while we're at it" adds 10-30% to the budget. Each individual addition feels rational. Cumulatively, they're a disaster. The cruellest part? Scope creep is invisible to your future self. When you look back, you won't say "I added too much." You'll say "renovations are just expensive these days."

A useful trick: write down your scope before you start, in detail. Then, every time you're tempted to add something, assign it a real cost in pounds and days. Suddenly "let's also do the hallway" becomes "let's also spend £2,200 and lose another weekend." Magically, half the temptations evaporate.

The other half? Fine, do them. But do them knowingly, not by accident.

Optimism Bias: We're All Slightly Delusional

Ask anyone if they're an above-average driver. Roughly 80% will say yes. Mathematically impossible. Spiritually, very on-brand for humans.

We carry the same delusion into projects. We assume we'll be more productive than usual, less interrupted than usual, and that nothing genuinely awful will happen. We mentally book every weekend for "working on the side hustle" and then forget that life contains weddings, hangovers, the flu, and Netflix.

This is why "I'll launch in three months" almost always becomes nine. Not because you're lazy. Because Week 1 You massively overestimated how many uninterrupted, high-energy hours Week 7 You was going to deliver.

The antidote is to plan based on your worst recent week, not your best. If your best week had 15 productive hours but your typical week had 5, plan around 5. Anything more is a bonus. Anything less is — well — normal life.

Strategic Underestimation: Sometimes the Lying Is on Purpose

Not all overruns are honest mistakes. The economist Bent Flyvbjerg has spent decades studying mega-projects and found something delicious: the people pitching them often deliberately lowball estimates to get them approved. He calls it strategic misrepresentation. The rest of us call it lying.

You see this with builders, contractors, and that friend who said "I'll only need to crash for a few nights." The initial number is whatever it takes to get a yes. The real number arrives later, by which point you're committed, emotionally invested, and have already demolished your kitchen.

Defence: get multiple quotes, ask explicitly what's not included, and assume the final bill will be 20-40% higher than the most expensive quote. If that breaks your budget, the project is too expensive. Better to learn that now than halfway through, surrounded by exposed pipework.

The Contingency Buffer: Plan for Chaos Like an Adult

Professional project managers don't avoid overruns by being smarter than you. They avoid them by building in contingency — a buffer of time and money assumed to be needed for unknown problems.

Standard practice in construction is a 10-20% contingency. For complex or unfamiliar projects, 25-30%. For your DIY loft conversion done at weekends with help from your mate who "knows electrics"? Honestly, double everything.

The mental trick is to treat contingency as already spent. It's not a savings cushion to dip into for nice-to-haves. It's a war chest for the boiler that explodes, the joist that's rotten, the council that needs a form you've never heard of.

If, miraculously, you don't use it — wonderful. Put it straight into savings. Do not, under any circumstances, "treat yourself" with it. That money was protecting you. Reward it by letting it grow up safely.

So What Actually Works?

You can't outsmart the planning fallacy. You can only outflank it. Here's the cheat sheet:

• Use the outside view. Find five similar projects. Use their actual numbers.
• Pad time by 50%, budget by 25%. Minimum. This isn't pessimism, it's arithmetic.
• Lock the scope in writing before you start. Price every "while we're at it" before you agree to it.
• Plan around your average week, not your fantasy week.
• Treat your contingency as already spent. If you don't need it, that's a windfall, not a budget line.

The goal isn't to predict the future perfectly. It's to stop being shocked by it. Projects run late and over budget because that's the natural state of projects. Your job isn't to defeat that reality — it's to budget like you believe it.

Now go on. Get that quote. And then add 30%.