Most time estimates quietly assume the task will happen in a smooth lane.
Then the real day shows up: setup friction, messages, low energy, missing files, and the task takes longer than the fantasy version did.
You keep estimating the clean version
The planning fallacy is normal, not rare
People usually imagine the work itself and forget the real-world drag around it. That is why the first estimate is often too small.
Small friction is what breaks the plan
Reality is rarely one clean assignment on one clean table.
It is the login that expired, the message you forgot to answer, and the task that needs one more pass before it can even start.
Quick check
Estimate check
Why are time estimates usually wrong?
Exactly. The estimate is usually for the fantasy version, not the real one.
Try this
Use the 1.5x rule on important estimates
If you think the task will take 40 minutes, block 60. If you think it needs two hours, consider three. Mechanical buffer beats repeated surprise.
Key idea
What to remember
Assume the first estimate is optimistic. Multiply it, leave slack, and stop planning against the fantasy version of the task.