Saving know-how before it retires, one voice note at a time

Picture a maintenance lead, say Frank, with thirty years on the same floor. He retires next spring. Everyone knows he's good. Few know exactly what he knows, because almost none of it is written down.

Think about what walks out the door with him. Which valve gets closed first when the old boiler comes down, and why the order matters on that unit. The warm-up the big lathe needs on a cold Monday before it holds tolerance. The faint whine that means a bearing on the conveyor drive is going, a week before it fails.

None of that is in the manual. It lives in Frank's head, and he has a few months left. This post is about getting it out in his own words, without turning him into a writer.

Why the know-how is at risk

The Bureau of Labor Statistics projects about 30,400 openings a year for machinists and tool and die makers (opens in a new tab) from 2025 to 2035. It expects all of those openings to come from replacing workers who move to other occupations or leave the labor force, such as to retire.

The people who keep the machines running are in a similar spot. Over the same decade, BLS projects about 51,900 openings a year for industrial machinery mechanics, maintenance workers and millwrights (opens in a new tab) and about 40,600 a year for heating, air conditioning and refrigeration mechanics and installers (opens in a new tab). For both, it expects many of those openings to come from replacing workers who change occupations or leave the labor force, such as to retire.

Across all of US manufacturing, a 2024 talent study by Deloitte and The Manufacturing Institute (opens in a new tab) estimated that the net need for new employees could be around 3.8 million between 2024 and 2033. It said around half of those jobs, 1.9 million, could go unfilled if manufacturers can't address the skills gap and the applicant gap.

A new hire can fill the job. What they can't fill on day one is the tacit part: the how and the why that never made it into the manual. That's the part that leaves with the person.

Why it rarely gets written down

Everyone agrees this stuff should be written down. It rarely is.

Writing is slow. A good write-up of one fix can take an hour, and it feels like a second job on top of the real one. Manuals and binders are out of date before they're printed, so nobody trusts them, so nobody updates them. And the people who know the most often like writing the least. They became experts by doing the work, not by writing about it.

The problem isn't intention. It's friction. If saving what you know means an hour at a desk, it won't happen on a busy week, and every week is busy.

Why talking works better

Experienced people already explain things out loud every day, to apprentices, new hires and customers. The trick is to catch that explanation once instead of letting it disappear.

It's how people already explain things

"Let me tell you how I really troubleshoot this pump" is an easy sentence to say. "Write detailed troubleshooting procedures for all pump failures" is a hard assignment to start. Talking lets people share what they know the way they already share it, with the emphasis, the asides and the "here's the thing nobody tells you" that make it stick.

The context comes with it

When people talk, they say why. Picture Frank at the lathe on a cold morning, phone in hand: "Run the warm-up program for twenty minutes before you cut anything. The spindle grows as it warms up. If you measure the first part cold and chase the offset, you'll be chasing it all morning. Warm it up, then measure."

The same goes for the old boiler. Frank can stand next to it and walk through the shutdown, following the lockout/tagout procedure: which valve gets closed first, why that order matters on this unit and where each lock goes. The written procedure lists the steps. His note explains them, and that context comes along for free when someone talks.

Anyone can do it

Some of your best techs hate writing. They'd rather fix three machines than write up one. Talking removes that barrier. A tech can stand at the machine, take out a phone and talk for a minute or two about what just happened. No typing, no form, no desk.

It also means the know-how doesn't only come from people who like paperwork. The second-shift operator who quietly figured out the jam on line 2 can share it as easily as the plant engineer.

What a good voice note covers

A voice note doesn't need a script, but a loose order helps. Before you hit record, think through five things:

1. Name the machine or the place, so the note can be found later.
2. Say what you saw: the noise, the reading, the fault code, the leak.
3. Say what you checked, including what turned out fine.
4. Say what fixed it, and the part or tool you used.
5. Say why it worked, or what to watch for next time.

That's a minute or two of talk. It doesn't need to be polished. A note with a few "ums" in it is far more useful than the perfect write-up nobody gets around to.

Start small, then make it a habit

You don't need a big program. You need a few people, a few problems and a few weeks.

Pilot (first month)

Pick two or three people who are close to retirement. With each of them, list the three to five problems that keep coming up: the jam that happens every winter, the unit that trips on hot days, the customer site with the tricky access. Ask them to record one note per problem, at the machine or on the site.

Then have a newer person listen to each note and say what was unclear. That one round of questions often brings out the best detail.

Spread (months 2-3)

Bring in more crews. Keep the ask simple: one note at the end of a job that taught you something, and one after every breakdown. A rough note today beats a perfect one never.

Habit (after that)

After a few months, it should feel like part of the job, like cleaning up the bay. New hires learn to listen to the notes on a machine before they ask, and to ask when the notes don't cover it. When they do ask, the answer gets recorded too.

The human side

Recording is the easy part. The hard part is how people feel about sharing what they know.

Credit the people who share, by name. When a note saves a breakdown, say so at the morning meeting, and say whose note it was. Being the person who knows is part of how experienced people see themselves. Make sharing it something they're recognized for, not something that makes them feel replaceable.

Make it safe to say what really works. Sometimes a note shows that the real way differs from the written procedure. Don't treat that as a confession. Thank the person, then take it to whoever owns the procedure so it gets reviewed and fixed. Nobody should have to work around a procedure, and nobody should be punished for pointing out that it's wrong.

Keep it imperfect rather than never. Frank will stumble, repeat himself and forget a step on his first few notes. That's fine. Someone can ask a follow-up, and he can record it again. What you can't do is ask him next year, after he's gone.

Start this week. Pick one person and one problem, and ask for a minute or two at the machine. Spring comes sooner than you think.