The short answer

You are not bad at planning because you are disorganised. You are bad at planning in a specific, predictable, well documented way: you systematically underestimate how long your own tasks will take, while remaining perfectly capable of estimating other people's accurately.

Buehler, Griffin and Ross demonstrated this across a series of studies in the Journal of Personality and Social Psychology. In one, students predicting when they would finish their thesis gave an average estimate that landed well short of reality. Their worst case estimates, the ones given under instruction to imagine everything going wrong, were still optimistic compared to what actually happened.

The most striking part: people can accurately recall their history of running late, and it does not change their next prediction.

Why knowing your own history does not help

This is the core puzzle the research resolves. If you have missed the last ten deadlines, why does the eleventh estimate not adjust?

The answer is about which information you use when predicting.

When you estimate a task, you build a narrative of the future: a plan-based scenario in which you sit down, work through the steps, and finish. That scenario is coherent, specific and plausible. It is also constructed from the steps of the task, and it silently assumes no interruptions, no scope discovery, no waiting on other people and no bad days.

Your track record is distributional information: the base rate of how tasks like this have actually gone. It is available in memory but it is not the input you reach for while constructing the forecast. It sits in a different mental drawer.

Observers do better precisely because they lack the inside view. Without access to your detailed plan, they fall back on base rates, and base rates are more accurate.

What the research does not say

It is not simple overconfidence. People are not uniformly optimistic about everything. The effect is specific to predictions about their own future task completion. Predictions about others show the bias much less, or reverse it.

It is not solved by pessimism. Being told to imagine the worst case narrowed the gap but did not close it. Worst case scenarios are still constructed inside the same plan-based frame.

It is not a character flaw. It is a feature of how forecasting works when the inside view dominates. It shows up in individuals, in teams and in national infrastructure projects.

What actually reduces the error

Does not work well	Works better
Trying harder to be realistic	Looking up how long the last three similar tasks actually took
Imagining what could go wrong	Using the recorded distribution of your past completion times
Adding a generic buffer to the estimate	Estimating from the outside, as if predicting for someone else
Breaking the task into steps and summing	Noting that step-summing usually makes the estimate worse, not better

Three operational rules:

Prefer recorded base rates to remembered ones. The bias is not that you lack the data. It is that you do not retrieve it while forecasting. Data that is written down and placed in front of you at the moment of estimation is data you will actually use.
Estimate as an observer. Ask what would happen if a competent colleague with your workload took this on. That framing pulls you toward the outside view.
Plan capacity, not just tasks. A list of tasks with no total duration attached cannot be wrong, which is why it is always wrong. Compare the sum of estimated durations against the hours you actually have.

Why UpTicker asks for your wake time and available hours

A day plan that ignores capacity is not a plan. It is a wish list with checkboxes.

This is the practical reason UpTicker needs time inputs during setup: when you wake, when your protected work block sits, and how many hours you actually have. Without those, any generated plan is being assembled against an unbounded day, and an unbounded day is exactly the condition under which the planning fallacy produces its largest errors. You will accept a plan that requires eleven hours because nothing in the interface says the day has seven.

Two design consequences.

The plan is bounded by capacity, not by ambition. Tasks are ranked and fitted against the hours available, so the overflow is visible as overflow rather than being silently absorbed and then discovered at 6pm.

Completion history is retained and surfaced. Your recorded pattern of what actually got done is the outside view. The whole finding is that the base rate exists but is not retrieved at the moment of forecasting. A system that holds that history and puts it in front of you when the day is being planned is doing the one thing the research says fixes the error.

Frequently asked questions

What is the planning fallacy? The tendency to underestimate how long your own tasks will take, even when you know similar tasks have taken longer in the past. Buehler, Griffin and Ross (1994) documented it experimentally.

Why does my past experience not correct my estimates? Because forecasting draws on a constructed narrative of how the task will go, rather than on the distribution of how similar tasks actually went. The historical information is available but not retrieved during prediction.

Does adding a buffer fix it? Poorly. Buffers are applied to an estimate that is already anchored too low, and they tend to be sized by the same optimistic process.

Why am I better at estimating other people's timelines? You lack access to their detailed plan, so you fall back on base rates. That outside view is more accurate than the inside view you use on yourself.

What is the single most effective fix? Reference class forecasting: find how long comparable tasks actually took, and start from that number rather than from your constructed scenario.

Reference

Buehler, R., Griffin, D., and Ross, M. (1994). Exploring the "planning fallacy": Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366 to 381.

The Planning Fallacy: Why Your Day Plan Is Always Wrong