How to Plan a Realistic Day Instead of a Wish List

A realistic day is one where the minutes you have committed are fewer than the minutes you actually have. That is the whole test, and it takes two numbers: how much task time today contains, and how long your list will take. Most planning advice gives you neither. It tells you to put your fixed commitments on the calendar first, pick your top three, and protect your focus time, and then it stops before anyone does any arithmetic.

So start with the number almost nobody calculates.

Your day does not contain eight hours of task time

Take the hours you are actually at work. Subtract meetings. Then subtract the part of the day that is real work but is not a task on your list. Email, messages, the person who comes to your desk, the five minutes of nothing between finishing one thing and starting the next.

What is left is your task capacity, and for most people it is startlingly small. A nine-hour day with two hours of meetings is not seven hours of task time. Once you take out communication and transitions, three to four hours is a normal honest answer for a desk job with a meeting load. If that sounds low, the test is simple: think of a recent day you would describe as productive, and add up the hours of listed work you actually finished.

This number is personal and worth measuring rather than guessing. For a week, write down what you planned and what you finished. The gap is your real daily capacity, and it is more useful than any figure in an article, including this one.

It also answers the question people usually ask first, which is how many tasks you should plan per day. There is no general answer, because a day is not a count of tasks, it is a quantity of minutes. Five ten-minute tasks and five ninety-minute tasks are both "five tasks" and only one of those days is possible.

Two things change that number and most plans ignore both. Meetings consume task capacity rather than sitting beside it: a day with four hours of meetings has roughly half the task capacity of a day with none, and deserves half the work. And a day you are also commuting, collecting a child or travelling is a shorter day, not the same day with inconvenience attached.

Your estimates are low, and knowing by how much does not fix it

Having a capacity number only helps if you can put numbers on tasks. You can, and they will be wrong in a predictable direction.

In 1994 Roger Buehler, Dale Griffin and Michael Ross published a set of studies on what they named the planning fallacy in the Journal of Personality and Social Psychology. The best-known experiment followed 37 psychology students finishing their honours theses. Their average estimate was 33.9 days. They took 55.5 days. Only about 30 per cent finished by the date they themselves had predicted.

The detail that matters most for planning is what happened when the researchers asked the same students for a worst case. The average worst-case estimate was 48.6 days, and the actual average was still about a week beyond it. Being asked to imagine things going badly moved the number, and not far enough.

This is why the standard advice to pad your estimates does not work as well as it sounds. Look at what is actually in circulation: add twenty per cent, double everything, never schedule past eighty per cent of your available time, use sixty to seventy per cent of open time. Those are four different rules, none of them with a published derivation, and the research above suggests the problem is not the size of the multiplier. Asking people to be pessimistic did not make them accurate.

So how do you estimate how long a task will take, if being careful does not make you accurate? Treat estimates as relative rather than absolute. You do not need to know that a task takes 47 minutes. You need to know that it is a 45-minute task and not a two-hour one, because that distinction is what tells you whether your day fits. Estimate quickly, in fifteen-minute steps, and expect the total to run over. Then plan to a total below your capacity so the overrun has somewhere to go, which is a single buffer at the end of the day rather than a tax on every task. A buffer per task disappears into the tasks. A buffer at the end is visible, and you can watch yourself spend it.

A worked example: planning a real Wednesday

Here is a Wednesday, planned properly. Eight hours at a desk, 90 minutes of meetings.

Step one: the capacity

Five hours.

Step two: the list

Estimated fast and roughly, in fifteen-minute steps:

That is 385 minutes against 300. It is over by 85, which is 28 per cent, which is exactly the kind of margin that feels survivable in the morning and is not.

Step three: the subtraction

The question is not what matters most. It is what is not happening today.

The onboarding doc goes. The new hire starts in nine days, so it has somewhere else to live, and at 90 minutes it is the single biggest thing that is not time-sensitive. That leaves 295 against 300: technically fitting, and therefore still too full, because the estimates are low.

So something else gives. The roadmap page at 45 minutes is the next candidate, and cutting it leaves 250 against 300, with 50 minutes of slack. That is a day with room in it.

