Private preview. Not launched, not indexed. No analytics, no cookies, and nothing you enter is sent anywhere.
For teams: Does your AI need the cloud?
Run It Local
Protocols / P-04
P-04

Capture tribal knowledge once

Record the people who know how things work explaining it once, then turn it into written steps.

Fixes
Tribal knowledge
How much lives only in people's heads.
Time
An hour per process, spread over a few weeks
Part-time, alongside normal work.
Difficulty
Easy
Honest estimate for a 50–500 person company.

IndicationsUse this when

  • Key processes live in a few people's heads.
  • Someone important is leaving or overloaded.

ContraindicationsDon’t, or be careful, when

  • Get consent before recording, and follow your state's recording rules.
  • Avoid recording screens that show customer or employee personal data.

EquipmentWhat you need

  • Any screen or audio recorder
  • A local transcription tool such as whisper.cpp, so recordings stay on your machine
  • Optional: a local model to draft steps from the transcript

ProcedureSteps

  1. List the five processes that would hurt most if their expert left.
  2. Have each expert walk through one process out loud for 15 to 30 minutes, recorded.
  3. Transcribe the recording on your own machine.
  4. Turn the transcript into numbered steps (by hand or with a local model).
  5. The expert corrects the draft. File it in the source of truth with an owner.

ChecksHow you know it worked

  • Five processes are written down and checked by their experts.
  • A second person can follow each one.

HandoffWho owns it next

Each expert owns their process document (P-02).