How to plan a workday in pomodoros

To plan a workday in pomodoros, count how many sessions the day genuinely holds — far fewer than the arithmetic suggests — give each one a named task, and leave gaps on purpose. The whole value of the exercise is in the honest counting. A plan built on the day you wish you had is just a list of disappointments with timestamps.

The arithmetic is humbling

An eight-hour day divided by half-hour rounds gives sixteen pomodoros. Nobody gets sixteen. Subtract meetings, lunch, messages, the colleague with a quick question, the tea, the walk to the printer, and the plain fact that attention is a muscle rather than a motor, and a genuinely good day at a desk holds perhaps eight to ten sessions. A normal day holds fewer. A day with three meetings in it might hold four.

This is not a confession of laziness; it is what a day is actually made of. The reason it feels shocking is that most of us have never counted. We plan in hours, hours are elastic in the imagination, and so every morning’s plan quietly assumes a day that has never once occurred.

The first time you count honestly, two things happen. The day’s plan shrinks, and the plan starts coming true. Of the two, the second matters more.

Plan by sessions, not hours

An hour is a container of unknown contents — an hour of blended attention, interruptions and drift is not comparable to an hour of focused work, yet a plan written in hours treats them as equal. A session is a fairer unit, because a session has a definition: one named task, one interval, attempted properly.

So the plan for a day stops being “morning: report; afternoon: emails and project work” and becomes something like: two sessions on the report’s summary section, one on the awkward email you have been circling for days, one for the shallow batch — messages, approvals, expenses — and one held in reserve for whatever the day throws. Five named blocks. It looks meagre next to the old imaginary plan. It has the advantage of being achievable.

Naming the tasks the evening before or first thing in the morning takes a few minutes and repays them immediately, because the worst moment to decide what to work on is the moment you sit down able to work.

Leave slack, and mean it

A plan that fills every countable session is a plan with no shock absorbers, and days deliver shocks on schedule. Something urgent will land. A session will collapse. A meeting will breed another meeting.

Leaving one or two sessions unassigned is not padding; it is the difference between a plan that survives contact with a Tuesday and one that dies by ten thirty. If the slack goes unused — it won’t, but if — you simply pull the next task forward and finish ahead. Nothing about slack requires it to be wasted.

The same honesty applies to the gaps between sessions. Breaks are part of the plan, not leakage from it. A day planned as an unbroken row of blocks is the hour-fantasy again, wearing a tomato costume.

Office days count differently

If your calendar belongs partly to other people, plan around the fixed points rather than pretending they aren’t there. Meetings are the tent poles; sessions go in the spaces between. A forty-minute gap holds one. A two-hour stretch holds three with breaks. The office version of the technique is mostly this: finding the sessions the calendar left behind, and defending their edges.

It follows that different days have different honest capacities, and the plan should say so. A Monday of back-to-back calls is a two-session day, and planning it as a six-session day just manufactures an evening of feeling behind. Feeling behind a fictional schedule is the most avoidable misery in knowledge work.

Review with a mirror, not a scoreboard

The evening question is not “did I do enough?” — that question has no answer and never tires of being asked. The useful questions are smaller: how many sessions actually happened? Where in the day did they land? What killed the ones that died?

This is where a simple record earns its keep. PetPomo keeps a stats page that counts finished sessions and nothing else — no score, no streak to break, no red days. Looked at over a week or two, a pattern usually emerges: perhaps the mornings hold three reliable sessions and the afternoons rarely hold more than one, or Thursdays are always lighter than the plan admits. That is not failure data. That is the shape of your actual week, and what the numbers can and can’t tell you is worth understanding before you let them make you feel anything.

Then — and this is the part people skip — adjust the plan to fit the evidence rather than resolving to fit the evidence to the plan. If the data says five sessions is a good day, plan five. Planning eight and achieving five every single day is not ambition. It is choosing to end every day with a deficit.

A plan is a bet, not a promise

Held lightly, a day planned in pomodoros does something pleasant: it replaces the vague, infinite obligation of “get lots done” with a short list of specific, finishable things — and a finished list, even a short one, is a different feeling to a survived day. The cat asleep beside the timer doesn’t know whether you did five sessions or fifteen. It only notices that the sessions happened and the breaks came with company, which, as measures of a working day go, is more sensible than most.