01 · THE GRAVEYARD
Open a neglected company wiki and ask it a live operating question. Which rattle means stop the machine? Which complaint needs the owner tonight? The search returns a neat page with an old date, an absent owner, and no trail back to the job that taught the lesson. The page exists. The answer does not. That is how a repository becomes a graveyard, and the first mistake is blaming the people who were asked to fill it.
02 · THE BUG
Traditional documentation asks the person who knows to stop the work, predict a stranger's future question, add all the context that stranger might need, and do it now. The depositor pays in full. The benefit may arrive years later, to somebody else, or not at all. That is an incentive laid backwards in time. Thin pages are not surprising. They are the rational output of the clock.
03 · WHAT WON'T COME OUT
The blank page has a second cause. Michael Polanyi wrote, we can know more than we can tell. Some expertise appears as pattern, judgment, and feel before it appears as a rule. A technician hears one rattle differently from another. An owner notices the complaint that does not fit the usual pattern. Ask either person to list every rule from a blank page and the most valuable distinctions may never surface. The limit is not willingness. Some knowing has to be caught in the doing.
04 · CAPTURE IN THE WORK
So do not begin with a retrospective manual. Begin with evidence close to the work. After an exception, ask what changed, what surprised you, and what nearly failed. Keep the job record, the decision, the correction, and the outcome beside that account. Add the owner, date, source, and access boundary while they are still obvious. This is not free capture, and it will not extract every tacit distinction. It is smaller, better-timed work that preserves the incident from which the distinction can later be reconstructed.
05 · MOVE THE COST
Knowledge escrow moves the expensive packaging to retrieval. A real question arrives. Only then does the system gather the relevant incident, work record, correction, and outcome, and shape them for this asker. But retrieval is a gate, not a licence to improvise. The answer must cite its sources, respect the asker's access, show what was redacted, and expose how fresh the evidence is. If those checks fail, the right output is not fluent completion. It is: the archive cannot support this answer yet.
06 · THE REUSE GAP
Lynne Markus gave this timing problem a precise frame in her 2001 theory of knowledge reuse. Her synthesis found that repositories require considerable rework before new users can use what producers left behind, while producers often lack the resources or incentives to do that repurposing at deposit. The producer knows the work but not the future question. The reuser knows the question but arrives later. Knowledge escrow does not erase that gap. It places a human or technical intermediary at retrieval, where the real user, purpose, and evidence are finally known.
07 · Advertisement · Twain GTM Agents
A good outbound message should know why it is being sent. Twain GTM agents research accounts, qualify contacts, and turn live signals into relevant outreach. They work with your CRM, personas, and GTM stack, so the message is not just personalized. It is backed by a specific reason to start the conversation.
08 · THREE ASKERS
Now the same governed evidence can answer three different questions without pretending every asker may see the same thing. The stand-in at six in the morning gets a current checklist for this exception. A buyer's adviser gets a redacted trail inside the diligence scope. A new hire gets a first month in sequence, with owners and expiry dates. The format changes. The evidence does not. Each answer shows its receipts, its omissions, and the boundary of what that asker is allowed to know.
09 · THE REHEARSAL
Here is the turn. Stored material is not transferred know-how. Before the expert disappears, give a stand-in one real exception and ask them to act from the archive alone. Make them show the source, the access scope, and the freshness of every step. Then bring the expert back. What was missing? What was dangerously smooth? Where should the system have refused? A failed rehearsal is useful while the expert can still correct it. After departure, the same failure is permanent ambiguity.
10 · THE STAND-IN TEST
Run one stand-in test this week. Pick a recurring client, supplier, or machine exception that only one person handles well. Ask for the last time it surprised them. Attach the work record, decision, correction, and outcome. Then let somebody else query the archive and make the next move. They must be able to act, verify the answer, and spot what is missing. Correct the gaps while the expert is still present. That is knowledge escrow: not a better graveyard, but operating evidence captured at work, packaged at need, and proved before absence.