The Context-Switching Cost

Every switch between projects carries a cognitive cost. When you switch from Project A to Project B, your brain does not instantly transition. It must disengage from A, recall the context of B, re-engage with B, and then begin productive work. This transition takes time — research suggests an average of fifteen to twenty-five minutes to reach full focus on a new task — and the cost accumates with each switch. A day spent switching between five projects, even if each switch is brief, may involve an hour or more of transition overhead, time that produces no output. More importantly, the quality of work in each project is degraded, because full focus is never achieved — the brain is perpetually in a state of partial engagement, never reaching the depth of concentration that complex work requires. The person who manages multiple projects by switching between them is not doing five projects. They are doing five projects poorly, at a higher cognitive cost than doing them well, one at a time.

Managing multiple projects is not about doing them all at once. It is about knowing which one matters now — and having the discipline to let the others wait.

Sequencing Over Simultaneity

The alternative to simultaneous work is sequencing — arranging projects in an order that allows each to receive focused attention, one at a time, while maintaining awareness of all. Sequencing requires two things: a clear understanding of each project's priority, timeline, and dependencies, and the discipline to focus on the current project without yielding to the anxiety of the others. The sequence is determined by several factors: deadlines (projects with nearer deadlines generally take priority), dependencies (projects that unblock other work go first), and importance (projects that serve higher-priority goals take precedence). Once the sequence is established, the practice is to focus on the current project — fully, without checking on the others — until it reaches a natural stopping point, then transition to the next. This approach produces more output, higher quality, and less fatigue than the simultaneous approach.

The Project Dashboard

Managing multiple projects requires a system that provides visibility without constant engagement — a way to know the status of all projects without actively working on all of them. This is the project dashboard: a single view, updated regularly, that shows each project's status, next action, and deadline. The dashboard serves two purposes. First, it provides the awareness that prevents the anxiety of not-knowing — the feeling that something is being neglected, which drives the compulsive checking that fragments attention. Second, it supports the sequencing decisions — which project to focus on next, based on current status and priorities. The dashboard, reviewed daily or weekly, provides the visibility needed to sequence effectively, without the constant context-switching that visibility-through-engagement requires. The projects are all visible. Only one is being worked on. This is the balance that makes multiple-project management effective.

Defining Done for Each Session

When working on one project at a time, it is essential to define what 'done' means for each work session — the specific outcome that, when achieved, allows a clean transition to the next project or to non-work. Without this definition, work sessions tend to drift — continuing until interrupted, with no clear stopping point, which makes transitions feel incomplete and leaves the project in a state that is hard to re-enter later. Defining done — 'complete the introduction,' 'finish the data analysis,' 'draft the first three sections' — provides a clear target, a sense of accomplishment when reached, and a clean transition point. The definition should be achievable within the available time block, specific enough to know when it is reached, and meaningful enough to represent real progress. This practice, applied to each project session, transforms work from open-ended effort into a series of completions, each of which builds momentum and reduces the cognitive residue that complicates transitions.

Communicating Across Projects

Multiple projects usually involve multiple stakeholders, and the sequencing approach — focusing on one project at a time — can create anxiety for stakeholders of the projects that are not currently being worked on. This is managed through communication: setting clear expectations about when each project will receive attention, providing regular status updates, and being responsive — without being reactive — to urgent issues. The stakeholders who know that their project is sequenced for Thursday, and who receive a status update on Wednesday, are less anxious than stakeholders who do not know when their project will be attended to and who therefore assume it is being neglected. Communication does not replace sequencing. It makes sequencing sustainable, by ensuring that the focus on one project does not create problems with the stakeholders of the others.

Managing multiple projects successfully is not about doing them all at once. It is about sequencing — knowing which project matters now, focusing on it fully, maintaining visibility of all through a dashboard, defining clear outcomes for each session, and communicating with stakeholders to prevent anxiety. The approach that seems slower — one project at a time — is actually faster, because focused work produces more and better output than fragmented work. The discipline to sequence, rather than to switch, is what makes multiple-project management effective.