The Operator Who Trains the Next Operator: Capturing Know-How Before It Walks Out


Every plant has one. The operator everyone walks over to when the line acts up, the job runs hot, or the new hire is stuck. They don't just run the machine — they carry the judgment calls, the workarounds, and the "don't do it that way" lessons that never made it into a manual.

The problem isn't that this operator will leave someday. It's that when they do, the knowledge leaves with them — unless the handoff itself is a system, not a farewell lunch and a week of shadowing.

Listen to this post:

Why shadowing isn't a handoff

Shadowing feels thorough, but it transfers habits, not judgment. The new operator watches what the veteran does, not why. The veteran can't narrate thirty years of decisions in two weeks, and once they're gone, there's no record to check when the odd case comes back.

A real handoff leaves something behind that the next operator — and the one after that — can actually use.

Three places in Plex where know-how can live

1. The checklist at the point of work. When the steps for a job live as a checklist where the work happens, the next operator follows the same steps, in the same order, and the completed record proves it. The veteran's sequence stops being memory and becomes the standard. When reality differs from the checklist, fix the checklist — that's the handoff getting better, not worse.

2. The bulletin where the work happens. When a veteran finds a better way — a different sequence, a warning about a finicky setup, a check that catches a defect early — that discovery needs to become the posted way, not hallway lore. A bulletin at the workcenter puts the change in front of every shift at once, instead of letting it spread one conversation at a time (or not at all).

3. One approved version in document control. Binders on a shelf and folders on a shared drive all go stale the same way: nobody knows which copy is current. Keeping the approved procedure in one controlled place means the next operator never has to ask which version to trust — and an auditor never has to take someone's word for it.

None of this replaces the veteran. It multiplies them: their judgment keeps working the night shift, the weekend shift, and the shift after they've retired.

A handoff routine you can start this week

You don't need a retirement date to start. Pick the jobs only one person knows how to run — every plant has a few — and run this routine:

  1. List the single-point-of-failure jobs. If only one operator can run it, it goes on the list.
  2. Walk the job once, checklist in hand. The veteran does the job; someone else writes down what actually happens, step by step.
  3. Fix the checklist where reality differs. Every gap between the written steps and the real job is knowledge that was living only in someone's head.
  4. File it in the controlled place. The finished checklist and procedure become the approved version — and name a "next operator" owner to keep it current.

Do one job a week and the list shrinks fast. The point isn't paperwork; it's that the next operator starts from the veteran's finished thinking instead of from zero.

What changes when the handoff is a system

New hires ramp on the system, not on one person's availability. Night shift runs the same way day shift does. Quality issues get traced to a step, not to a memory. And the veteran's value stops being "the only person who knows" and becomes "the person who taught the plant."

That's the deeper point behind Rescuing Tribal Knowledge: connected workers matter, but the connection that lasts is the one written into the system. The operator who trains the next operator doesn't give their value away. They make it permanent.

Popular posts from this blog

Your Tool Crib Is Telling You Something: Cycle Counts as an Early Warning

Image
A year ago, I wrote about setting up cycle counting for supply items in the Plex ERP tool crib . We covered why counting a little throughout the year works better than doing one large annual count, how to set up counts in Plex, and the basics of ABC classification and assigning ownership. That post focused on how to count . This one is about what the count results can teach you. Listen to this post When the Counts Start Drifting You set up the cycle types, define the parameters, and get Plex Mobile scanning. Counts happen on schedule—and then the same variances keep appearing. A few carbide inserts are short. A drill index is over. The differences aren’t huge, but they keep coming back. The first instinct may be to count more often. But if the same items repeatedly drift in the same direction, counting more frequently probably won’t fix the cau...
Read more

Ticket Triage for Plex ERP: How Small BA Teams Decide What Gets Fixed First

Image
It is 7:40 am on a Monday morning and your inbox already has four Plex problems in it. A supervisor at one plant cannot print labels. An accountant at another company cannot close last month's books. Somebody - you are not sure who - reports that "Plex is slow." And a text message from a plant manager says a workcenter stopped recording production two hours ago. Four tickets. One of you. Which one do you touch first? If your answer is "whichever one I saw first" or "whoever is loudest," you do not have a support process - you have a reaction process. The fix is an old idea borrowed from emergency medicine: triage . This article covers what ticket triage is, why it pays for itself in a Plex ERP environment, the five-step pass I recommend for every incoming ticket, and the specific challenges that hit small Plex business analysts who support more than one company, in more than one location, at the same time. Listen to the podcast version of this post:...
Read more

Cybersecurity Awareness Month 2026: Don’t Make It Easy for Them

Image
  Every October, individuals, businesses, and government agencies come together for Cybersecurity Awareness Month —a global campaign initiated by the Cybersecurity and Infrastructure Security Agency (CISA) and the National Cybersecurity Alliance (NCA). The goal is simple yet critical: empower everyone to take control of their digital safety. Under the rallying theme "Secure Our World: Don’t Make It Easy for Them," this year focuses on closing the small gaps that threat actors routinely exploit. Key Steps to Take This Year Cybercriminals rarely breach systems through complex science fiction methods; most rely on predictable habits, weak passwords, and unpatched software. By covering the basic fundamentals, you eliminate the easiest paths of attack. 1. Enable Multi-Factor Authentication (MFA) According to CISA, enabling Multi-Factor Authentication makes you significantly less likely to be hacked. Even if a cybercriminal steals your password, MFA creates an additional wall—such...
Read more