Context switching between projects: how to cut the cost when you juggle clients

Context switching is shifting your attention from one task to another, and it carries a restart cost: the time it takes to reload what the new task requires. When you move from Client A’s website to Client B’s brand guidelines, you have to recall decisions, find files, reread the last message, and remember what you promised.

Researchers have studied the effect for decades under names like task switching and attention residue, the idea that part of your mind stays on the previous task after you move on. You do not need a study to recognize it, though. It is the feeling of having been busy all day and finished very little.

Context switching is worse with several clients because each client carries a separate set of context: different people, different decisions, different tools, and different promises. Switching between two tasks in one project reuses most of what is in your head. Switching between clients often reuses almost none of it.

Messages make it worse still. An email from Client C in the middle of a deep block for Client A pulls you across the whole gap and back again, often for something that could have waited two hours.

Reduce context switching by making each switch rarer and each restart cheaper. These six habits do both:

1. Protect client blocks. Give deep work for one client at least 90 minutes without other clients in it.
2. Batch shallow work across clients. All approvals in one sitting, all follow-ups in another.
3. Write a next-step note before every switch. One sentence: what you were doing and the next physical action.
4. Keep each project’s context in one place. Files, decisions, and messages reachable from the project, not scattered across apps.
5. Check messages at set times. Tell clients when you respond, and keep that promise.
6. Plan the day across all clients at once. A short morning sweep prevents the reactive zigzag. The multi-client guide has the full routine.

A good next-step note says what you were in the middle of, the very next action, and anything you were about to forget. It takes thirty seconds to write and can save ten minutes of rereading when you return.

Keep the next-step note alongside its project tasks, files, and commitments. Portfolio helps you choose which project gets the next block; Execute is where you work on that selected project.

Use Nodes when stored relationships need inspection. For simple work, a clear task and a short note may be enough. The point is to shorten the restart, not to open every tool on every switch.