Notice the order of those two decisions. Neither was made on importance. The onboarding doc is arguably the most important item on the list for the business, and it still came off, because it has nine days of runway and nothing else did. Importance decides what you do first. Deadlines decide what can wait. Those are different questions and planning advice routinely conflates them.

One more detail from that list. The invoice chase is ten minutes and stays in every version, because at ten minutes it never competes with anything. Small items with a real consequence should be done rather than ranked, and a list that makes you deliberate over a ten-minute task is costing you more in deliberation than in work.

When the subtraction will not close

Sometimes you cut everything optional and the day still does not fit. That is not a planning failure, it is information, and it means one of three things.

The commitments are genuinely impossible, in which case the useful action is a conversation rather than a better plan. "I have 300 minutes today and 385 minutes of work, so one of these four things moves to Friday. Which one?" is a specific question with a specific answer, and it lands very differently from saying you are busy.

Or a task on the list is a project pretending to be a task. "Finish the pricing deck" at 120 minutes might really be four hours and three decisions you have not made yet. Items like that are the most common reason a careful plan collapses, and the test is whether you can name the first action. If the first action is "work out what this needs", that is the task, and it is twenty minutes, not two hours.

Or you are planning the day you wish you had. The honest version of capacity is lower than the flattering version, and the flattering version is the one that has your day failing by four in the afternoon.

This is also the real difference between time blocking and a to-do list, and it is not the one people usually describe. A to-do list has no denominator, so it will accept anything. Blocking time forces the comparison, because a block you cannot fit in the day is visibly a block you cannot fit in the day. You do not need a calendar grid to get that benefit, though. You need the total.

Why your tasks keep rolling over to tomorrow

The most useful signal in planning is not whether you finished today. It is what happens to the things you did not finish.

If the same item moves forward for five days, it is not waiting for time. It is waiting for a decision, or it is too big, or it is not actually something you intend to do. A plan that quietly carries work forward without anybody choosing is how a list becomes unmanageable, which is a slower version of the same problem as a day that does not fit.

So look at the rollover deliberately. For each item that did not get done, pick one of four. It goes on tomorrow with a real slot. It goes on a specific later day. It goes back to the backlog. Or it is not happening, and comes off the list.

Four options, chosen on purpose, once a day. That single habit does more for a to-do list than any sorting system.

Doing the arithmetic without doing the arithmetic

Everything above works on paper, and the reason I built Todonado around it is that the arithmetic is the first thing to be abandoned. It takes five minutes every morning, it is dull, and it is most tempting to skip on exactly the days when the day does not fit.

So the sum is built in. Tasks carry effort estimates in minutes. The Today view totals what you have scheduled and compares it against the capacity you set, and shows you the overcommitment before the day starts instead of after it has failed. Calendar events you import come out of the same total, so a morning of meetings reduces the afternoon's task capacity without you subtracting anything. Unfinished work comes back as a decision with those four options rather than silently reappearing. If the day will not close, Week planning spreads the overflow across the next seven days against each day's own capacity, so moving something to Thursday means checking that Thursday has room.

Two limits worth stating. It will not estimate for you, and your estimates will be optimistic for the reasons above, so the totals drift even when the comparisons are sound. And the capacity meter is a mirror: it will tell you clearly that the day does not fit, and it will let you commit to it anyway.

The short version

Find out how many minutes of task time your day really contains, which is probably three to four hours rather than eight. Put rough numbers on your list. Compare the two. Decide what is not happening today on the basis of what can wait rather than what matters most, and leave the overrun a visible buffer at the end instead of padding every task. Then look at what rolled over and choose, item by item, rather than letting it accumulate.

A wish list and a plan look identical on paper. The only difference is that one of them has been compared against the number of minutes in the day.

If your list is already far past the point where this works, the problem is not today's plan: organizing a huge to-do list is the step before this one. If the feeling is more paralysis than overcommitment, getting started when you have too much to do deals with that directly. If the subtraction keeps refusing to close because every remaining item has someone waiting on it, prioritising when everything feels urgent is the harder version of the same decision. And if the hours themselves are not yours, because a job owns the middle of the day, the arithmetic changes shape: planning around a 9-to-5 starts from what is left at the edges.