Hello {{first_name|Motivated and Miffed Community}},

You said it'd take a week. Three weeks later you're still in it. You're not disorganized and you're not a bad estimator — you're just using the wrong inputs. The Planning Fallacy is one of the most documented cognitive biases in behavioral science, and it doesn't care how experienced you are. Nobel laureates underestimate project timelines. NASA engineers underestimate project timelines. You, estimating how long it'll take to "clean up" your Notion workspace, stand no chance.

→ The Playbook's section on deadline engineering covers the structural version of this system. If you've ever shipped late on something you planned out carefully, that chapter was written for you. ⬇️

The Move: Add a 30% buffer to every time estimate you make today — not as a guess, but as a policy.

The Evidence: Research by Roger Buehler and colleagues found that people completing a task for the second time still underestimate completion time by roughly the same margin as the first — suggesting that experience alone doesn't correct for the bias. The fix isn't more experience; it's an externally applied correction factor.

Start Here: Pick one task on your list right now. Whatever time you estimated — multiply it by 1.3 and reschedule accordingly. Don't second-guess the math. Just do it once and see what happens.

Ready to transform artificial intelligence from a buzzword into your personal revenue generator?

HubSpot’s groundbreaking guide "200+ AI-Powered Income Ideas" is your gateway to financial innovation in the digital age.

Inside you'll discover:

Download your guide today and unlock a future where artificial intelligence powers your success. Your next income stream is waiting.

Get Your Guide

Here's what the Planning Fallacy actually is: a documented tendency to predict best-case scenarios for your own future tasks while ignoring how similar tasks actually went in the past. It's not hope. It's a feature of how the brain constructs forward-looking narratives — it focuses on the specific plan in front of you rather than the base rate of how projects like this one usually land.

Kahneman and Tversky named it in 1979. It hasn't gotten less real.

The frustrating part is that you probably know, somewhere in the back of your head, that things take longer than expected. You've lived through enough "this should only take an hour" moments. But when you sit down to estimate the next thing, the same process runs again. Knowing about the bias doesn't fix it — changing the inputs does.

This is the fix Kahneman actually recommends, and it's blunt in the best way. Instead of estimating from the inside of your plan ("here's what I need to do and how long each step will take"), you estimate from the outside ("how long did similar projects actually take for people who did them?").

The method: before you commit to a timeline, identify a reference class — a set of comparable past projects. If you're relaunching your newsletter, the reference class isn't "how long my outline says it'll take." It's "how long newsletter relaunches actually took for the last five creators I can think of who did it." If you can't find external data, use your own history. Look at the last three times you did something at this scale. Average them. That average is more accurate than your current estimate, almost certainly.

The uncomfortable part: your reference class will almost always be longer than your gut estimate. That's the point. (And if you want to understand why your brain also fills whatever extra time it finds — that's Parkinson's Law doing its thing. The two biases run together.)

How to use it today:

If Reference Class Forecasting fixes the estimate, Implementation Intentions fix the execution. The concept, developed by psychologist Peter Gollwitzer, is simple: instead of planning what you'll do, you plan when and where and what happens if — in advance, in writing.

Standard productivity advice says: "Block time for the task." Implementation Intentions go further: "When [situation X] occurs, I will do [behavior Y]." The research consistently shows that if-then planning dramatically increases follow-through compared to goal-setting alone. The plan survives interruptions because you've already decided what to do about them.

But Implementation Intentions alone still fail if you're working from a bad estimate. The buffer is what makes the schedule honest. You're not padding because you're slow — you're padding because reality is nonlinear and something will always eat 20 minutes you didn't plan for.

How to use it today:

The UK government promised 40 new hospitals by 2030. Boris Johnson made the pledge in 2019. The programme has since been reset and expanded to 46 schemes at an estimated cost of £60bn, with the final projects not expected to open until 2045–46. Hospitals that were supposed to be replaced by 2030 at the latest are now targeting 2032–33, with further delays still possible. The project manager, apparently, had never heard of the Planning Fallacy. (Neither had the government. Or the one before it.)

→ If this framework landed, the Playbook has the full system — including the deadline engineering chapter that covers both of these methods in one place.

The Planning Fallacy doesn't mean you're bad at planning. It means you're using your imagination instead of your history. The fix isn't willpower — it's better inputs and a calendar with some honest padding in it. 🐿️

Stay MOTIVATED,

Gio