| |
By Bill Murphy · Powered by Colony Spark |
THE OPERATIONS
BRIEF |
|
ISSUE #15 · JUNE 26, 2026 |
|
| |
|
| |
|
Hi there,
Every hire is paid for twice. Once at the offer letter, the recruiter fee, the first paycheck, the part that goes on the budget line. Then again in the three to eight months of ramp before they contribute at the level the role was built for. The second payment shows up as overtime, scrap, and senior operators answering the same questions for the fourth new person in two years.
This issue is about closing that gap from 90 days to 30, not with a new training program, but with a context layer the new hire can search instead of interrupting the people who already know.
Bill
|
| |
The Onboarding Tax.
Every hire is paid for twice. Only one of those payments shows up in the budget.
The math on hiring looks straightforward until you include the part nobody puts on the budget line. The first payment is visible: the offer letter, the recruiter fee, the onboarding paperwork, the first paycheck. The second payment is invisible: the three to eight months it takes a new technical or ops hire to stop asking questions and start contributing at the level the job was built for.
The cost does not appear on the P&L under “onboarding.” It shows up as lower throughput on shifts where the new hire is working, overtime for the experienced people picking up slack, a higher scrap rate during transition, and senior operators who have been on the line for 15 years answering the same questions for the fourth new person in two years.
|
The numbers behind the tax
· 1.9 million US manufacturing positions risk going unfilled by 2033, a 50% fulfillment gap on the 3.8M needed, with $1T in 2030 economic output on the line (Deloitte / Manufacturing Institute).
· 415,000 manufacturing job openings sitting unfilled as of mid-2025 (BLS / Manufacturing Lead Generation).
· 92% of organizations don’t consistently capture knowledge from soon-to-retire employees, even as 58% of C-suite leaders call the risk very serious (Emerj / APQC).
· 12% of annual revenue is the average enterprise loss to delayed productivity during the new-hire ramp period (SenseiLab, May 2026).
|
This is not a pipeline problem anymore. It is a velocity problem, and it is structural, not temporary. 26% of the current manufacturing workforce is 55 or older. More than a quarter of the people who know how things actually work are within striking distance of retirement, and most of what they know has never been written down.
For technical and operations roles, ramp typically runs three to eight months. For senior maintenance technicians and lead operators, it can stretch past a year. A February 2026 Litmos analysis confirmed what plant managers have been experiencing without measuring: manufacturing ramp times are getting longer, not shorter, driven by workforce shortages, rising job complexity, and the accelerating loss of experienced workers (Litmos, Feb 2026).
The operations shortening this curve share one thing: they have stopped treating onboarding as an HR function and started treating it as an operations problem. Instead of handing new hires a binder of SOPs that no longer reflects how work is actually done, they build repeatable systems for capturing and delivering the knowledge that actually drives performance. The result is faster ramp, fewer interruptions to senior staff, and institutional knowledge that survives the next turnover.
|
The ramp time is the capacity leak. Every week of it is productivity that was paid for and not received.
|
Sources: Deloitte / Manufacturing Institute 2024; BLS via Manufacturing Lead Generation, Feb 2026; Emerj / APQC, May 2026; SenseiLab, May 2026; Litmos, Feb 2026.
|
|
| |
The double-throughput problem.
Sebastian Dykas, Smith+Nephew, on what 15 years of operator experience actually produces
Sebastian Dykas is Director of Manufacturing, Engineering, and Maintenance at Smith+Nephew, a global medical device manufacturer. On the Emerj AI in Business Podcast in May, he put a measurable number on what senior operators do that newer operators don’t.
|
“Some of the older, more senior workforce were able to provide double the quantity in a shift as someone who was only doing it for a short period of time. They had developed their own best practices: they knew just because of quantity and time and hours on the equipment how they could produce almost no scrap, how they could produce higher throughput. But it’s very difficult to put that and ingrain that into someone who’s starting off.”
|
Dykas is naming the exact mechanism. Senior operators developed best practices over years on the equipment, practices that live in their heads, not in any system. The performance gap between senior and newer operators was measurable and traceable: double the throughput, near-zero scrap, all from knowledge that was never standardized.
|
The takeaway
This is not a training problem. It is a knowledge access problem. The best practices that actually drive performance were never standardized, and the new hire has no way to reach them until they have spent months on the line absorbing the informal version one conversation at a time.
|
|
|
| |
The Onboarding Agent.
Day 1 with context, not blank slate.
A personalized brief that pre-loads what senior colleagues used to be interrupted to explain.
The ramp time problem is not primarily about training programs or onboarding checklists. It is about knowledge access. Sebastian Dykas named the mechanism: senior operators have developed best practices over years on the equipment that live in their heads, not in any system. When they retire or leave, the knowledge goes with them.
The Onboarding Agent generates a personalized brief on the day a new hire starts: a living context layer tailored to that person’s role, accounts, and function. It is not a 200-page handbook. It is synthesized, structured, and role-specific. The sales rep gets relationship context. The ops lead gets process context. The engineer gets project history and the technical decisions that were made and why.
What the agent does, on Day 1
|
· Pre-loads role-specific context. Key accounts they will serve and the relationship history behind each, open opportunities and recent deals, who to call about what (the informal org chart, not the official one), and critical processes: what gets escalated, who approves exceptions, where the handoffs are.
· Surfaces tribal knowledge from the sources that actually hold it. Call transcripts and meeting notes from the past 12–24 months, deal history and CRM data (not just what is in the notes field, but what actually happened), past SOPs, project history, and internal communications where policy allows.
· Kills the “who do I ask?” loop. Instead of interrupting a senior colleague to ask about a customer’s last complaint, the new hire searches the brief. Instead of discovering three months in that one key account has a pricing exception, they know it on Day 1.
|
How it works in practice
|
Four parts of the build
1. Inputs. CRM data (Salesforce, HubSpot, or equivalent), call transcript archive (Gong, Chorus, or any tool with transcript output), project records, SOPs and internal docs (even outdated ones, since the agent flags gaps), and internal comms where policy and access allow.
2. Processing. An AI agent ingests the data, synthesizes by role and account, and builds a structured brief. Not a data dump, but a curated context layer organized around what the new hire needs to function in their first 30 days.
3. Output. A personalized onboarding document delivered before or on Day 1: key accounts and relationships, critical processes and who owns what, tribal knowledge surfaced from transcripts and notes, and an “ask before you assume” layer that flags known exceptions.
4. Maintenance. The brief updates automatically as new calls are recorded, deals close or move, and the CRM is updated. It is not a document that goes stale. It is a living layer that gets more accurate over time.
|
Week one: with vs. without
|
Without the agent
The new hire spends two to three weeks in survival mode, asking the same questions the last person asked. Experienced colleagues get pulled out of their own work three to five times a day. The first customer call feels cold: the new hire knows the name, not the history. The first exception sends them on a two-hour expedition to figure out who handles it and why. The tribal knowledge the operation runs on stays in the heads of the people who are already overloaded. After 90 days, they might have 60% of what they need.
|
|
With the agent
The new hire arrives with context. Before the first customer call, they have read the relationship history, the last three CRM notes, and the summary of the last call transcript. They know this customer has a pricing exception on freight, that a competitor made a run at the account last year, and that the operations contact is the real decision-maker. The questions they ask are better questions. The interruptions to senior staff are fewer and more specific. After 30 days, they are contributing at a level that used to take 90.
|
What the operator gets
|
· Shorter ramp. 30 days to meaningful contribution instead of 90, because the hire arrives with context instead of blank-slate questions.
· Fewer interruptions to senior staff. The institutional knowledge that used to live in their heads is now accessible through the brief.
· Institutional memory that survives turnover. When the next person leaves, the knowledge doesn’t go with them. It stays in the system.
· A system that compounds. Every call recorded, every note added, every deal closed makes the brief more accurate for the next hire.
|
|
Training teaches skills. Context makes them usable on Day 1.
|
|
|
| |
|
THE OPERATIONS BRIEF
By Bill Murphy · Powered by Colony Spark
|
|
Watching the ramp tax show up as overtime, scrap, and burned-out senior staff, or already building a context layer for new hires? Hit reply, I read every one. Bill
|
|
| |
|