The Tuesday Henrik Said He Was Leaving
It was a Tuesday in March. Henrik came to breakfast and announced, between two slices of toast, that he'd be moving back to Norway in October. Six months. Plenty of notice, he said. Plenty of time.
For most of the table it was sad but ordinary. Members come and go. Henrik had been with us nine years. We'd miss him.
I sat there counting in my head. Henrik was the only person who'd worked on our well pump. He knew about the boiler's two angry winters. He knew that the third washer fitting in the laundry shed needs PTFE tape doubled twice or it leaks by Christmas. He knew where the original septic baffle was buried. He knew which neighbor to call when we needed a chainsaw repair done cheap.
None of this was written down anywhere.
I finished my toast. I went into the kitchen and made another coffee. I tried to act normal. Inside I was running an audit, and the audit was telling me we had a problem.
What Tacit Knowledge Actually Is
Tacit knowledge is the stuff that lives in members' heads and never quite makes it into a document. Sometimes because nobody thought to write it. Sometimes because the person who holds it doesn't realize they know it. The philosopher Michael Polanyi gave it the cleanest description: we know more than we can tell.
In an intentional community, tacit knowledge accumulates faster than almost anywhere else I've worked. The infrastructure has quirks. The vendors have relationships. The compost has a history. The members have a history with each other. The land itself has a history. Almost none of it is in the Library. Most of it lives in three or four people, and a lot of it lives in the one person you're about to lose.
Documenting tacit knowledge is the practice of getting that information out of heads and into a form the community can keep. It's slower than writing meeting notes. It's also the single highest-leverage investment a small community can make in its own survival.
The Knowledge That Always Walks Out First
After watching about fifteen members leave various communities over the years, the same kinds of knowledge tend to walk out the door first.
Infrastructure quirks. The boiler resets if you hold the red button for nine seconds. The septic alarm is a false alarm if it rings before 7am. The cold tap in the upstairs bathroom only runs after you've flushed twice. Nobody writes this down. Everybody learns it.
Vendor relationships. Maria's husband does chainsaw repairs cheap if you mention you met at the school fair. The roofer in the village will come on a Sunday if it's an emergency. The seed company gives a 15% discount to anyone who emails before March. These are phone numbers in someone's head and a small social currency.
Why-we-stopped-doing-X knowledge. We tried a milk cow in 2019 and it broke three of us. We had a compost loo in the front field for two summers and the neighbors hated it. We don't do solstice fires anymore because the council fined us. The reasons disappear within two years of the decision. The decision itself is on the record. The reasoning isn't.
Conflict history. Who fell out with whom. Why those two members don't sit next to each other. Why we changed the membership criteria in 2021. New members can't see the pattern. Old members forget there's a pattern to see.
Seasonal rhythms. When the apples are ready. When the slugs come out. When the south paddock starts to flood. The almanac that lives in one member's notebook and that member's notebook only.
Each of these categories is worth capturing. None of them survive on their own.
Why Most Communities Wait Too Long
The standard mistake is to think about tacit knowledge only when someone announces they're leaving. By then you've got three to six months. Too little time, too much pressure, and the departing member has half-checked-out already. They want to spend their last weeks on goodbyes, on packing boxes, on walking the land. They don't want to spend them writing the manual.
The fix is to treat the capture as a continuous practice, separate from any specific departure. Once a year, every year, for everyone. Not a crisis response. A standing rhythm.
In our Sanctuary we run an annual interview process for every member. The work is spread across the spring quarter. The result is one of the most valuable things we produce all year.
The Annual Interview
Two members do the asking. One holds a notebook and a small audio recorder. The interviewee gets three categories of questions, in this order.
1. What do you do here that nobody else knows how to do? This catches the obvious stuff: the well pump, the seed-saving, the legal filing, the tax accounting. About 60% of the value lands here.
2. What do you know that you'd struggle to write down? This catches the harder stuff: the relationships, the reasons, the seasonal calendar in your head. Slower to surface. Worth waiting for.
3. If you weren't here next week, what would the community quietly lose? This is the question that catches the things even the holder didn't realize they held. Long pauses are normal. The answers that take a minute to arrive are usually the most valuable.
Each interview produces three things: an audio recording, a written summary of the highlights, and a list of follow-up Scrolls to write before the next quarter.
It is exhausting work. Two interviewers running fourteen members across six weeks takes about forty hours of community labor. That's the price. It's a fraction of what we'd lose if Henrik had left without us paying it.
Apprentice Every Critical System
Writing doesn't catch tacit knowledge fully. The well-pump Scroll can list every part number, every service date, every quirk in the maintenance log, and the next member still won't recognize the rattle that means the impeller is failing.
So pair every critical system with a designated apprentice. They shadow the expert through a full annual cycle. They do every service interval, every seasonal task, every "huh, that's not right" moment that pops up across twelve months.
For our 14-adult Sanctuary we run apprenticeships on six systems: the well pump, the boiler, the septic, the legal filings, the bookkeeping, and the bee hives. Six experts. Six apprentices. About forty hours per pair per year. We rotate apprentices every two years so the knowledge spreads.
Three years in, we have functionally redundant coverage on every critical system. If anyone falls off a ladder tomorrow, the community keeps running. That sentence isn't dramatic. It's the entire point.
The Walking Tour
Once a year, the longest-tenured members walk the full property with newer members. Three hours. Stop at every quirk. Tell the story.
"This valve here was replaced in 2019 because the old one kept sticking when the temperature dropped. The new one is bronze. Costs three times as much. Worth it." That sentence captures more than four pages of writing.
We schedule the walking tour the week after the spring equinox. About six people typically come, two of them new. We record the audio on a phone in someone's chest pocket. Later, one member sits with the recording and pulls out the bits worth turning into Scrolls. Most of it doesn't get transcribed. The audio sits in the archive, indexed by stop.
When Someone Is Actually Leaving
When a member with deep tacit knowledge announces a departure, the playbook changes. We block out two full days in the first month after the announcement. Walk every system together. Record everything. Identify which apprentice is taking each domain. Block four to six follow-up sessions across the remaining time.
It's a heavy month. We treat it as a Garden in itself, with its own Seeds, its own owner, its own rhythm. The departing member is on light duties otherwise. The transfer is the work.
Henrik's departure produced eleven new Scrolls, three audio walking tours, and one apprentice (Sara) who is now the de facto person on the well pump and the boiler. He left in October. The boiler had its first scheduled service under Sara in February. It ran clean. We sent Henrik a photo.
The Founder Problem
The hardest case is the founder. Founders hold an order of magnitude more tacit knowledge than anyone else, partly because they made every original choice and partly because everyone else has unconsciously deferred to them for years.
Plan for the founder transition from year three onward, while the founder is still happily present. Run the annual interview every year. Apprentice every domain twice. Treat the founder's residual influence as something to redistribute, deliberately, before they're gone. The exercise in Power Mapping is most of the diagnostic for what's still load-bearing.
A founder departure that's been prepared for ten years is a graceful transition. A founder departure that's been ignored is, usually, the end of the community within three.
Where the Records Live
The audio, the Scrolls, the apprentice rotations all live in ARA's Library. One folder per system. Each Scroll links to the audio it came from. The annual interviews live behind a tighter visibility setting (current members only) because they sometimes contain reflections people wouldn't say in public.
That's the explicit scaffolding. The harder part, the work the tool can't do, is the apprenticeship itself. Two people, side by side, across a year. The tool stores what gets said. The relationship is what carries the knowing.
The piece on documenting decisions is the closer companion to this one. Decisions are the easy half: written, dated, voted on. Tacit knowledge is what surrounds the decisions and makes them legible. Both matter. Both compound.
The Quiet Compounding
Communities that do this work have a strange property. Members leave less often. And when they do leave, the loss is smaller.
The capture practice itself slows the exits. Being interviewed annually makes members feel seen. Being asked what you uniquely know is, it turns out, a kind of love. Several of our members have told me the interview is one of the things they look forward to most in the year.
And when somebody does go, the community doesn't crater. The Scrolls cover the explicit part. The apprentices cover the practical part. The audio archive covers the texture. Three years in, we keep maybe 90% of what used to walk out the door. The remaining 10% is real but survivable. The 90% is what stays the community.
Start With Yourself
If your community has never run this practice, start with the longest-tenured member. Block 90 minutes this month. Ask the three questions. Record the conversation. Take the notes.
Next month, do another. Take a year to interview everyone. By next March you'll have a body of recorded knowledge no other community in your region has. It will already be paying you back.
Tacit knowledge walks out the door whether you capture it or not. The work is asking for it while the people who hold it are still here. Henrik is still around when we have a question we can't crack. He picks up the phone. But we don't need him most of the time. That, in the end, is the gift he left.