The standard advice on context switching is wrong. Or rather, it’s right for someone who works on two things and switches between them. For someone running five, the standard advice doesn’t apply, because the problem isn’t the switch itself. The problem is the debt that accumulates around it.
What Context Switching Costs
The literature says context switching costs you ~20% productivity per switch. That’s measured in lab settings on people doing one thing, getting interrupted, going back to the original thing.
Real multi-project work doesn’t look like that. Real multi-project work looks like: you spend Monday on Project A and make three decisions. Tuesday you spend on Project B. Wednesday you’re back on Project A but the three decisions from Monday are partially gone from your head. You re-derive two of them, which takes time. You misremember the third one, which causes a bug or a wrong commitment.
The cost isn’t the switch. The cost is the rebuild.
Cognitive Debt
Each time you context-switch, you build up cognitive debt. Decisions you made get half-stored. Reasoning you went through gets half-retained. State changes you committed to get half-tracked.
The debt compounds. By Friday of a five-project week, you’re carrying a load of half-finished mental models. Some are still accurate. Some have drifted. You don’t know which.
This is why multi-project operators wake up at 4am wondering if they sent that email. The debt doesn’t surface on its own. It surfaces when you can’t pay it.
What Doesn’t Work
Time-blocking. “Mondays are for Project A, Wednesdays for Project B.” Works in theory. Falls apart the first week a real fire happens. By month two, your calendar is a fiction.
Pure delegation. “I’ll just hire someone for Project B.” Works if you can fully delegate. For owner-operator work, you can’t. The strategic decisions still flow through you. The delegation reduces volume but not switches.
Discipline-based recall. “I’ll just remember better.” You won’t. Working memory is a fixed resource. Loading 5x as much state doesn’t make you 5x as good at recall. It makes you 5x as likely to forget.
What Works
External state. Treat your brain as a CPU and your project files as memory. Don’t store decisions in your head. Store them in writing, in a place you can find them, in a format that’s quick to scan.
Three pieces of infrastructure made the five-project life sustainable:
1. A status file per project. Three sections: Active Priorities, Blockers, Recent Updates. Updated at the end of every session that touched the project. Read at the start of every session that returns to it. The status file holds the cognitive state I would otherwise be holding in my head.
2. A session log per project. Short entries, time-stamped, written as I work. Not after. “10:30 - chose RS256 over HS256 for JWT signing because key rotation requirement surfaced in conversation with X.” Six months from now, when I read that line, I have full context. Without it, I’d see the code and wonder.
3. A cross-project status report I read every Monday. Aggregated automatically by an agent. Tells me where every project is. What’s stalled. What’s overdue. What I last touched. The report is generated; I don’t write it. I just read it and use it to plan the week.
These three together cost about 90 minutes a week to maintain. They save me the cognitive debt that would otherwise compound across five projects.
The Real Insight
Context switching isn’t the enemy. Trying to hold the context internally is the enemy. The brain is a bad database. Once you accept that, you stop optimizing for “switching less” and start optimizing for “switching cleanly.”
A clean switch looks like this: close one project by writing down where you are. Open the other by reading where you left it. Zero working-memory carryover. The current project is the only one in your head, but you can return to any other one in five minutes by reading its status file.
This is also why I don’t believe in “deep work” as a defense against multi-project life. Deep work assumes you only have one deep thing. If you have five, the answer isn’t “be deeper on the one you’re touching” - it’s “be cleaner about how you enter and exit each one.”
What This Lets You Do
Once you’ve offloaded state to files instead of holding it in your head, the constraint changes. You’re not limited by working memory anymore. You’re limited by how many sessions you can run per week, which is mostly a calendar problem.
That’s manageable. Working memory isn’t. The shift from “I have to remember everything” to “I have to write everything down” is the whole game.