It’s 7:40 on a Monday morning, and a 2019 F-150 is booked in for a timing job.
The technician is 26, three years in the trade, good hands. He has done this job on this engine plenty of times. So, he does what any competent technician does when the shop is full, and the customer wants it back Wednesday. Between jobs he pulls up the supplier’s site on his phone, finds the kit he has used before, and puts it on the afternoon delivery run.
Tuesday, 9:15. Engine apart, cover off, and the chain in that box is the wrong pitch.
There was a mid-year production change. Two kits, same year, same engine, and the only way to tell which one this truck takes is a casting number on the front cover. Which he could not have read on Monday, because on Monday the cover was still bolted to the truck.
Notice who never got a phone call. The parts counter. Their catalog would have caught this. Millions of SKUs cataloged down to the sub-model and the mid-year change. It just needs you to know that a mid-year change exists, and to know you should ask.
He didn’t know what he didn’t know. That isn’t a training problem. That is what experience looks like, right up until the day the exception shows up.
So: a lost day, a wasted delivery run, and a truck on the lift that isn’t going anywhere.
Tuesday afternoon. Right kit finally on the bench. And the day gets worse.
The kit calls for a holding tool he doesn’t own, and he finds that out with the cover already off.
And now that he can see in there, the water pump is weeping. On this engine it runs off the timing drive. He quoted this job on Friday. At a number with no water pump in it.
And here is the part that should sting if you make this kit. You sell one with the pump already in it. Same brand, same box, one line down in your own catalog. He has run your kits for years, and it never crossed his mind on Monday, because on Monday nothing in front of him raised the question.
Look at what that actually costs you because it is not the delivery run. It is the attach rate on the higher-content kit. The one with the better margin, the one your product team built precisely because the pump usually goes with the chain. Every job like this one is a unit of the small kit sold where the big kit was the right answer, and the difference is pure mix. Most suppliers can pull that ratio in an afternoon. Almost no one had ever looked at it as a knowledge problem instead of a merchandising one.
Meanwhile he needs three more answers, right now, with the truck apart and a customer expecting a call. Which tool? Whether the pump is a do-it-now on this engine, and whether he can even get one today. And whether there is anything else about this build he should know before he closes it up.
He would ask Marty. Except Marty retired in March, after thirty-one years.
He calls the tech line. Hold, then a callback tomorrow.
So, he does what everyone does. He guesses, or he watches a video made by a stranger, or he asks the AI on his phone, which has never read your installation bulletin and answers anyway. Then he makes an awkward call to the customer.
Here is the part worth sitting with. Every one of those answers exists. You published a bulletin about the mid-year change. You published another about the holding tool. Your tech line has been explaining that water pump for six years. And the kit with the pump already in it has been in the catalog the whole time. Somebody wrote all of it down.
None of it could reach a 26-year-old with an engine apart on a Tuesday morning.
Those were your two days too. Your kit is in the car. Your name is on the box. A delivery truck went out twice. And the kit you actually wanted him to buy is still sitting in your catalog.
Your catalog answers the question it gets asked. Nobody owns the rest.
This industry solved fitment. It took decades and it is genuinely impressive. Ask which part, and you get an answer that holds up.
But look at what happened on Monday. The catalog was not wrong. It was never asked. And it could not have been, because the question required a number that was still bolted to the truck.
That is the first gap: a system that answers well but only answers the question you already knew to bring it. The person who needs it most is the one least likely to know there was a question.
Then there are four more that nobody owns at all.
What will I need? Special tools, holding fixtures, the consumable that isn’t in the box.
What will I find? The parts that always fail alongside this one, on this engine, at this mileage. The while-you’re-in-there.
How does it go in? Sequence, torque, what to do when the marks don’t line up, the break-in step people skip.
What do I tell the customer before I open it up? That is the one that costs a shop money and costs you goodwill, because by the time he knows, he has already quoted the job.
Now notice that those are not service questions. They are sales questions in work clothes. A technician who knows on Monday that the pump usually goes with the chain buys the bigger kit, quotes the job right, and never has to make the awkward call. The one who finds out on Tuesday buys the smaller kit, eats the difference, and remembers which brand put him there. Same truck, same technician, same catalog. The only variable is whether anybody answered a question he did not know to ask.
Tribal knowledge isn’t a mystery. It’s a phone number.
We talk about tribal knowledge like it’s something mystical living in a few veterans’ heads.
It’s not that romantic. It’s which of two look-alike kits fits the early build. It’s the install step your best field rep demonstrates in person because it never quite made it onto the sheet. It’s knowing that on this engine you sell the customer the pump on Friday, not on Tuesday with the truck apart.
Call it tribal knowledge or institutional knowledge. It’s ten thousand small answers about your product, living in the heads of your tech line veterans, your senior field reps, and a few thousand Martys scattered across the shops that install what you make. 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.
The people asking are new. The people who know are leaving.
The TechForce Foundation projects 971,000 auto, diesel, collision, and aviation technicians needed between 2024 and 2028, a figure it raised by nearly 20 percent over the prior year. The more telling number is the mix: replacement openings outrun growth openings by roughly four to one.
Four out of five of those seats exist because somebody left, not because the industry grew. That is the whole problem in a ratio. The bays are filling with three-week people, and the questions they can’t answer roll uphill to you.
Now look down your own hallway. Your best tech line guy is 61. The field rep who can install your product blindfolded has mentioned retirement twice.
Everybody lands on the same answer. Document it before they go.
You have already documented it. That was never the problem.
I believed that too, and I’ve watched enough of those projects to change my mind.
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 tech line logs, training decks from three product managers ago, install guides on your site. Somebody wrote up the water pump after the third call about it. Nobody dropped the ball, not your people and not the catalog people who keep millions of parts close to right. The information exists.
Documentation was never the bottleneck. The bottleneck is that the answer never reaches the person in the bay 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. It also 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. They can answer a question.
So, start with the questions, and let your own history hand them to you. Pull twelve months of tech line calls, warranty claims and returns, and cluster them. In most product lines you’ll find thirty or forty questions 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. Ask four harder questions.
Can they find it? A technician three states away, truck apart, in under a minute, without knowing the file name or whether the document exists.
Does it come back in the form each person needs? A three-week technician, a twenty-year master, a counter pro, and your own field rep 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 about your product and whether it was current? That question gets sharper, not easier, the moment you point an AI tool at the binder and let it answer for your brand.
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 portals fail all four. The suppliers who fix it will be the ones whose parts go in right whether or not the right veteran picks up the phone.
The question worth asking
None of this is really about technology. It’s about a good young technician, three states from your building, with a truck apart and a customer waiting, stuck on something your company answered years ago.
Every product has a Marty, the one person the whole channel calls. What actually happens the day he doesn’t pick up?
