Your best people are retiring and taking the tribal knowledge with them.
A technician orders a timing kit for a 2019 Explorer from his phone, between jobs. He has done that job plenty of times.
Tuesday morning, engine apart, and the parts in the box aren’t the ones on this engine. Ford made a running change, and the two versions don’t interchange. The only way to tell them apart is a mark on the cover, which he could not have seen on Monday, because on Monday the cover was still on the engine.
Right kit arrives that afternoon. Now that he can see in there, the water pump is weeping. On that engine the pump sits behind the timing cover, driven off the chain, so replacing it later means doing this entire job a second time. He quoted the job on Friday, without a pump in it.
The supplier sells a kit with the pump already in it. One line down in the same catalog. It never crossed his mind on Monday, because on Monday nothing in front of him raised the question.
He would have asked Marty. Marty retired in March, after thirty-one years.
Here is the part worth sitting with. Every one of those answers already existed. The manufacturer published a bulletin about the mid-year change. Their tech line had been explaining that water pump for years. The better kit was in the catalog the whole time.
None of it could reach a 26-year-old with an engine apart on a Tuesday morning.
I used a truck technician as an example. You already know your own version. The nurse who cannot find the current protocol. The adjuster who does not know the state rule changed in April. The new rep who quotes a term your legal team retired two years ago. Same shape every time. The answer exists. It cannot reach the person who needs it.
Tribal knowledge isn’t a mystery. It’s a phone number.
Tribal knowledge is the accumulated, unwritten know-how living in the heads of your most experienced people: which part supersedes which, why the exception exists, what the customer actually means when they call. Losing it is not a documentation problem. It is a delivery problem. The answers mostly still exist. Nothing gets them to the person who needs them at the moment they need them.
We talk about tribal knowledge like it’s something mystical living in a few veterans’ heads.
It’s not that romantic.
Call it tribal knowledge or institutional knowledge. It’s ten thousand small answers living in the heads of your veterans, your senior field people, and a few thousand Martys scattered across everyone who touches your business. Nobody ever needed to write them down while those people were reachable. You just called.
That works right up until the day you can’t. And the day is arriving and on schedule: the ISM manufacturing employment index moved into expansion in July for the first time in 33 months, with 481,000 manufacturing jobs open in the June JOLTS release. More new people are asking. Fewer veterans are answering.
Everybody lands on the same answer. Document it before they go.
You have already documented it. That was never the problem.
They start the same way. Interviews, a template, momentum for a month. Then it stalls, and everyone decides the lesson is that they should have started sooner.
I don’t think that’s the lesson. Most companies already have the binder.
Go look. You published the bulletin. There are fifteen years of support tickets, training decks from three product generations ago, and guides on your website. Somebody wrote up the hard case after the third call about it. Nobody dropped the ball. The information exists.
Documentation was never the bottleneck. The bottleneck is that the answer never reaches the person at the moment they need it, in a form they can actually use.
Marty was never the documentation. Marty was how the answer got delivered. You brought him half a question, he asked two back, and gave you the answer in the shape you needed it. That’s what left in March. The knowledge is mostly still there. The way to reach it is gone.
Capturing it is the easy half. Delivering it is the job.
If you buy that, the work changes shape, and it gets a great deal smaller.
Don’t sit a veteran down and ask him to write out what he knows. He can’t, he’ll hate it, and you’ll get a document nobody opens. People cannot write down what they know. But they can answer a question.
How to capture tribal knowledge before someone retires
So, start with the questions, and let your own history hand them to you. Pull twelve months of support tickets, warranty claims and returns, and cluster them. In most organizations you’ll find thirty or forty questions that account for most of the volume, and the repeats are your map. Then put a veteran in a room and ask him those forty out loud, one at a time. That’s two afternoons with a defined end, not a two-year initiative.
When you’re done, don’t declare victory because the binder got thicker. Run it through what I think of as the four delivery questions.
Can they find it? Someone three states away, under time pressure, in under a minute, without knowing the file name or that the document exists.
Does it come back in the form each person needs? A three-week hire, a twenty-year veteran, a partner, and a customer need four different answers to the same question. Marty knew that without thinking about it. Your website doesn’t.
Can they trust it, and can you? Can they see where the answer came from, and can you tell afterward what was said and whether it was current? That question gets sharper, not easier, the moment you point an AI tool at the binder. Kiteworks’ 2026 survey found half of organizations can’t produce a complete record of what their AI accessed within one business day.
Does it get better every time someone asks? Marty’s answers did. Every call taught him something about what confuses people.
Most support sites and wikis fail all four.
The question I keep coming back to
None of this is really about technology. It’s about a good person, far from your building, under pressure, stuck on something your organization answered years ago.
For what it’s worth, this is the problem we spend our days on at AnswerMyQ. But I’m more curious about your organization than mine.
Every company has a Marty, the one person everybody calls. What actually happens the day he doesn’t pick up?
