Every organization I've worked with has a Steve. Steve knows which customer needs a call before the invoice goes out. He knows why the old machine gets restarted on Tuesdays. Nobody wrote any of it down, because Steve was always there.

Then Steve retires, or takes another job, or gets sick for a month. The work doesn't stop, but it gets slower and more expensive, and people start making the same mistakes Steve learned to avoid years ago.

That's tribal knowledge. It isn't a character flaw. It's what happens when capable people solve problems faster than anyone can document them. The trouble is that it lives in one head, and heads leave.

How to tell if you have the problem

Ask a few plain questions. If one person were gone for six weeks, what would break? Who do people go to when the written process doesn't match reality? Which tasks only get done right when a certain person is in the building?

If the same two or three names keep coming up, you've found where the knowledge is stored.

What to do about it

The instinct is to schedule a big documentation project. Those usually stall. The binder gets written, nobody opens it, and it's out of date by spring.

What works better is smaller and more practical:

  • Start with what breaks most. Pick the two or three tasks that cause the most trouble when the expert is out, and capture those first.
  • Interview, don't assign. Experts are usually too busy to write it all down. Sit with them, ask them to walk through the work, and write it up yourself.
  • Capture the why, not only the steps. A checklist tells someone what to do. The reasons behind it help them handle the case the checklist didn't cover.
  • Have someone else run it. The test of a good process is whether a capable person who has never done it can follow it. Watch where they get stuck and fix that spot.
  • Put it where the work happens. A procedure nobody can find in the moment might as well not exist.

None of this is glamorous. But the goal is simple: turn what a few people know into something the whole organization can use. Steve will appreciate it too. He'd probably like to take a vacation without his phone ringing.