It is 8 p.m. on a Tuesday. The paper is due Thursday at midnight. You tell your roommate, with the calm confidence of someone who has never been wrong about anything, "I'll knock this out in two hours." At 2:47 a.m. you are still typing, the thesis statement has changed three times, and you are eating dry cereal out of a coffee mug. Welcome to the planning fallacy.
The planning fallacy is the well-documented tendency to underestimate how long a task will take, even when we have done very similar tasks before and were similarly wrong about those. It was named by Daniel Kahneman and Amos Tversky and put to a now-classic test by Roger Buehler, Dale Griffin, and Michael Ross in 1994, using a population every undergraduate will recognize: college students staring down a big deadline.
What the research actually shows
Buehler, Griffin, and Ross followed 37 psychology honors students at the University of Waterloo as they worked on their senior theses. The students were asked when they realistically expected to finish, plus a best-case and worst-case estimate. On average they predicted 33.9 days. The actual average was 55.5 days — about 64% longer than the realistic estimate. Only about 30% of students finished by the date they had confidently picked for themselves. Even the average worst-case prediction (48.6 days) was still too optimistic.
That was not a fluke. Decades of follow-up studies across writing tasks, tax returns, and class projects have shown the same pattern. In one review of time-estimation research, a clear majority of participants underestimated how long their work would take. The bias is remarkably persistent: students will admit, in the abstract, that past assignments took longer than expected, and then turn around and produce a too-rosy estimate for the next one anyway.
Why our brains are like this
Kahneman called the underlying mistake the "inside view." When you sit down to plan a paper, your mind builds a clean, frictionless mental movie of the task itself: open the doc, write the intro, drop in three sources, done. What it does not pull up is the messy data of every other paper you have ever written — the dead-end paragraphs, the missing PDF behind a paywall, the citation manager that decides to log you out, the friend who texts you at the worst possible moment, the realization at hour two that the prompt is actually asking for something different.
The fix Kahneman proposed is the "outside view": instead of imagining this task in particular, look at a reference class of similar past tasks and ask how long those actually took. For students, that is roughly: "How long did my last three 5-page papers really take, start to finish, including all the staring at the wall?" That number, not the optimistic one, is your honest baseline.
Why this matters for college students specifically
A college schedule is a compounding system. One underestimated lab report cascades into a skipped reading, which becomes a half-prepared discussion section, which becomes a frantic catch-up before the midterm. Research on undergraduate time-management behavior consistently links accurate time estimation, planning, and short-range scheduling with higher GPAs and lower academic stress (Adams & Blair, 2019, in SAGE Open). Conversely, chronic underestimation drives the all-nighter → sleep loss → worse performance loop that hits hardest during midterms and finals weeks.
It also quietly damages confidence. When you repeatedly miss your own private deadlines, the story you start telling yourself is not "my time estimates were off" but "I'm lazy" or "I can't focus." That is a cognitive bias being mistaken for a personality flaw.
Four things that actually help
- Use the outside view. Before estimating a new assignment, pull up your last two or three similar ones and write down how long they really took. Use that as your starting number, not your gut.
- Write an implementation intention, not a vibe. Buehler and colleagues later showed that students who specified exactly when and where they would do an assignment ("On Wednesday at 4 p.m., at the second-floor library carrel, I will draft the introduction") were dramatically more likely to finish on time — jumping from about 14% in a control group to 41% on-time completion in one experiment. The if-then plan removes the moment of "wait, where do I even start?"
- Plan to the worst case, not the realistic one. Forecast best-case, realistic, and worst-case. Schedule the work to fit the worst case. You will rarely regret finishing early; you will frequently regret finishing at 4 a.m.
- Apply a multiplier. Software engineers have learned to multiply their gut estimates by 1.5–2×. Students can borrow the same trick. If your first instinct says two hours, block three. The math is humbling and the calendar will love you for it.
The point is not to become pessimistic about your own work. It is to plan for the student you actually are — the one with a job, three group chats, a 9 a.m. lecture, and a brain that gets bored — instead of the idealized one your imagination keeps drafting in. Your future self, at 11 p.m. on a Wednesday, will be deeply grateful.