What it costs to stop one thing and start another
The short version
- Moving between two tasks carries a real time cost. It shrinks when you can see the switch coming, and it does not go away entirely.
- A day cut into fragments is cheap for some kinds of work and very expensive for others. Which kind of day you get is usually decided by a timetable, not by you.
- Most of this cost is invisible because each individual switch is too small to notice. It only becomes visible when you count them.
You were at it all day and the honest total of work produced is a small fraction of that. Nothing went wrong. You went from the reading to a message to the seminar to the reading again, and each move seemed free at the time.
Why it does not feel like anything
When you stop one task and start another, what you had loaded for the first has to be put down and what you need for the second has to be picked up. That has been measured directly in the laboratory: switching between tasks carries a measurable time cost, the cost shrinks when you can see the switch coming and prepare for it, and it does not disappear even with full warning (Monsell, Trends in Cognitive Sciences, 2003).
The reason it does not register is arithmetic. One switch sits below the threshold of noticing. A day is made of dozens of them. You experience the aggregate — a day that produced very little — without experiencing any of the individual charges, so the explanation you reach for is about effort or character, because those are the only candidates visible from where you are standing.
Switching also feels like progress. Answering the message is a completed action, and moving between three pieces of coursework feels like working on all three.
The timetable is a design decision
Here is the part worth being clear about. Whether your day arrives whole or in fragments is mostly not your choice.
A course that puts three one-hour contacts on three separate mornings has consumed three working days to deliver three hours of teaching. A team that spreads five meetings evenly across a week has left nobody with a usable block. Both were decided by whoever found it easiest to fill the gaps in a shared calendar, and neither was thinking about what happens between the entries.
The same shortfall then gets explained two different ways depending on where it is located. Located in the person, it is a problem with concentration. Located in the schedule, it is a problem with the schedule — and schedules are things other people can change.
Where a fragmented day pays and where it costs
It pays when the work is genuinely made of separate small pieces, and when responsiveness is the point. A day of short blocks suits admin, replies, marking, coordination, anything where nothing has to be held between the pieces. It also suits work where the risk is going too far in the wrong direction, since frequent stops force you to look up and check. In some jobs that is not a side effect. It is the job.
It costs when the work has to be held whole. A dissertation chapter, a long proof, a piece of code with connected parts — these have a loading cost that must be paid every time you sit down, and a fragmented day charges it repeatedly for a single day's output. The waiting time between fragments is also unusable in practice: forty minutes before a lecture is not forty minutes of work, and the whole gap gets written off.
What preparation actually reduces
Preparation shrinks the cost, which is worth knowing precisely because it does not remove it.
The usable version is to make re-entry cheap rather than to make switching rare. Before you stop, write down not what you did but what you were about to do next. Leave the file open at the right place. Say where you are going next, so the switch is expected rather than sprung.
The rest is grouping. Two hours of the same kind of work, in any order, costs less than the same two hours interleaved with something else.
What the setting can do
Ask for teaching contacts, shifts or meetings to be clustered rather than spread. This costs the person building the timetable nothing and hands back whole days. Ask for one recurring block in the week with nothing scheduled in it — for a team, a no-meeting morning; for a course, a protected study block that nothing may be booked into.
Ask for an interruption norm. A group can agree that non-urgent questions are collected and asked once rather than arriving one at a time. The asker waits an hour. Everyone else keeps their morning.
Small things to try this week
- Count your switches for one day. Just a tally on paper. The number is usually the argument.
- Before you stop any task, write the next action on a sticky note and leave it on the keyboard.
- Group one category of work — all replies, all admin — into a single block, and see what the rest of the day does.
If nothing changes after a few weeks, that is useful information. It generally means the fragmentation is coming from the schedule rather than from your handling of it, and that is a conversation rather than a technique.
Written for Thought Club as general guidance, not medical advice. Free to read, print, and share.