Capturing a Lesson So It Outlives the Person Who Learned It

Why this matters

Every shop is one resignation away from relearning things it already paid for. The lead tech who knows which supplier actually delivers on time, the office manager who knows the one billing quirk that trips up every new hire, the installer who figured out the sequence that stops a callback - when they leave, that knowledge walks out with them, and the shop pays the tuition a second time. The lesson lived in a head, and heads leave. Capturing a lesson means moving it out of one person's memory and into something the business keeps. This is how you stop buying the same lesson twice.

The problem: most of what a shop knows is invisible

Knowledge in a trade comes in two forms. Explicit knowledge is anything already written down: the manual, the checklist, the spec. Tacit knowledge is what lives only in experience - the feel for when a customer is about to cancel, the trick that makes a stubborn job go smooth, the judgment for when a reading is close enough. Tacit knowledge is the good stuff, and it is exactly the stuff that evaporates.

The danger is that tacit knowledge does not feel like it needs capturing, because the person who has it does not experience it as a lesson. It feels like just knowing. That is why it survives only as long as the knower does, and why turnover quietly resets a shop to its own past.

The test: would this survive you being gone

Run a simple check on any hard-won lesson: if the person who holds it did not show up tomorrow, would the shop still have it? If the honest answer is no, you have a capture job to do. A few common places lessons hide:

• In one tech's routine ("he always checks that first, we don't know why").
• In a relationship (the supplier rep who does you favors nobody else can get).
• In a workaround (the manual step someone does to dodge a known problem, undocumented).
• In a scar (the expensive mistake that made someone cautious, but only that someone).

Anything that would leave with a person is a lesson that is not yet captured, only borrowed.

Turn the tacit into something explicit

Capturing is the act of pulling the lesson out of the head and into a form the shop holds. The move is almost always the same: get the person to explain not just what they do but why, then write the why down where the work happens.

• Interview the knowledge before it leaves. Ask your experienced people to walk through the tricky parts of their work out loud. "Why do you do it that way?" surfaces tacit rules they never knew they had.
• Write the reason, not just the step. "Check the shutoff first" is a step. "Check the shutoff first because on this style it fails closed and you will chase a phantom fault for an hour" is a captured lesson. The reason is what makes it stick and what stops someone from deleting it later.
• Attach it to the work, not to a binder. A lesson belongs in the checklist, the job template, or the record it applies to, so the next person meets it at the moment they need it, without knowing to go looking.

Choose a format that actually survives

Not every lesson wants the same container. Match the form to the lesson so it lands and stays.

• A single fact or rule: one line in the relevant record or a short entry in a shared reference.
• A repeatable method: a checklist step or a short procedure, so it changes how the work is done rather than sitting as trivia.
• A judgment or a feel: harder, but capturable as a worked example or a short "here is a case and how to read it" note, plus deliberate hands-on teaching. Some tacit skill only transfers by a senior person coaching a junior one, so build that time in on purpose.

The format bar is low: findable, attached to the work, and stating the reason. A perfect document nobody can find loses to a rough note in the right place.

Keep the captured knowledge alive

Capture is not a one-time archiving project. A lesson written once and never revisited rots as the work changes.

• Review it when the work changes. New equipment, new process, new supplier means old lessons need a check.
• Let people correct it. The crew closest to the work will spot when a captured lesson has gone stale. Make fixing it easy and expected.
• Fold it into onboarding. The fastest test of whether a lesson is truly captured is whether a new hire can pick it up without a veteran in the room. If onboarding still depends on one person's memory, the capture is not done.

The mental model to keep: a lesson in a person's head is a rental, and people move out. A lesson captured in the work is something you own. Build the shop so that what it knows does not depend on who happens to be standing there.

References

• Trade-standard practice for knowledge management and standard operating procedures
• U.S. Small Business Administration (SBA), documenting processes and reducing key-person risk
• See related: After-Action Review: Learning From a Bad Job; Document This Fix or Just Tell the Crew (decision tree)
• See related: The Checklist That Grows Every Time Something Goes Wrong