Jim retired in March. Twenty-eight years on the maintenance side of a marine fabrication yard. The retirement party was Friday afternoon. By Monday morning, the plant had a maintenance crew that looked, on paper, exactly the same size it had been the week before.
The plant manager I was working with told me, in the first week of April, that he thought the transition was going smoothly.
By July, he was in my office asking me what was happening to his numbers.
His unplanned downtime was up. His preventive maintenance compliance was slipping. He had three repeat failures on the same equipment in two months — the kind of repeat failures that, when Jim was around, never happened twice because Jim caught the root cause the first time. The new lead was technically capable. The new lead was not Jim.
This is the 18-month gap. It is the most expensive part of a senior technician retiring, and it is the part that almost never makes it onto the P&L as a single line item, because the cost is structurally diffused across four other line items where it gets blamed on something else.
Where the cost actually hides
When a Jim retires, the cost shows up in four places. None of them are labeled “knowledge loss.”
The first place is scrap and rework. The new technician makes good-faith decisions that the experienced technician would have caught. The decisions are not wrong on paper. They are wrong on this specific equipment, this specific shift, this specific upstream condition. The scrap number ticks up. The QA team writes it up as a quality issue. The root cause investigation produces a procedural finding. Nobody traces it back to the missing 28 years.
The second place is unplanned downtime. The same equipment that ran for years without major event starts producing minor events. Each one is small. None is a crisis. But the cumulative hours add up across a quarter, and the maintenance budget overruns in a way that is easy to attribute to “aging equipment” or “supply chain issues with parts.”
The third place is overtime. The remaining experienced technicians get pulled in to cover. They work weekends. They miss their own preventive work to fix what the new person didn’t catch. The overtime hits the labor line, and at the end of the quarter someone says “we need to look at scheduling.”
The fourth place is onboarding and training spend. The new person needs more training. The training program runs longer. The internal trainers are pulled away from their own jobs to provide it. None of this is wrong. All of it is the structural cost of replacing 28 years of tacit knowledge with a job description.
The Association of Equipment Manufacturers (AEM) estimates the average cost to a single company of failed knowledge transfer at $47 million per year, including time wasted, missed opportunities, frustration, and delayed projects. That number sounds high until you start adding up your scrap, your unplanned downtime, your overtime, and your training cost across an 18-month transition window. Then it sounds conservative.
Why 18 months, specifically
The 18-month figure is not arbitrary. It is the average window industry research consistently reports for a replacement to reach equivalent productivity in complex maintenance and operations roles. New hire ramp times in manufacturing have stretched from 3–4 months a decade ago to 8–12 months today, and for senior technical roles the curve extends well beyond a year before the new person is performing at the level of the person they replaced.
In the meantime, the gap is real. MIT Sloan research on learning curves in complex work has documented productivity differentials between high- and low-performing employees in high-complexity jobs as high as 800%. That number gets smaller as the new person climbs the curve. But it does not get smaller quickly.
This is also why the conventional “succession planning” answer falls short. Succession planning assumes you can hand the role off. The 18-month gap exists because the role cannot actually be handed off — only the title can. The role itself is a body of accumulated decisions, near-misses, and corrective instincts that are not written down anywhere.
What you actually need to do — and when
The window to do something about this is before the retirement, not after. Once Jim is on the beach, the knowledge transfer cannot happen. It can only be approximated, awkwardly, by the people who were in the room when Jim was still there.
The structured intervention is straightforward, and it is the one we run at SenseiLab. Identify the 5 to 10 procedures where the retiring person’s tacit knowledge is most concentrated. Run a recorded knowledge-capture session where the person walks through what they actually do, including the parts that are not in the document. Validate the captured procedures with the people who will run them after. Train a designated internal champion to maintain those procedures as they evolve.
This is the work of the SenseiLab SOP Sprint — 30 days, fixed scope, fixed price, on-site with your team. We come in before the retirement, not after. The Sprint produces 5 to 10 living procedures, a deployed platform instance, a trained internal champion, and a documented Knowledge Capture playbook your team can extend.
The Sprint costs less than one quarter of the diffused cost of a single botched transition.
Run this in your plant this week: price the exposure
You probably do not know what the 18-month gap costs your operation. Most plants do not, because the cost is distributed across four line items that each get blamed on something else. Here is the back-of-envelope calculation that surfaces it.
Step 1. Pull a list from HR: every employee who is (a) age 55+ AND (b) has 15+ years of tenure. These are your retirement-exposure population. In most plants the list is shorter than people think, usually 5–15% of headcount.
Step 2. For each person on that list, identify the one or two critical processes they own — processes where they are demonstrably faster, safer, or more accurate than any of their peers. If you cannot identify a process they uniquely own, they are probably not on the exposure list. If you can identify three, they belong at the top of the list.
Step 3. For each of those processes, estimate two numbers: the annual scrap-and-rework cost on that process today, and the historical unplanned downtime hours on that process. Multiply the downtime hours by your fully-loaded hourly cost of the line. Add it to the scrap-and-rework number. That is the annual cost of that process running at its current performance level.
Step 4. Apply a conservative 30% degradation factor for the 18-month window after the senior operator retires. (Industry data on ramp times and high-complexity productivity differentials supports this as conservative — the real number is often higher.) That is the annual cost of that process running degraded.
Step 5. Sum across all the people on your exposure list. That number is your unfunded retirement-knowledge liability. It is not on your balance sheet. It is in your scrap, downtime, overtime, and onboarding line items, waiting to surface.
I have done this calculation with plant managers across half a dozen industries. The number is almost always large enough to fund a structured response. It is also almost always larger than the same plant manager would have estimated before running the exercise.
You probably have a list of people in their late 50s or early 60s with 20+ years of tenure. You may not have that list written down. You can probably name them right now, by face and role, without thinking.
The question is not whether they will retire. The question is whether the 70% of their job that is not in your SOPs walks out the door with them, or stays.
If your exposure number is large enough that you want a structured response to it, book a free 30-minute SOP Readiness Diagnostic. We will walk through who is leaving, what knowledge is at risk, and whether a Sprint would close the gap before it opens.
— Diego Echenique, SenseiLab
Subscribe to the SenseiLab Newsletter for one piece every Thursday on knowledge capture, living SOPs, and operational excellence. Subscribe at senseilab.io
