Single-tasking at work: does one thing at a time actually suit you?

Is single-tasking really better than multitasking at work?

Better for some people, in some jobs, and far less of a discipline question than the advice around it suggests. Howard and Cogswell pulled the research together in Organizational Psychology Review in a meta-analysis of polychronicity, the trait-like preference for dealing with several activities at the same time. Their framing is person-environment fit. What the preference costs you or earns you depends on the work you bring it to, not on the preference alone.

One finding in that paper explains why you have probably read flatly contradictory things about multitasking. Studies in this area have not all been measuring the same behaviour. Doing two things in the same moment, dual-tasking, is a different act from leaving one task for another and coming back to it, task-switching. Howard and Cogswell show that the difference changes what the numbers say, which means a headline about multitasking can be true of one and false of the other.

Their claim about job performance is worth reading exactly as they wrote it. The association between polychronicity and job performance appears to have strengthened over the years the studies span, and they suggest the growing complexity of businesses as the reason. That is a proposed explanation, not a measured cause, and they word it as one. Read loosely it says preferring to juggle now pays at work. Read as written it says the fit between this preference and the work has moved over time, and names a plausible reason why.

So it is a fit question.

That leaves you something more answerable than whether single-tasking is better. If a half-done task nags at you until you close it, one thing at a time is likely the cheaper way for you to work, and the methods on the focus pillar are built for that. If you sit comfortably across three open threads and lose nothing coming back to any of them, a rule forcing one at a time takes something away and hands you little back. Neither is the better kind of worker. They fit different jobs.

How do you tell whether single-tasking suits you?

Start with the days you already have, because one study measured this exact situation. Pachler and colleagues ran a diary study with knowledge workers, published in the Journal of Occupational Health Psychology: 149 people reporting across five consecutive working days, 644 daily observations in all. On days carrying a lot of workflow interruptions, people were less satisfied with their own performance and more emotionally exhausted that same day.

Then the trait came in, and it did only half of what you would expect. Among people who scored high on polychronicity, the link between a heavily interrupted day and dissatisfaction with their own performance dissolved. The exhaustion did not. Polychronicity failed to moderate that side of it at all, and that is the half most summaries of this study drop.

It buffers the judgement, not the cost.

So the protection is narrower than it sounds. Preferring to work across several things protects how the day feels about your output. It does not protect you from the tiredness a fragmented day produces. The colleague who thrives on a chopped-up schedule is not immune to it, and neither are you if that description fits.

The version you can run at your desk takes two weeks and one line in a notebook. This part is site practice rather than a research protocol. At the end of each day, write down how many times you left a task before it was finished, then rate two things out of five: how satisfied you are with what you got done, and how drained you feel. The interruption-heavy days will separate themselves out.

What you are reading for is which of the two ratings moves with the interruptions. If satisfaction tracks them and the drain score sits flat, the fragmenting is costing you work you would rather have done, and a stricter rule about whole tasks is worth the trouble. If satisfaction holds steady while the drain climbs, protecting whole tasks will not fix what is tiring you. Fewer arrivals will.

What do you do with everything that arrives while you single-task?

The arrivals are the real obstacle here, not your willpower. A single-tasking rule breaks at the moment something lands that outranks the thing in front of you, and most working hours contain one or two of those. A firmer rule does not help. Somewhere for the arrival to go that you trust enough to stop carrying it does.

The Ivy Lee Method is the plainest version that already assumes this. You write down six tasks the night before, in priority order, and work them one at a time until each is finished. What makes it a single-tasking method is not the six. It is the ranking, decided while you were calm, so a new arrival has to beat a decision you already made instead of winning simply by being the newest thing on your screen.

Task Batching covers the smaller class: the messages and two-minute requests that cost nothing individually and eat an afternoon collectively. You group them and clear them in one pass at a fixed point in the day. They still arrive at the same rate. They stop landing in the middle of the work, which is where their real price sits.

Both charge you something real, and they charge it in response time. A request that would have got an answer in four minutes now waits for your next pass, and some roles cannot carry that delay. Name the one channel that stays live, tell the two or three people who use it, and let the rest wait for the pass. A single-tasking rule nobody around you knows about is one you will keep breaking on their behalf.

Write it down, then decide at the next boundary.

How does your working style change the answer?

Neither study sorted its participants by working style, so treat the rest of this section as a reading rather than evidence.

Four working styles run through this site: Architect, Sprinter, Visionary and Improviser. Each meets a single-tasking rule at a different weak point, and where it breaks first decides which version of the rule is worth adopting.

An Architect mostly has this in place already, and the leak is at the edges. The rule survives the day you planned and fails on the request you did not. Give arrivals one fixed destination and one fixed time you deal with them, and the rule stops needing a decision at every interruption.

What costs a Sprinter is leaving mid-burst rather than moving between tasks at all. Set the block by the burst rather than by the task, and let the whole arrival pile wait for the gap after it. One task per burst, and whatever is left over at the end is the next burst.

The Visionary often scores high on the preference this article is about, and frequently for a sound reason: several threads open at once is where the connections between them turn up. A rule forcing one at a time can take that away. That is a real loss. Keep the threads and put the limit somewhere else, on how many of them are live in a single day rather than on how many exist.

An Improviser never had room for a strict rule. One protected task a day is different. Pick the one you would be embarrassed to leave unfinished, give it the hour before the requests start, and single-task that one only.

One change this week, then. Keep the two ratings from the section above for ten working days and watch which one moves with the interruptions. That tells you whether you are about to fix the wrong thing, and it costs you a minute a day. If you are not sure which of these four is yours, the working style assessment takes a few minutes.

Frequently asked questions

Sources

• Howard & Cogswell (2023), Organizational Psychology Review: A meta-analysis of polychronicity: Applying modern perspectives of multitasking and person-environment fit
• Pachler et al. (2018), Journal of Occupational Health Psychology: Workflow interruptions and employee work outcomes: The moderating role of polychronicity