Most jobs require several responsibilities. That does not mean every task benefits from rapid switching. The useful question is where a handoff or interruption breaks a line of reasoning.
Identify the expensive switch
Choose one task where resuming is difficult: checking a detailed contract, drafting an analysis or debugging a fault. Write down what must be held in mind when you stop. A simple resumption note can record the current version, next test and unresolved question. Routine work may be easy to batch; complex work often needs a protected interval. Do not assume the same schedule suits a receptionist and a researcher.
Batch what can wait
Separate work by required response time. Handle routine messages at predictable intervals, but keep a clearly marked urgent path for incidents or customers who genuinely need immediate help. Group similar short tasks when their context is shared, and avoid mixing a writing task with a stream of unrelated approvals. Ask whether a process can remove a request entirely by documenting a decision once.
Make handoffs resumable
Before changing tasks, leave a note for your future self or the next owner: goal, last completed step, location of the current file and the next concrete action. When you return, review the note before opening a fresh set of tabs. Measure errors and completion time after the change, not merely the number of tasks touched. More visible activity can coexist with slower, less accurate delivery.
Try it in a real workweek
An analyst has to interrupt a forecast for a customer issue. Before leaving, they save the model version and write “next: validate Q3 assumption against the signed price list.” The customer channel stays open; the resumption note prevents a second hour reconstructing the work.
In safety-critical or regulated tasks, follow established interruption and verification procedures. A personal productivity technique is no substitute for them.
Check the source and the context
For the next step, see this related field guide.