Why care delivery doesn’t scale — and what externalizing the work of care actually means.
Imagine you had to hand your entire panel to someone else tomorrow morning. Not a weekend of cross-coverage — the whole thing, permanently.
What would actually transfer?
The charts, obviously. The problem lists, the med lists, the notes going back years. On paper, everything the next physician needs is right there in the record. And yet every one of us knows, with total certainty, that something enormous would be lost. The new doctor would spend months rediscovering things you already know. Some of it they would never rediscover at all.
That gap — between what’s in the chart and what’s in your head — is one of the central unsolved problems in medicine. And it’s the reason care delivery doesn’t scale.
Every good physician has built a private operating system
Somewhere in your third or fourth year of practice, you stopped following the system and started building your own.
You developed a shorthand. A place in the note where you always put the thing you’re worried about. A way of phrasing an assessment that tells you, on re-read, exactly how confident you were. You learned that Mrs. R’s daughter is the one who actually fills the pillbox, so any med change has to be relayed through her. You learned which cardiologist calls back and which one doesn’t. You learned that when this particular patient says he’s “fine,” it means something different than when that one does.
None of that is in a field. There’s no discrete data element for the daughter is the real historian or I don’t trust this A1c. It lives in your notes as shorthand, if it lives anywhere at all — and mostly it lives in your head.
This private operating system is not a bug. It’s a mark of expertise. It’s what separates a physician who has known a patient for eight years from one meeting them for the first time. It is the accumulated, compressed judgment of thousands of encounters.
It is also completely non-transferable, and that is the problem.
Notes are compression, not shared thinking
We tell ourselves that the note is the record of our reasoning. It isn’t, really.
The note is an artifact produced by reasoning — compressed for billing, for legal defensibility, for the version of you who will read it in six months and needs a fast reminder. It’s written by an author who assumes he’ll also be the only reader. Which is why your notes are legible to you and merely decodable by everyone else.
Watch what happens when you read a colleague’s note on a shared patient. You can extract the facts. You cannot reconstruct the thinking. Why did she stop the beta blocker? Was that a considered decision or a reflex to a soft blood pressure? Is “will monitor” a real plan or a placeholder? You don’t know, and the note can’t tell you, because the note was never built to carry that.
Sociologists have a name for the labor that surrounds this. Anselm Strauss called it articulation work — the business of putting tasks, sequences, and clusters of tasks together so that the actual work can flow, a concept he developed alongside his research on the social organization of medical work. In clinic, articulation work is the thing you do in the gaps: remembering, sequencing, re-orienting, deciding what matters next. It’s real work. It’s just invisible work, and it has no home in the chart.
So it goes in your head.
Brains don’t scale. Systems do.
Here’s why this stops being an interesting observation and starts being an urgent one.
Medicine is being asked to care for more patients, with more complexity, with fewer physicians per capita, across more distributed teams. Care is delivered by a rotating cast: you, your partner, the covering doc, the NP who just joined, the pharmacist doing titration, the care manager calling between visits, the hospitalist who admits at 2 a.m. The old model assumed a single physician holding a single patient’s story in a single mind. That model is quietly, thoroughly obsolete.
But we never replaced its infrastructure. We just added people to a system whose intelligence still resides inside individual skulls.
Think about where your private operating system fails today:
- Coverage. Your partner sees your patient and misses the thing you would have caught, not through incompetence but through inaccessibility.
- Handoff and sign-out. You compress eight years of context into ninety seconds and hope.
- Team-based care. The pharmacist doesn’t know you were already planning to back off the diuretic. The care manager doesn’t know why the referral matters.
- Turnover. A physician leaves and takes a thousand patients’ worth of tacit knowledge with them. We treat this as unremarkable. It’s catastrophic.
- You, eight months from now. The most common failure. You reread your own note and the shorthand no longer decompresses, because the mental state that produced it is gone.
Every one of these is the same failure: a system that works brilliantly and privately, encountering a world that requires it to work publicly.
What externalizing actually means
The instinct is to say: document more. Write better notes. Put the reasoning in.
That instinct is a trap, and it’s why so many documentation initiatives make physicians miserable. More documentation is more burden, and burden is the thing we’re trying to eliminate. Externalizing your system is not the same as narrating it.
What it means instead is building infrastructure that holds the work of care, so it doesn’t have to be held in a person. Four properties matter:
Reproducible. The same clinical situation produces the same structure every time — not because you typed it the same way, but because the system organizes it that way. Anyone can walk into it and know where things are.
Reliable. A follow-up you set doesn’t depend on you remembering to look. It surfaces because the system surfaces it, whether you are on service, on vacation, or gone entirely.
Consistent. The same information appears in the same shape across patients, across clinicians, across settings. Structure becomes invisible so attention can go to content. (This one deserves its own argument, which I’ve made in I Don’t Read Charts. I Hunt Through Them.)
Persistent. The state of care — what we’re working on, what’s outstanding, what’s next — lives outside any single person’s memory and outside any single encounter. It carries forward.
Put those together and something changes in character. The story of a patient’s care stops being something a physician maintains and becomes something the physician contributes to and reads from. It becomes an object in the world rather than a state in a mind. That’s what makes it possible for a team to care for a patient without pretending to be a single brain.
The part that hurts
There’s a reason this feels heavier than a workflow problem.
Being the sole storage medium for your patients’ care is not a neutral job description. It means the right thing happening depends on you personally holding it in mind, across weeks, across hundreds of patients, forever. Most days you manage. The days you don’t are not forgettable, and they accumulate.
That accumulation has a name — moral injury rather than burnout — and it deserves more than a paragraph. I’ve written about it separately in The Work Before the Work.
For now, one line: you didn’t train for a decade to be the storage medium.
The work of care should outlive the person doing it
The private operating system every good physician builds is one of the most remarkable things about clinical expertise. It’s also a fragile, unbacked-up, single-instance piece of infrastructure that we’ve somehow made load-bearing for the entire health system.
Externalizing it isn’t about replacing physician judgment. It’s about giving that judgment somewhere to live besides one exhausted person’s memory — so that the next clinician, the next visit, and the next version of you can all pick it up and keep going.
The goal isn’t a system that thinks for you. It’s a system that remembers with you.
What part of your practice lives only in your head? And what happens to your patients on the day you can’t be there?