The Case for Doing One Thing at a Time

The end of a busy day, and the evidence is still on the screen. A report open at paragraph three. An email begun before lunch and abandoned mid-sentence. A spreadsheet with a column half filled, next to a form you meant to submit hours ago. Four tasks, all of them touched, none of them finished. Nobody could accuse the day of being idle. It simply has nothing to show for itself.

Days like this are common enough that they can start to seem like the natural shape of work. They are not. They are the shape of a particular habit, the habit of keeping several things open at once and moving between them whenever one becomes difficult or dull. The habit feels efficient while it is happening, which is what protects it. So rather than argue against it in the abstract, consider an experiment you can run. For one week, do one thing at a time, genuinely, and watch what changes.

What the experiment asks of you

The rule sounds simple and needs defining, because the loose version proves nothing. Doing one thing at a time means the task in front of you is the only one open. One document, one screen, nothing else waiting in a visible tab. It means that when a new task occurs to you mid-task, and it will, you write it down on a piece of paper beside you and return to what you were doing. It means you leave a task in one of two ways only: finished, or deliberately parked with a one-line note about where you stopped and what comes next. Drifting away from a task without noticing does not count as parking.

The experiment does not ask for heroic stretches of concentration. A task can be small. Answering one email is one thing; answering email while a document loads in another window is two. The unit does not matter. The discipline of sequence does. Nor does the week require a quiet job or a cleared calendar. Meetings and interruptions from other people still happen, and still get handled. The experiment only governs what you control, which is what happens in the moments when nobody is forcing a switch and you switch anyway.

A few kinds of work resist the frame, and it is better to decide about them in advance than to improvise mid-morning. If your role requires you to be reachable, give the channel its own turns: a pass through messages becomes one task, taken up and finished like any other, rather than a presence humming underneath everything else. The point is a modest one. Almost any job contains more room for sequence than it first appears to, and the experiment only needs that room, not a silent week.

That last clause about voluntary switches is where the week does its work, because they are far more frequent than they feel.

The uncomfortable first days

The first day or two usually feel worse, and it helps to expect this. A single open task offers no exit. When the paragraph will not come together or the numbers refuse to reconcile, the accustomed relief of glancing at something else is gone, and what remains is the task and your own restlessness. That restlessness is worth observing rather than obeying. It arrives with remarkable speed, often within a few minutes of starting, and it always has a plausible errand attached: a message worth checking, a small chore that would take only a moment. The errand is rarely the point. The exit is the point.

There is also the sensation of slowness. Working in sequence feels slower than working in parallel, the way a single queue feels slower than four, even when it moves faster. Part of this is the loss of the busyness signal. Four open tasks produce constant motion, and motion reads as progress even when it is only circulation. One open task produces long stretches where nothing appears to happen except the work itself quietly getting done. By the second day the paper beside you starts filling with the tasks you would otherwise have jumped to, and the length of that list is its own small revelation. Each line on it is a switch that did not happen.

Nothing more dramatic than this occurs early in the week. Mostly the first days show you the shape and size of the habit, which is something the habit itself never lets you see.

What changes by midweek

Somewhere around the third day, finishing starts. This sounds trivial and is anything but. Tasks that had been open for a week close in a morning, mostly because they were never large, only endlessly interrupted. A day now produces a short list of completed things rather than a wide smear of progress, and the difference in how the evening feels is considerable. An ending is a specific satisfaction that partial progress cannot supply, however much of it accumulates.

Four half-finished tasks weigh more at the end of a day than three finished ones and one not yet begun.

The texture of the work changes too. Every switch between tasks carries a cost that is easy to ignore because it is paid in small denominations: the few minutes of rereading, the reconstruction of where you were, the trace of the last task clinging to your attention while you work on the next. Paid dozens of times a day, those minutes amount to a serious tax, and by midweek you are simply not paying it. Sessions have runway. The deep middle stretch of a task, the part that used to be perpetually postponed by switching, actually gets reached.

Mistakes thin out as well. The small errors that divided attention produces, the figure copied into the wrong row or the reply sent to the wrong thread, come mostly from working on one thing while holding another in mind, and a week of sequence quietly removes their cause.

Parking, meanwhile, turns out to be a skill that improves quickly. The one-line note at a stopping point, which felt like ceremony on the first day, starts earning its keep every time you return to a parked task and resume in seconds instead of minutes. Even interruptions from other people sting less, because a forced pause lands differently on a person with one thread to save than on a person with four.

What the week leaves behind

The experiment’s last discovery is about the list rather than the work. A week of writing down every task that tried to interrupt leaves you with an unusually honest document. Some entries got done in their turn. Others were captured, never acted on, and by the weekend are plainly not worth doing at all. They were never tasks. They were exits wearing the costume of tasks, and a switch would have dignified each one with twenty minutes of attention it did not deserve. If your list of obligations has been feeling heavier than your actual obligations are, this is one quiet way a list becomes unmanageable: it fills with things that were only ever escapes.

What should you carry forward when the week ends? Probably not the pure rule. Held strictly and forever, it would become a burden of its own, and there are stretches of legitimately reactive work where sequence is a luxury. What survives is calibration. You now know what a voluntary switch feels like from the inside, the restless moment just before it happens, and recognizing that moment is most of resisting it. You know the difference between parking a task and abandoning it. You know that the feeling of slowness was mostly the absence of noise. One clean week is enough to reset your sense of what a working day can produce, and that sense, once reset, is hard to argue back down.

The question the week answers is not whether you can concentrate. It is how much of the scattered feeling was circumstance and how much was choice. The answer tends to be uncomfortable, and usefully so, because choices can be changed.

One small step: Tomorrow morning, run the experiment on a single task. Open only that task, keep a scrap of paper beside you, and write down every urge to switch instead of following it. When the task is finished, count the lines on the paper.