If your most experienced person left tomorrow, how much would your team struggle the day after?

Most organizations only ask that question when a resignation letter is already on the desk. By then it's a scramble. But the problem was there long before the letter — quietly, every day, in the form of one person who is the only one who knows why.

There's a name for the logic running behind every process, every compliance call, every judgment — undocumented, unacknowledged, but load-bearing. When the expert leaves, the steps remain. The logic disappears. It's called Ghost Code. You don't need a retirement announcement to have a Ghost Code problem. You just need one person who is the only map.

Question 1 — What is the "it depends" of this team?

Ask the people who lead the work: where do new hires consistently stall? Listen for "they just need to get a feel for it" or "it depends." That phrase is the tell — a real, knowable rule exists, but it lives in one person's head instead of in your institution.

🟢 We can point to the written rule. → Healthy.   🟡 We have notes, but people still check with one person. → The logic is leaking.   🔴 "You just get a feel for it." → Ghost Code. A dependency, not a skill.

Question 2 — If your top expert left tomorrow, which process drops in accuracy first?

Ask which specific process would degrade, and how fast. It moves succession from a someday-worry to an immediate operational consequence. Whatever they name isn't a training gap — it's a vulnerability with a name and a deadline.

🟢 Accuracy holds — others can reconstruct the reasoning.   🟡 It'd wobble, then recover.   🔴 That process would break, and we'd be guessing. → That's infrastructure leaving.

Question 3 — Where are we training people on the steps instead of the source logic?

Open your onboarding material. Are you teaching what buttons to push, or why those buttons exist? If it's only steps, your training depends on the expert still being there to answer "but why?"

🟢 Our training traces each step to its source.   🟡 Some of it.   🔴 We document the steps; the "why" is assumed. → When the expert goes, the reasoning goes with them.

What the answers mean

Mostly green — you've separated the logic from the person. Rare. A few yellows — the logic is leaking; cheapest moment to act. One or more reds — a load-bearing dependency on one person. The good news: it's usually explicit knowledge that never had a home. It can be surfaced, mapped, and transferred — before it walks out the door.

Ends with a soft CTA: book a 20-minute Ghost Code Risk Call. (Full manuscript also in the kit as 01_Ghost_Code_Diagnostic_LeadMagnet.)

Subject: Your Ghost Code Diagnostic

Here's your Ghost Code Diagnostic. It's three questions — about ten minutes to work through honestly — and they'll show you where your institutional knowledge is most likely to break first.

A suggestion: don't answer them alone. Ask the people who actually lead the work where new hires keep stalling. The answers you get out loud are usually more honest than the ones you'd write down by yourself.

Over the next week or so I'll send a few short notes — the thinking behind each question, and a case where this played out with real numbers. For now, just run the diagnostic. Count your reds and yellows. — Oliver

Subject: It's not complex. It's hidden.

Most of what gets treated as "complexity" isn't complex. It's hidden. When a team experiences every case as an edge case, it's usually because nobody can tell a routine situation from a real exception — the rule that separates them was never written down. It lives in one person's head.

"Complex" is a wall — all you can do is wait for new people to slowly absorb it. "Hidden" is a door — you can find it and give it a home. So with each red on your diagnostic, ask: is this really too complex to transfer? Or is it explicit knowledge that just never had a home? Most of the time, it's the second one. — Oliver

Subject: Seven analysts in eighteen months

A public-sector division had cycled through seven analysts in eighteen months. Every new case sent them back to the one experienced analyst with the same question — "Now what?" — and the answer was always "it depends." Nobody had asked what it depended on. When I traced it, the answer wasn't her judgment. It was the law.

So we built the map — a curriculum on the source logic, not the steps. Six months later: three new analysts reached independent operation, questions to the principal dropped about 90%, and they're now two and a half years in. She's still the most experienced person in the room. She's just no longer the only one who understands why. — Oliver

Subject: Your experts are maintainers

In open source there's a role called the maintainer — the person who holds the load-bearing logic of a system. When a maintainer leaves, the code stays exactly where it was, but the reasoning goes with them, and the people left behind can't tell whether a change is safe anymore.

Your veteran employees are maintainers too. When they leave, the documented process remains and the architecture behind it disappears. That's why Ghost Code isn't an HR inconvenience — it's an infrastructure problem, and in the public sector, infrastructure failures have a public on the other end. If one of your answers came back red, that's a maintainer you haven't backed up yet. — Oliver

Subject: Want a second read on your diagnostic?

If even one answer came back red or yellow, you already know more than most organizations do. If it'd help, I'll give you a second read — a 20-minute Ghost Code Risk Call. We walk through your three answers and I help you identify the single dependency most worth closing first. No pitch, no deck.

And if now isn't the time — keep the diagnostic. Run it again in six months. The point was never to sell you something. It was to make sure the question never catches you by surprise. — Oliver

• 01When the expert leaves, the steps remain. The logic disappears. That missing logic has a name: Ghost Code.
• 02You don't need a retirement announcement to have a knowledge problem. You just need one person who is the only map.
• 04Most of what gets called "complexity" isn't complex. It's hidden. Complex is a wall. Hidden is a door.
• 11Ghost Code isn't an HR problem. It's an infrastructure maintenance failure with compliance consequences.
• 18She's still the most experienced person in the room. She's just no longer the only one who understands why. That's the whole goal in one sentence.

"The Only Map"

What seven analysts in eighteen months taught me about knowledge that's documented but invisible. The case study, restructured for a general audience — from "it depends" to the law underneath it to the curriculum that changed the division.

"Why You Can't Document Your Way Out"

The reason "just write it all down before you go" almost never works — built on three borrowed ideas (Sinek on the limbic "why," Nonaka & Takeuchi on externalization, Asparouhova on maintainers), credited and kept light. The theory piece for the sophisticated reader.

Cadence: LinkedIn 2×/week (primary), X 3–4×/week, a long-form piece every 3–4 weeks. There's an 8-week launch sequence that walks a cold audience through the idea the way a good talk does: name the problem → make it concrete → the diagnostic → raise the stakes → offer the standard.

The engine (this is the part that lasts): you already write long — case studies, talk notes, debriefs. You don't "create content," you decompose what you already wrote. One source doc → ~6–10 X posts, 3–5 LinkedIn posts, a story post, maybe one essay. That's two weeks of posting from one document.