Switching is more than lost minutes
Context switching is the work of unloading one mental model and loading another: files, goals, social role, urgency, even keyboard shortcuts. The visible interruption may be ten seconds. The rebuild is often ten to twenty minutes of low-quality half-attention before real progress resumes.
Remote work increases switches because channels multiply and nobody sees you already loaded.
Example 1: Developer mid-feature to pull request review
You hold a feature branch, failing test, and plan for the next commit. A review request arrives "quick look."
You read the diff, comment, return to your branch. You reopen files, rerun tests, forget which assertion you were fixing, reread your own notes. Forty minutes later you merge a comment thread and make one local change.
Cost: not the review time. The feature thread tax.
Cap reviews to a labeled window or batch at noon and four pm. See deep work for developers.
Example 2: Support ticket to architecture doc
Morning starts in incident tone: short replies, high vigilance. At 11:00 you open a design doc needing slow thinking.
Your brain stays in reply mode. You write bullet fragments, check chat between paragraphs, produce text that reads reactive. You switch back to tickets at lunch without finishing the section.
Cost: doc quality and double setup for both modes.
Schedule support windows explicitly. Put doc blocks where chat is closed.
Example 3: Writing proposal to Slack debate
You draft pricing for a client. A thread erupts on unrelated policy. You read twenty messages, form opinions, reply twice, return to the proposal.
The sentence you were building is gone. You restart the section and accidentally import argument tone from chat.
Cost: writing voice and an hour of shallow participation.
Treat chat debates like meetings: join at a time or read a summary later.
Example 4: Machine wait to second project
Deploy runs. You "just" start another feature. Pipeline fails. You ignore it for twelve minutes while the new feature loads context. Both threads are now red.
Cost: missed failure plus two partial contexts.
Rank wait work by abandon cost (work while build runs).
The social switch matters too
Switching from individual focus to video call reloads persona: camera, tone, agenda. Back-to-back calls with coding between them often produce neither good calls nor good code.
Leave buffer between modes, even five minutes to write the next action before joining.
Caps that work
One active thread for composition work (code, design, long writing).
Batch shallow work (email, triage, reviews) into two windows.
Write resume crumbs whenever you leave a thread: next action, links, state (clear next action).
Name switches in the plan so they are intentional, not stolen by pings.
Debug switches cost double
Mid-debug switches are the worst case (interruptions during debugging). Protect them with tiers and parks.
Measure the bill
For three days, note each unplanned switch and rough rebuild minutes. Most people find chat and "quick" reviews dominate, not big project changes.
Fix the top two sources before buying a new app.
Protect focus at home reduces external switches. Internal switches need batching and honest capacity (structure a remote workday names how small adds consume the plan).
Context switching is not a personal flaw. It is a load. Lower the load or pay the rebuild time on every invoice and every deadline.
Estimate switching tax in planning
When you schedule four different project types in one afternoon, add invisible buffer: not calendar padding for lunch, but fewer promised deliverables.
If each switch costs fifteen minutes of rebuild, four unplanned switches are an hour gone before guilt kicks in.
Tools that help and hurt
Multiple monitors reduce window thrash but can invite parallel threads. One monitor forces focus but slows legitimate reference checks.
Pick a layout for the day type. Depth days: one main screen for code. Coordination days: split with inbox visible.
Notifications are switches you outsourced to vendors. Turn off marketing; keep only tier-one paths.
Team agreements
Agree on "no meeting Wednesdays" or "focus mornings" as a norm, not as individual heroics. Norms reduce the social cost of ignoring a ping.
Document the norm where new hires look first. Silent norms do not exist.