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

You've heard the advice a hundred times: break big projects into smaller tasks. It's supposed to make things manageable. What nobody mentions is that it also makes you significantly worse at estimating how long the whole thing will take. This isn't a motivation problem. It's a math problem — and the brain is terrible at the math.

→ The Playbook's deadline engineering chapter covers the structural version of this system. If your carefully broken-down project plans keep falling apart anyway, that chapter is exactly where to start.

🧩📈 Breaking projects into subtasks inflates your confidence — not your accuracy

🔍💀 The Pre-Mortem makes you smarter about risk before you've committed to anything

⚓🧭 Dead Reckoning means you stop replanning and start correcting — in real time

🗓️🪤 The issue isn't that you planned wrong — it's that you planned like things go right

The Move: Write one sentence that starts with "This will fail because..."

The Evidence: Research by Gary Klein, published in the Harvard Business Review, found that prospective hindsight — imagining a future event has already happened — increases the ability to identify reasons for future outcomes by approximately 30%. The pre-mortem works because it bypasses the social pressure to be optimistic about a plan you already committed to.

Start Here: Before you finalize the timeline on your next project, spend 3 minutes writing out the most likely failure scenario. Not the catastrophic one — the boring, Tuesday-afternoon one where a meeting ran long and you never caught back up. That's the one that actually happens.

Agents are desperate for ephemeral databases.

They spin up projects, fork environments, test ideas, and tear them down. Over and over. But every database on the market was designed for humans who provision once and stick around. Agents don't work that way.

Ghost is a database built for agents. Unlimited databases, unlimited forks, 1 TB of storage, and 100 compute hours per month. All free. Try it here.

Install the ghost MCP

Here's something that doesn't get talked about enough: the act of breaking a project into subtasks makes you feel more prepared without making your estimates more accurate. Psychologists call this the Unpacking Effect — the more granularly you decompose a task, the more total time you estimate it'll take in aggregate, but the more confident you also become in that estimate. Both things are happening at once. You feel like you've accounted for everything, which makes the eventual miss feel even more disorienting.

The mechanism is straightforward. When you look at a project as a whole, your brain runs a quick narrative check: "How long does something like this take?" It's vague, but it's calibrated by experience. When you break it into 12 subtasks, your brain evaluates each one individually — and each one looks manageable in isolation. The interactions between tasks, the transition costs, the things you haven't thought of yet — none of that shows up in the decomposed view. You've made the plan look like a spreadsheet when reality is going to come at you like a group chat.

The Unpacking Effect is one of a whole family of cognitive biases quietly running in the background every time you sit down to plan. None of this means don't break projects down. It means don't trust the confidence the breakdown produces.

Gary Klein developed this in the 1990s as a way to get people to say the quiet parts out loud before a project launched rather than after. The setup is deliberately uncomfortable: before you finalize your plan, you imagine it's six weeks from now, the project is finished, and it went badly. Not catastrophically — just the realistic kind of bad. Missed deadline, scope blew up, one key thing got dropped. Now you work backward: why did that happen?

The reason this works when standard risk assessment doesn't is that it bypasses the social dynamics of the planning room. Nobody wants to be the person who says "I think this is going to fail" in front of the team that just spent two weeks building the plan. The pre-mortem gives everyone permission to voice the concern because the failure is already hypothetically confirmed. You're not doubting the plan — you're forensically analyzing the wreckage.

For solo work it's even simpler, because the only social dynamics are between you and your own optimism. Which, frankly, is the harder conversation.

How to use it today:

Before GPS, ships navigated by dead reckoning: you know your starting point, your speed, and your heading. You don't know exactly where you'll end up, but you track your deviation from the expected course in real time and correct continuously. The goal isn't to predict the future perfectly — it's to know, at any given moment, how far off you are and which direction to adjust.

Applied to project planning, this is a shift in orientation that most productivity advice skips entirely. Standard planning is destination-focused: here's the finish line, here's the path, here's the schedule. When something goes wrong, the instinct is to replan — rebuild the schedule from the new position. That instinct is expensive. Every replanning session costs time and cognitive overhead, and it resets your confidence to a new (still optimistic) baseline.

Dead reckoning doesn't replan — it corrects. And it pairs well with what we covered last time on Reference Class Forecasting: a good outside-view estimate gives you an honest starting position; dead reckoning keeps you honest as you move through it. The companion problem — where whatever slack you find in the schedule just gets filled back up — is Parkinson's Law doing its thing. Worth keeping both in mind.

How to use it today:

The Sydney Opera House was projected to cost $7 million AUD and open in 1963. It opened in 1973 at a final cost of $102 million. The architect, Jørn Utzon, quit mid-project. The original estimate had no contingency for the fact that the shell roof design had never been built before — anywhere — at that scale. The planning was meticulous. The Unpacking Effect did its work. Nobody pre-mortem'd a building that had never existed. They just assumed the subtasks would add up.

→ The Playbook's deadline engineering chapter builds on both of these methods — pre-mortem included. If this issue clicked, that chapter is where the system lives.

The breakdown felt like progress. It just wasn't the kind that shows up in the finished work. Plan like things go wrong — because they already have, somewhere in the future. You just haven't seen it yet.

Stay MOTIVATED,

Gio