the multi-organization problem
For ten years I wrote short posts that circled one object without naming it. The object is a person who belongs to many organizations at once, where every tool assumes one and every method assumes the unit of attention is a task, so the work of moving between them is done by unaided memory. This is the theory in one place, what three fields and forty years of software know about it, whether anyone has solved it, and what a solution has to be.
the thing itself
Count your organizations. Not your jobs. Your organizations: every group with its own state that you owe something to. An employer. Each customer, if you have customers. A household. The side project with one member. The volunteer thing. The body, which has appointments and a vocabulary and a backlog like everything else.
Each of those has its own people, its own words, its own credentials, its own tools, its own open items and its own pace. Each keeps moving whether you are looking or not. And each one, when you are inside it, behaves as though it is the only one you have. Log in and you are there. Log out and the tool forgets you were ever anywhere else.
That is the multi-organization problem. You are one person running N organizations, every tool you own is built for N = 1, and nothing in the stack is responsible for the between. Not the save when you leave one. Not the restore when you come back. Not the choice of which one gets you next. All of it is done by memory, and memory is the one component in the system with a documented decay rate.
Everyone has this. N is greater than one for every adult. It is merely acute for the people I have spent my career among: consultants with six clients on six tenants, managed-service operators, fractional anybody, and now anyone running a stable of agents, where N went from six to sixty in a year.
I hate that we all put up with it. This is my attempt to say what it is, precisely enough that it can be worked on.
what I was writing around
Going back through the blog, the pieces were all there.
In 2019 I defined context switching as movement across “functional domains … two customers, two distinctly different IT technologies, two different tool-sets, or some combination thereof.” I did not notice I had defined the switch as being between organizations, not tasks.
In 2020, two sentences: being away from a project costs more the longer you are away from it. Mind bit-rot.
Across 2016 to 2022 I kept recommending tools that gave each thing a place on the screen: MaxTo, alt-drag, tiling window managers, two monitors with private documents on the second one. A 2019 draft that never went up ends: to manage this, we need colored tools. When someone said tiling window managers solved a problem that doesn’t exist, I said it’s a feature, not a software. I meant the boundary between contexts should be a property of the environment, not a product you install.
In 2021, get it out of email: decisions buried in replies, “context scattered across forwards,” put the work and the conversation about the work in one place. That is a locality argument, and email is the anti-tool because it is the one surface where every organization drains into the same inbox.
From 2019 to 2026 the contraction thread: infrastructure got leaner, one person could cover more, and by this February that had a name, multi-tabling. One person, many tables. More decisions per hour. What I never wrote was the next sentence: more tables means more switches, and nothing in the stack got better at the switch.
And from the Ansible years, 2017 to 2019, the idea that turned out to be the key: resources are stated or unstated; define state; unstated items get queried. I spent years making infrastructure stated so it could be rebuilt from nothing. It did not occur to me that the human side of the work was almost entirely unstated, and that I was rebuilding it from memory every morning.
Six themes, ten years, one object. This piece is what happens when you put them in a room together.
the theory
Five claims. The first three are about what the problem is; the last two are about why it persists.
One. The unit is the organization, not the task. Psychology measures the switch between two rules and finds a fixed cost. The switch that hurts in practice is between two worlds. Each organization is a whole language-game in Wittgenstein’s sense: the same word, “prod,” “the client,” “done,” means something different inside each, and the meaning lives in the practice, not the dictionary. When you cross between them you are not reloading a task. You are reloading a language.
Two. The cost is interest, not a toll. Every switching model I have read charges per switch. The multi-organization cost accrues per unit of absence, on every organization you are not currently in, at a rate set by how fast that world moves and how little of it you wrote down. Two days away is a small bill. Two weeks is a re-onboarding. Two months and you are a new hire with your own name on the old commits. Toll thinking produces batching and timers. Interest thinking produces a ledger. I made this argument on its own in interest, not a toll.
Three. The mechanism is the unstated state. The word “context switch” is borrowed from the kernel, where the switch is cheap for exactly one reason: before a process leaves the CPU, everything it was gets written into a fixed-shape structure, the process control block, and restored from it on return. A person’s context has no block. Whatever is not stated is re-queried from memory, and memory decays. That is the whole of claim two’s mechanism, and it is the argument of no process control block. We took the word from the machine and left the mechanism behind.
Four. Tools solve within, never between. Every tool with a workspace switcher isolates contexts and then drops you inside one. None gives you a root: a surface above all your organizations, belonging to none, showing each one’s state and what each needs. A multi-tenant platform gives its tenants three services: isolation, scheduling, and an operator’s console above them all. The person running many organizations got the first one, by hand, with browser profiles and colored terminals, and neither of the other two. That is human multi-tenancy without the platform.
Five. The fix has two halves and both are required. A mental tool: a discipline of writing the state down before you leave, a fixed shape for it, a ritual for the crossing. And a digital tool: a root surface, per-organization state that tools write into, a scheduler that surfaces need rather than noise. Either half alone reproduces the status quo. Discipline without a surface is a notebook that goes stale. A surface without discipline is another dashboard nobody fills in.
what is known
I went looking for who else has worked on this, expecting to find either that it was solved or that nobody had noticed. Neither. It has been noticed at least three times, by three fields that do not read each other, and each one stopped at the border of the thing I care about. What follows is sourced. I have marked what I could not verify.
the science
Psychology has measured the switch. Rogers and Monsell, 1995: alternate between two trivial rules and switch trials are slower and sloppier; even with 1.2 seconds of warning a residual cost remains that only clears when the actual stimulus arrives. Allport and colleagues, 1994: the reason is task-set inertia; the old task lingers. Sophie Leroy, 2009: the same thing in an office, named attention residue, with the detail that merely finishing the prior task did not clear it but finishing under time pressure did.
Human-computer interaction has named the unit. In 2004 Victor González and Gloria Mark watched information workers and concluded “task” was the wrong size; people organized their day around working spheres, sets of related events sharing a motive: a project, a customer, a responsibility. The 2005 follow-up, twenty-four workers shadowed for a little over twenty-five hours each, found 11.7 working spheres per day, eleven minutes and four seconds per stretch before a switch or interruption, 57.1 percent of stretches interrupted, and a return gap of twenty-five minutes and twenty-six seconds when interrupted work was resumed the same day, with 2.26 other spheres handled in between. The “twenty-three minutes to refocus” figure you have read is not in any of her papers; it traces to a 2006 Gallup interview and measures time-until-return, not time-to-refocus. Mark’s screen-logging, collected in her 2023 book, puts average time on one screen before switching at about two and a half minutes in 2004 and forty-seven seconds by 2016 to 2021.
Sociology has described the ritual. Ashforth, Kreiner and Fugate, Academy of Management Review, 2000, “All in a Day’s Work: Boundaries and Micro Role Transitions”: every role sits on a line from segmented to integrated. Segment hard and each crossing is clean but expensive, so people invent rites of passage, the commute, the change of clothes. Integrate and crossings are cheap but everything blurs, so you do boundary work all day. Christena Nippert-Eng, 1996, watched laboratory staff and found segmentors carrying two key rings, two calendars, two wallets. Sue Campbell Clark, 2000, named the person a border-crosser.
Three fields, three magnifications: the rule at milliseconds, the sphere at minutes, the role at years. I wrote them up on their own in eleven minutes and four seconds. The finding that matters here is what none of them measured. Nobody has a number for what a working sphere costs to come back to after a week. Mark’s outer bound is same-day. The lab’s is 1.2 seconds. The sociologists count crossings, not absences. The quantity that decides whether six organizations is survivable, the decay rate of an untouched world, has never been on anyone’s stopwatch.
Two more results, because they bear directly on the fix. Masicampo and Baumeister, 2011: unfulfilled goals produce intrusive thoughts and degrade performance on unrelated work, and forming a specific plan for the goal eliminates the effect even though the goal remains undone. And a 2025 meta-analysis of the Zeigarnik effect across fifty-nine studies found no real memory advantage for interrupted tasks, but a robust tendency to resume them, about two-thirds versus a coin flip. The pull back toward an unfinished world is real. The mind does not hold the world better for having been interrupted in it. It just wants to go back, and when it gets there, it has to rebuild.
the software
Forty years ago the problem had a design. In 1986 Henderson and Card at Xerox PARC published Rooms: windows cluster by task, so give each task its own workspace with doors between them and an overview of all of them. Every virtual desktop descends from it.
The next two decades tried to add the missing half, memory of what the room was for. UMEA in 2003 declared a project and collected the files, URLs and contacts you touched while in it. TaskTracer in 2005 instrumented Windows and Office to do the same and added a model to guess which task you were in. Bardram’s activity-based computing in 2006 made the activity a first-class operating-system object with suspend and resume across hospital terminals. Mylyn, also 2006, filtered the Eclipse IDE to the code a task had touched, with a measured improvement in sixteen industry programmers; it still ships. Giornata in 2008 gave each declared activity its own desktop.
What shipped everywhere was the room without the memory. Spaces, Windows desktops, GNOME workspaces: “Desktop 1” through “Desktop 4,” none of which knows what it is for. KDE Activities was the one desktop that kept the memory, and in September 2025 Plasma 6.5 removed starting and stopping activities and kept only switching. I wrote this lineage up in the room that forgot what it was for. Every system in it, including the ones that remembered, lived inside one machine, one account, one employer. The unit was the task within an organization. Nobody in the lineage was a consultant with six clients.
Then the present. I surveyed the tools a person with many organizations touches in a day. Chat, identity, cloud consoles, browsers, desktops, terminals, password managers, planners, MSP tooling, and the 2026 crop of agent orchestrators. Nearly all of them are switchers: they isolate a context and hand you a menu. GitHub added an account switcher in November 2023 because Enterprise Managed Users made everyone two people. AWS’s console lets five identities sign in at once, since January 2025, each in its own tab. Superhuman’s help page is titled “Unified Inbox Workaround.” Slack’s 2023 redesign can merge unreads across workspaces, and it is a merged feed, not a view of state.
The genuine roots exist, and they share one property: one party owns every context. 1Password shows every vault from every account. Discord’s inbox spans your servers. Microsoft 365 Lighthouse gives a managed-service provider one portal over every customer tenant they administer. Where the contexts have different owners, the root vanishes and a help article appears. Roots belong to owners, and you are a guest in most of your organizations. I built one, called Tickler, where I happened to own all the organizations, and wrote that up in a root to stand on.
the methods
The productivity literature has its own version, and it is worth being exact about what it does and does not do.
David Allen’s Getting Things Done, 2001, has a concept it calls contexts, which is the right word attached to the wrong unit: @computer, @phone, @errands. A GTD context is the tool or place a next action requires. Multiple roles live at a higher altitude, “Areas of Focus,” which the weekly review sweeps. One system, one set of contexts, no mechanism for the crossing between areas, only for reviewing them. Stephen Covey’s First Things First, 1994, is the earliest mainstream method that plans per role, up to seven of them, and it is a planning device, not a switching one. Tiago Forte’s PARA, 2017 onward, files everything by actionability into one replicated folder structure across every tool; different jobs become separate Areas. It optimizes retrieval, not reconstitution. Cal Newport, in A World Without Email, 2021, prescribes protocols for people serving several clients: fixed communication expectations, client-visible status boards, office hours. His Slow Productivity, 2024, prescribes the other answer: fewer concurrent commitments. Reduce N.
Every one of these assumes a single system in which all your organizations are rows. None has a theory of the between, and only Newport even gestures at the fact that the rows belong to other people.
the recent wave
The 2026 agent tools are the most interesting case because they are where N exploded. Claude Squad and Conductor list agent sessions, in one repo. Cursor’s Agents Window, from April 2026, lists sessions across repos. CrewAI’s CLI has org switch. Paperclip is the only one whose data model has company as a first-class, multi-instance entity, and its interface opens inside one company; issue #2212 against it, “No Cross-Company Coordination Mechanism,” was answered with “by design.” The academic side, three papers from late 2025 and 2026 on how developers oversee agents, studies oversight of one agent or aggregate fatigue. One survey of nearly fifteen hundred workers found cognitive fatigue tied to monitoring several AI tools at once. Nobody has measured the switching cost of one person alternating among several concurrent agent organizations. It is a year old as a mass phenomenon. The stopwatch has not arrived.
Everything above this line is the record. Everything below it is argument.
is it solved
No. But the shape of the no is specific, and it is more encouraging than a flat no would be.
It has been diagnosed three times. Psychology has the switch to the millisecond. HCI named the unit in 2004 and built six systems around it. Sociology described the crossing and the rituals people invent to pay for it. Each field stopped at its own border. The psychologists’ between is a blank screen. Mark’s is the 2.26 intervening spheres. The sociologists’ is a commute. All three treat the time you are gone as empty.
Everything has been built, within. Isolation is solved; it has been solved since Rooms. Memory-of-what-the-room-is-for was built five times between 2003 and 2008 and shipped once, into one IDE. Roots exist wherever one owner holds all the contexts.
Nothing has been built between. No general tool gives a person who belongs to many organizations a root over them. No tool writes or reads a per-organization saved state. No tool shows staleness. No method has a crossing ritual that is more than a commute.
Nobody has measured absence. The decay rate is the load-bearing quantity and it does not appear in any literature I could find.
How far are people from solving it? The pieces are on the table. Mark’s working sphere is the right unit. Masicampo and Baumeister’s result is evidence that a written plan discharges the cognitive cost of an open world. Rooms and its descendants are the container. Mylyn is proof that a tool can build the saved state from what you touched. Lighthouse is proof that a root works when someone owns the tenants. Paperclip is proof that the organization can be a first-class object in a tool one person operates. What does not exist is the assembly, and the reason it does not exist is structural, not technical: the person who needs the root is a guest in most of the contexts it would span, and no owner of a context builds views of contexts they do not own.
So the root has to be built from the guest’s side. That is the gap. Everything else is engineering.
the vocabulary
I want words for this, because a thing without a name gets re-discovered every twenty years and re-shelved. These are proposals. Argue with them.
The multi-organization problem. The condition: one person, N organizations, tools for one, the between done by memory.
Human multi-tenancy. The frame. One person is a platform running many organizations. The platform’s three services, isolation, scheduling, and the operator’s console, are the checklist for what the person is missing.
The block. The fixed-shape record of one organization’s live state, written before you leave it, after the process control block. Five fields are enough: who this is for, what’s open, what I tried, what’s next, what I promised. It comes from the infrastructure principle: what is unstated is queried, and what is queried from memory decays.
Mind bit-rot. The decay of unstated context during absence. I wrote this in 2020 and I am keeping it; it is better than any term in the literature.
The rate. How fast an organization’s context decays: how fast the organization moves, multiplied by how little of it is stated. The thing to optimize, instead of switch count.
Leak. One organization’s traffic arriving inside another’s context. Email is the leakiest surface ever built.
Colored tools. Anything that makes the current organization visible in the environment so the head does not have to carry it. Profile colors, terminal themes, a window region, a second key ring.
The root. The one surface above all your organizations that belongs to none of them. Shows each one’s state, need and staleness. Where you stand between organizations.
the solution, both halves
Two tools, and neither works alone.
the mental tool
Write it down before you switch. Not after. Not at the end of the day. At the moment of leaving, write the block: who, open, tried, next, promised. It takes ninety seconds and it is the only intervention in this whole essay with a controlled result behind it: a specific written plan discharges the intrusive cost of an unfinished goal. The block is a plan. It is also the thing that turns interest into a fixed fee, because a stated world decays far more slowly than an unstated one.
Make the crossing a ritual, and make it short. The sociologists are right that segmented roles need rites of passage, and the mistake is to make the rite a commute. The rite is: write the block for the world you are leaving, go to the root, look at every world’s need, choose. A minute. The point is not the pause. The point is that the choice of the next organization is made from the root and not from inside whichever one shouted.
Color everything. Every organization gets a visible marker in every tool that will hold one. This is the isolation half of multi-tenancy, done by hand, and it is the part we already know how to do. Do it more than feels reasonable.
Batch by organization, serialize within. My 2022 note said “multitask between specific problems, solve them one by one.” That is a scheduling policy: do not interleave organizations inside an hour; inside one, take the open items in order. It is the one piece of the toll model worth keeping, because within a single organization the toll model is correct.
Reduce N where you honestly can. Newport is right that the cheapest organization is the one you do not belong to. But this is a lever with a floor. Nobody gets to N = 1, and the people the problem is acute for cannot get near it. The mental tools are for the N you are left with.
the digital tool
A root that is yours. A surface above every organization, owned by you, reading from each what it will expose and holding the rest in blocks. Per organization, one line: state, need, staleness. No merged feed. No metrics of its own. The place you return to between organizations, and the place the crossing ritual happens.
Blocks that tools write. The write-it-down discipline fails when it depends on a person typing at the worst possible moment. Mylyn proved in 2006 that a tool can build the saved state from what you touched. Agents make it trivial: they were there when you left. An agent that writes your block for each organization it works inside, in the fixed shape, is the single highest-leverage thing an agent can do for the between, and it is exactly the observer-that-does-not-act I asked for in forty terminals, scoped to organizations instead of sessions.
A staleness column. Every organization’s time-since-you-looked, times a rough rate. This is the ledger. It is the one number that no tool shows and the one that should decide where you go next, because it is the interest coming due.
Leak control. Route every organization’s traffic to that organization, not to you. The inbox that receives from everyone is the design error, and it is fixable per organization even when the organizations are not yours: a filter, a folder, a profile, an account. Leaks are the only part of the problem that gets worse the more disciplined you are, because disciplined people answer them.
Federation, eventually. The hard version is the root over organizations you do not own, reading from six organizations where you are a guest, each of which would rather you saw only it. The honest answer is that it will be built from the guest’s side, out of whatever each organization exposes, plus blocks, plus an agent that visits each one on your behalf and writes down what changed. That is not a product anyone sells. It is close to being something one person can assemble.
the part I actually believe
The multi-organization problem is not a productivity problem, and I want to stop it being filed there, because that is the shelf it has been re-discovered on and put back on since 1986.
It is an architecture problem, in the plain sense: a missing layer with a missing owner. The kernel has a scheduler because someone decided the CPU was a shared resource with many claimants and that the sharing needed a mechanism, not a habit. Nobody has decided that about a person. Every organization you belong to treats you as its own, builds you a switcher to get to it and a feed to keep you there, and the sharing of you is left to you.
Three fields have looked directly at this and each has walked back to its own border. Forty years of software built the room and lost the reason for it. The tools of the last twelve months multiplied N by ten and shipped a sidebar.
What I have, after ten years of circling, is a unit, a cost model, a mechanism, a vocabulary, and a first root, Tickler, built in the one place I happened to own all the organizations. What I do not have is the number. Nobody has measured what a world costs to come back to after a month, because everyone who could measure it believes the month was empty.
It was not empty. It was where the bill got written. The rest of this is about learning to read it.