Why experienced people keep know-how to themselves, and what crew leads can do

Picture a machinist, say Joe, who could fix anything in the shop. He knew which lathe ran warm after lunch, which fixture needed a shim, and what the old mill sounded like right before a tool let go. Nobody wrote any of it down, because Joe was always there.

Then Joe retired. Nothing broke on his last day. It happened over the next few months. Jobs took longer. Old mistakes came back. People stood around a machine asking each other, "How did Joe do this?"

Here's the thing about people like Joe. Usually they aren't hiding anything on purpose. Nobody asked them in a way that fit their day, and nothing about the job rewarded them for sharing. A crew lead can change both.

Four honest reasons people keep it to themselves

Being the one who knows feels like job security

If you're the only one who can set up the big customer's parts, or who knows which bearing the old pump really takes, you matter. People come to you. Sharing that can feel like giving away the reason they keep you around.

It's rarely said out loud, but it's real. It gets stronger after layoffs, or when someone close to retirement worries about being pushed out early.

Nobody gets credit for sharing

Fixing the breakdown gets noticed. Showing three other people how to fix it next time usually doesn't. In a lot of shops, the hero who saves the night gets the thanks. The person who made sure nobody needs a hero gets nothing.

People do what gets noticed. If sharing earns nothing, it won't happen much.

There's no time

Experienced people are the busiest people on the crew. They get pulled from job to job, and everyone interrupts them with questions. Writing up a procedure after a ten-hour shift is not going to happen.

If sharing means a form, a meeting or a document, it loses to the next job every time.

Nobody wants to be wrong in front of the crew

Sharing what you know puts it where others can pick it apart. What if a younger tech spots a mistake? What if your way turns out to be out of date?

For someone whose standing comes from being right, that's a real risk. It's easier to keep it in your head, where nobody can check it.

What a crew lead can do

You can't order people to share. You can make it easy, make it count and make it safe.

Make sharing take one minute

Keep the ask small. Talk for a minute or two at the machine, on a phone, right after the job. No forms, no templates, no writing.

Three questions are enough: what was wrong, what did you check, and what fixed it? The easier it is, the more often it happens.

Credit people by name

At the shift meeting, say who shared what and how it helped. "Dave's note on which filters the old compressor takes saved the night crew a trip to the supply house." Say it in front of the crew, not in a private message.

Credit costs nothing, and it answers the job-security worry head on. The person who shares becomes known as the expert. They don't become less needed.

Go first

Before you ask anyone else, record your own know-how. Pick something you get asked about all the time and talk it through.

When the crew sees the lead do it, and sees it took a minute, the ask feels fair. It also shows them that a rough, spoken note is fine. Nobody expects a polished manual.

Check and thank, don't criticize

Some notes will be wrong or out of date. How you handle the first one decides whether you get a second. Fix it with the person, thank them for sharing, and move on. A wrong note gets fixed, not punished.

This isn't just being nice. When Google's researchers studied what made its own teams effective, they identified five key dynamics and put psychological safety first, in order of importance (opens in a new tab). The same page describes teammates who "feel confident that no one on the team will embarrass or punish anyone else for admitting a mistake, asking a question, or offering a new idea."

That's the crew you want. People share more when they know a mistake won't be held against them.

Make it part of the routine

Sharing that depends on someone remembering won't last. Tie it to moments that already happen:

• At the end of a job, especially a tricky one
• After a breakdown, once the machine is running again
• At the shift handoff, when the next crew needs to know what changed

Same moment, same small ask, every time. After a few weeks, nobody needs a reminder.

When you hear the objections

"I don't have time"

Fair. That's why the ask is a minute or two, not a write-up. Record it right after the job, while it's fresh.

It also saves time for the person who knows the most. One short note can replace answering the same question again and again for the next year.

"What I know isn't special"

It feels that way because you've done it so many times. To someone in their first month, the way you listen to a pump before you touch it, or the valve you always check first, is exactly what's missing from the manual.

Ask them what new people keep asking them about. That's the special part.

"I'll do it when it's perfect"

A rough note recorded today is worth more than a perfect one that never gets made.

If something is off, it can be checked and fixed later. The notes on a machine get better as more people add their own.

A 30-day starter plan

Week 1

Go first. Record two or three notes of your own on the things you get asked about most.

Then ask the crew one question: "What do people ask you about over and over?" Write down the answers. That's your list of notes to get made.

Week 2

Ask for one note per person, at the end of a job. Keep it to a minute or two, on the phone, at the machine or in the truck.

Don't judge the first ones. Just get them made.

Week 3

Credit the first notes by name at the shift meeting, and say how each one helped.

If a note is wrong or out of date, fix it kindly with the person who made it, and thank them. The crew is watching how you handle that one.

Week 4

Add "after a breakdown" to the routine. Then look back. Which notes got used? Who hasn't shared yet, and what's stopping them?

Pick the next step. It might be the shift handoff, a new machine, or the person who retires next year. For that last one, see saving know-how before it retires.

None of this needs a big program. It needs a crew lead who keeps sharing small, gives credit out loud and treats a wrong note as something to fix. Do that for a month, and the next Joe's know-how stays in the shop when he leaves.