Part 6 · Taking Your People With You · Playbook

The campfire protocol.

The fire is going out. Capture the stories. Encode the judgment.

The decision
Name your keeper this week, and put a retention package around them before the market finds them.
7 minute read · Last verified Sep 2026

Every company I work with has one person. They know where the bodies are buried, why the vendor relationship survived 2019, and which customer will leave if you change the product manager. None of it is written down, none of it is in the CRM, and all of it walks out the door the day they retire, resign, or get poached.

That is not a sentimental observation; it is a quantified one. When Boeing's senior engineers retired without structured knowledge transfer, the certification rework that followed became part of a failure that cost the company more than twenty billion dollars, a figure that appears in Senate oversight reporting, not in anyone's risk register beforehand. At asset-heavy operators, internal estimates put avoidable knowledge-decay losses in the hundreds of millions a year, showing up as missed yields and repeated mistakes rather than as an announced write-off. Institutional knowledge is a balance-sheet item that does not appear on the balance sheet, which is exactly why nobody budgets to protect it.

What has changed, and why this playbook exists now, is that captured judgment finally has somewhere to go. A story that used to die in a conference room can now become a rule, the rule a prompt, and the prompt a gate inside the systems your company runs on. The campfire is the discipline that moves knowledge down that chain before the person carrying it leaves.

The protocol: seven phases, one recorded hour a week

The campfire protocol.
1234567 Find the keeper Set the cadence Capture stories Extract the rules Encode Test on the keeper Scale 15+ years ofjudgment weekly, recorded,45 minutes incidents,not principles one ruleat a time prompts, gates,memory the keeper gradesthe output beyond theperson
Phases six and seven are where most attempts die. If the encoded judgment cannot pass the keeper's own grading, it is not ready to scale.

The cadence is the protocol. One recorded session a week, 45 minutes, same day, same time, no cancellations. The moment the campfire becomes reschedulable it becomes optional, and optional knowledge transfer is how Boeing happened. Treat the calendar entry like board prep.

Capture stories, not principles. Ask the keeper for advice and you get platitudes; ask what actually happened and you get the goods. Not "always maintain vendor relationships" but the specific call in 2019, who was on it, what almost broke, and what they did at the eleventh hour. Stories carry the context that makes judgment transferable. Principles are what you extract afterward, one rule at a time, written down in plain language: the unwritten rulebook, finally written.

Then encode, and test against the keeper. Each rule moves down a chain that removes ambiguity at every step: the story becomes a rule, the rule becomes a prompt your team and your AI tools can query, and the sharpest rules become gates, binary checks wired into the workflow itself. The test that keeps this honest is simple: the keeper grades the system's answers. Ask the machine the questions the keeper gets asked, and let the keeper score it. When the answers pass their grading, the judgment has genuinely left the person's head. Until then, keep the campfire burning.

The encoding stack: ambiguity narrows at every layer.
Story Rule Prompt Gate what happened, told whole, on the recording the unwritten rulebook, written, one rule at a time queryable by anyone, human or agent a binary check inside the workflow
Each layer reduces ambiguity. A story informs, a rule instructs, a prompt answers, a gate enforces. Most companies stop at the story, which is why the knowledge dies with the teller.

Finding your keeper: the twenty-minute audit

The keeper audit · 20 minutes
  1. Ask your top ten leaders one question: "Who would cause the most damage if they left tomorrow?"
  2. Watch for the signals: the most-consulted person rather than the highest-ranked one; the one who knows why 2019 survived; the one HR could not replace with a job posting.
  3. Any name that comes up three or more times is your campfire candidate.

Note what the audit does not ask: it does not ask who is most senior, most credentialed, or most visible. Keepers are usually operators fifteen or more years into a specific domain, and they are consulted far more often than the org chart suggests. That gap between consultation and rank is exactly why their knowledge never got documented: nobody with budget authority could see it.

Where to start when there is more than one

Hard to replaceReplaceable
High risk if lostStart here. This is phase one, this month.Document first, then encode.
Low risk if lostSchedule for next quarter.Deprioritize; onboarding handles it.
What this costs

One recorded hour a week from the keeper, a facilitator who owns extraction and encoding (a part-time role, and a natural one for whoever runs your AI program), and the real line item: a retention package around the keeper, because the market does not wait for your succession plan. Failure looks like this: the cadence slips, the sessions drift into status meetings, and the rules never reach a system. The cure for all three is the same standing calendar entry.

Monday
  1. Run the keeper audit with your top ten leaders. Twenty minutes.
  2. Name the top three domains where the knowledge sits in one or two heads.
  3. Schedule the first campfire this month: recorded, 45 minutes, recurring, no cancellations.
  4. Name a facilitator whose job is extracting the rules and building the encoding stack.
  5. Wrap a twelve-month retention package around every named keeper before the next board meeting.
Second edition note

Two things changed since I first taught this. In the first edition, the encoding step was half aspiration; today it is the point. The rules you extract go straight into the prompts, gates, and memory your AI agents actually run on, so the campfire now feeds the company brain directly instead of feeding a binder. And the retention package stopped being an aside. I have watched the market find keepers faster than their own companies did; put the package around them the week the audit names them.

BuildClub · Work together

The campfire is a discipline, not a product.

You can run it yourselves starting Monday. When clients bring us in, it is to stand up the cadence, do the extraction, and wire the encoded rules into the company brain their people and agents run on.

See how we work together The workforce engagement
Sources: Boeing figures from public filings and US Senate Commerce Committee oversight reporting Sep 2026 · Knowledge-decay losses at asset-heavy operators are industry-reported internal estimates, stated as such in the text

Part 6 · Taking your people with you · First Edition version of this topic