SimplBrain
Capture tribal knowledge without turning one person's habits into company policy
SimplSolutions editorial team · 3 min read
Published
Ask about a recent ordinary case
An experienced employee asked to document everything usually produces either a huge narrative or a list of obvious steps. Choose one recurring situation they handled last week. Ask what arrived, which fact changed the next action, which source they checked and how they knew the receiving person could finish.
Keep customer and employee details out of the first interview unless their use and handling are explicitly approved. A redacted or synthetic example can preserve the reasoning pattern without spreading confidential records.
Distinguish the rule from the shortcut
Use four prompts: what is the approved procedure, what do you do when it fits, what cues tell you it does not fit and who can decide the exception? Experienced staff often describe a local workaround as part of the normal process. That does not make the workaround authorized for everybody.
Record personal practice as a candidate for review. If a shortcut is valuable, the process owner can decide whether to revise the procedure. If it is unsuitable, retain it only as an identified pitfall in the permitted context. Do not publish it as the preferred answer simply because it came from the most experienced person.
Create a situation card instead of a transcript archive
| Part | What the reviewer needs |
|---|---|
| Situation | The recurring trigger in plain language |
| Critical cues | Facts that change the next step |
| Approved response | The governing procedure and applicable version |
| Exception | What must not be guessed |
| Recipient | The person who accepts the handoff |
| Review | Who approved this card and when it must be retested |
A card is easier to verify than an hour-long transcript. Keep the interview source only under the agreed retention and access rules. More raw material is not necessarily better knowledge.
Test the novice's question
Have someone less familiar with the task ask a natural question using the card. Can they identify the applicable source and complete the next step? Ask them to explain the exception route as well. If they still need the expert to translate the card, revise the guidance rather than concluding that the novice is deficient.
Then alter one important fact. For a receiving process, make the shipment incomplete. The explanation should move to the approved exception route, not continue through the normal steps. This tests whether the captured guidance includes judgment boundaries instead of only a happy-path checklist.
Give the source a continuing owner
The departing expert cannot remain the permanent repair destination. Name a process owner and alternate who can accept source changes. Record which parts of the guidance need periodic review and which events trigger an earlier check.
Avoid promising to reproduce a person's entire judgment. Expertise can include tacit cues and situation-specific experience that a short document does not capture. Start with the repeatable portion, and leave unusual cases with qualified people.
Judge transfer by accepted work
Count repeat explanations, clarification rounds, accepted handoffs and corrections. Include the expert's capture time and the owner's review time. A large document count is not proof that the business can now operate without the expert.
Inspect the tribal-knowledge use case and prepare one reviewed situation card. Request a relevant demo to explore how SimplBrain can explain approved guidance and route the unresolved question. The card's authority and maintenance matter as much as the answer interface.
