The switching tax

Multitasking feels like speed because motion is visible. The hidden cost is re-entry: each switch forces your brain to rebuild context, reopen files, and remember where the thinking stopped. Over a day, those taxes erase more progress than they create.

Single-tasking is not a personality preference. It is a way to reduce switching costs at the execution layer while still allowing a long backlog for planning.

The list design

Put one line at the top of your notebook or digital note: Current task. Beneath it, keep a waiting list. Nothing on the waiting list moves up until the current task is finished or deliberately paused.

Every current task needs a finish definition. “Extract three interview insights into a summary” can end. “Do research” almost never ends. Ambiguous tasks invite quiet multitasking because you never know when you are allowed to stop.

How to run it during a normal day

Start by choosing the current task from your weekly mainline when possible. Work it until the finish definition is met or the deep work block ends.

If a new request arrives, do not silently replace the current line. Ask whether the new item displaces the current task. If yes, pause the current task with a half-sentence handoff note. If no, place the new item on the waiting list.

This single social question—does this replace current?—prevents a large share of accidental thrash.

Handoff notes when interrupted

Before leaving a task, write a half-sentence of state: “Finished competitor table; still need pricing column.” When you return, start from that sentence instead of rereading the whole document.

Handoff notes are especially valuable between meetings. They convert a fragmented calendar into recoverable progress.

Single-tasking in collaborative jobs

Support, operations, and leadership roles cannot ignore parallel channels all day. Apply single-tasking inside protected blocks rather than as an absolute lifestyle rule.

A realistic pattern is: morning deep block on one current task, midday responsive window, afternoon second current task. The method survives contact with reality when you stop demanding purity.

Tools without tool obsession

Paper works. A single sticky note works. Any notes app works. Avoid building a complex task database before the behavior is stable. Complexity is often procrastination wearing a productivity costume.

Failure modes

Keeping three “current” tasks. That is multitasking with better stationery.

Using the waiting list as a guilt museum. Review it in the weekly review and delete stale items.

Changing the current task every time a message arrives. Messages need an intake policy, not veto power over every minute.

Single-tasking versus prioritization frameworks

Prioritization frameworks help you rank a backlog. Single-tasking governs what your hands do in the next hour. You need both, but confusing them creates elaborate lists with no execution discipline.

Use the weekly review to choose the mainline. Use the single-task line to execute. When someone asks you to “quickly juggle,” translate the request into a replacement decision.

If everything is labeled P1, you do not have priorities. Force a temporary order even when stakeholders dislike it.

Digital implementation details

In a notes app, pin the current task at the top and keep the waiting list below a horizontal rule. In a kanban, allow only one card in the Doing column. In a paper notebook, rewrite the current line at the start of each session so it stays visible.

Avoid linking the current task to five dashboards. One visible line beats a perfect system you must click around to interpret.

At the end of the day, either finish the current task or write a handoff note before shutdown. Do not leave a ghost current task that means nothing tomorrow.

FAQ

What about creative branching? Explore inside the current task’s finish definition. Branching into a new project requires an explicit replacement.

How do I handle email triage? Batch it in a responsive window as the current task, with a time box and a clear stop time.

Is single-tasking slow? It often feels slower hour-by-hour and faster week-by-week because finished work compounds.

Case study: shipping a doc without thrash

A product manager needed a strategy memo by Friday. Instead of juggling memo, Slack, and analytics tabs, she set the current line to “Write memo sections 1–2 to draft quality” each morning block. Waiting-list items included dashboard checks and vendor emails.

When a director asked for a “quick competitive look,” she asked whether it replaced the memo sections. It did not; it went to the waiting list for Thursday’s responsive window. The memo shipped Thursday afternoon with fewer mid-document stalls.

The behavioral change was social as much as personal: replacement questions made priority conflicts visible instead of silently shredding the current task.

Checklist

Next step

Rewrite today’s work around one current task with a finish definition. Keep everything else below that line. Practice for three days before adding any new productivity tool. More focus guides are in the article list.