Separate the planning session from the execution day
Do your planning in a dedicated session, never on the day you intend to start.
Why it works
Planning immediately before execution compresses deliberation under time pressure, which amplifies optimistic anchoring: you unconsciously plan for the ideal scenario because anything more conservative feels like giving up before you start. A separate planning session removes the emotional urgency, allows you to consult your reference class calmly, and lets the plan sit overnight — a form of incubation that often surfaces overlooked obstacles. This is also a form of "cool-state" decision-making: plans made in a neutral state are more realistic than those made in the motivated state of imminent action.
How to do it
- Designate a weekly planning session (e.g., Sunday evening) that is decoupled from any execution day.
- During that session, review last week’s actual vs. estimated times before building the new plan.
- Set next week’s schedule fully, then close the planner until execution begins.
- On execution days, run the plan; save replanning for the next planning session unless something genuinely breaks.
Evidence
Hot vs. cold state decision-making research (Loewenstein, 1996) shows that decisions made in a neutral state are more considered and less impulsive than those made in an affective state. Direct evidence for planning-session separation is mechanistic rather than trialed. (mechanistic)
The hot/cold distinction is robust; its application to time estimation specifically is plausible but extrapolated.
Sources
- Loewenstein (1996), Out of control: Visceral influences on behavior, Organizational Behavior and Human Decision Processes
Common mistake
Treating planning as a task to dispatch quickly before getting to the "real work" — fast planning is the source of most of the optimism bias.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for The Planning Fallacy — Why Your Estimates Are Always Wrong
- Reference class forecasting
Before estimating, look up how long similar past projects actually took — not how they felt.
- Run a premortem before committing
Imagine the project has already failed and work backwards to find why.
- Decompose tasks and sum the pieces
Estimate each sub-task independently, then add them up — the sum is closer to truth than a top-down estimate.
- Schedule buffers as first-class commitments
Add explicit slack time to your schedule and treat it as non-negotiable white space, not a reserve to fill.
- Set external accountability deadlines
Announce a completion date to someone who will notice if you miss it.
- Log actual vs. estimated time for every task
Build a personal database of your own estimation errors so you can calibrate future predictions.