Why Your Morning Plan Falls Apart Before 10 a.m.
Why your morning to-do list outruns the day, even when you know past tasks ran late, and how buffers, fewer items and your own history fix it.

It is 8:30, your coffee is still warm, and the list for the morning looks reasonable: answer the messages that came in overnight, finish the slide deck, review two pull requests, read the chapter for Thursday's class. By 10:00 you are still on the messages, the deck is half done, and the rest of the list has quietly moved to "after lunch". You have watched this happen before. You planned this way anyway.
That gap between what you know and what you plan has a name.
The planning fallacy
Daniel Kahneman and Amos Tversky described the planning fallacy in 1979: a confident belief that your own project will go as planned, even while you know that most similar projects ran late. In their chapter on intuitive prediction (Kahneman and Tversky), they separate two kinds of information you can use when you forecast anything:
- Singular information: facts about this particular case. Your plan, your steps, the way you intend to tackle the deck.
- Distributional information: how similar cases turned out. How long decks like this one actually took you the last few times.
Both matter. The research below shows which one usually wins when you plan your own work.
What the research found
In 1994, Roger Buehler, Dale Griffin and Michael Ross tested the idea with students and their real work (Buehler, Griffin and Ross, 1994). In the first study, 37 psychology students at the University of Waterloo in Canada, in the final semester of their honours thesis, were asked when they would hand it in. On average they predicted 33.9 days. They actually took 55.5 days. Fewer than a third (29.7%) finished by their own best estimate.
The detail that stings: the students were also asked when they would finish "if everything went as poorly as it possibly could." Fewer than half (48.7%) made even that date.
The pattern held across the paper's other studies, with school assignments and everyday tasks: in each case, fewer than half of the participants finished in the time they predicted. In a classroom survey by the same authors, students said they had finished about two thirds of their previous projects later than they expected.
So the problem is not that people have never been late. They have, they remember it, and they still believe this time's estimate is realistic. The authors' own example is the academic who carries a full briefcase home every Friday, fully meaning to finish all of it, even though no earlier weekend ever got past the first one or two jobs.
Why knowing your history is not enough
The researchers asked students to think aloud while they made their predictions. People talked almost entirely about the future: the steps they would take, the plan for getting it done. Past experience barely came up.
When it did, it was explained away. Students described their past misses with reasons that were external, short-lived and specific: that week was unusual, that task was different. If every past delay was a special case, none of them seems to count for today.
Two results point at what helps. In one study, students who only recalled past assignments still predicted earlier finishes than students who were also asked to connect those past experiences to the assignment in front of them. In that second group, the optimistic bias disappeared. In another study, observers who predicted someone else's finishing time leaned on past experience more, and they overestimated instead of underestimating.
The paper also reviews earlier lab work in which people planned a series of errands. They typically overestimated how much they could get done in a given time, and kept doing so after repeated negative feedback. That is the morning list in a nutshell.
How to plan a morning that survives
None of this needs special tools. Try these this week:
- Start from your own past, then connect it. Before you write a time next to a task, ask: "The last two times I did something like this, how long did it really take?" Then ask what makes today's version the same as those. In the study, the connecting step changed predictions; remembering alone did not do as much.
- Pick fewer items. Choose the two or three things that must move this morning. Everything else goes on an "only if there is time" line. A shorter list is not lower ambition. It is a list you can actually finish.
- Leave a buffer on purpose. Do not fill every slot. For example, keep the last stretch before lunch empty. If the morning goes well, you pull the next item forward. If it does not, the overflow has somewhere to land.
- Ask someone outside your head. A teammate or study partner looking at your plan is more likely to spot the obstacles you skip. If their estimate is longer than yours, it is a good one to plan with.
- Write down the real time. At noon, note how long each task actually took. After a week you have your own distributional information, and the next plan starts from facts instead of hope.
Writing the shorter plan in Snipset
Once the list is short, writing it down should take seconds. In Snipset, open the Tasks & Todo Menu with its shortcut and type one line in the "Add a task…" field, such as Review PR tomorrow 10am #qa P2. Snipset picks out the date, the time, the priority and the tag, shows what it detected, and saves the task when you press Enter. Words like "tomorrow" and "next week" move the items you are not doing this morning to another day, and P1 to P4 sets the priority from "Priority 1: Urgent" to "Priority 4: Low" (a task with no P gets Priority 4). It recognises a small set of words like these, not any phrase you might type, so keep the line simple.
Keep Snipset in your Google results
Add snipset.belajarcarabelajar.com as a preferred source on Google. Snipset posts then show up more often when you search, with a preferred badge in AI Overviews.
Add Snipset on Google