skills transfer & tacit knowledge
D-SKT-06 | First published 2026-08-02 | Revised 2026-08-02 | Primary sources: 1
Disclosure: Gemba Works Lab is supported by advertising. This page contains no affiliate links; if any are added in the future they will be clearly marked (per the FTC Endorsement Guides).
The other guides in this section assume the ideal case — 12-18 months of notice, time to run a full skills matrix, time to shoot video SOPs at a relaxed pace. Real shops often get less. A machinist gives 30, 60 or 90 days' notice, or a resignation lands with even less runway, and the owner needs a sequence that fits the calendar that actually exists. This playbook compresses general knowledge-transfer frameworks published for HR departures into a 4-week plan built around what actually walks out when a machinist leaves: not just task lists, but the judgment layer this section calls tacit knowledge (暗黙知).
KEY POINTS
Two things determine everything that follows, and both should happen on day one, before the 4-week clock starts. First, name the successor — an internal cross-trainee or a new hire who will shadow the departing machinist. If no successor exists yet, that hiring or reassignment decision is now the most urgent task in the shop, because every week without a named successor is a week of the 30 days spent capturing knowledge nobody is positioned to receive. Second, ask the departing machinist to list their own “top 10 jobs that go wrong without me.” Veterans consistently know where their own irreplaceability sits better than a manager's outside guess, and that list becomes the priority order for everything in weeks 1-2 (this framing is consistent with the standard advice in our retiring machinist guide).
Published knowledge-transfer frameworks for employee departures split what a departing person knows into two categories, and the split matters because they need different capture methods: things that are easy to document (procedures, file locations, system access, tooling and program libraries) and things that are hard to document because they only exist as judgment (troubleshooting instinct, which jobs are trouble, unwritten workarounds for aging equipment) (source: ShiftFlow, “Employee Leaving? Use This 12-Week Knowledge Transfer Plan,” Feb. 2026). Spend week 1 building both lists specifically for this machinist's role, using the “top 10 jobs” list from before week 1 as the starting point rather than a generic template. Do not start documenting yet — week 1 is inventory, so that week 2's limited time gets spent on the highest-value items first instead of whatever happens to come up first.
With the inventory from week 1 in hand, week 2 is writing, prioritized by what actually stops production if it's missing rather than by what's easiest to write down first. The general framework's priority order translates directly to a shop floor:
| Priority | Shop-floor translation | Format |
|---|---|---|
| Critical | Setups and programs needed immediately; who to call when a specific machine acts up; any access/credentials for CNC or ERP systems | Step-by-step setup sheets, a one-page contact list |
| High | Regular jobs this person owns; customer-specific tolerances that differ from the print (the “this customer's ±.005 really means ±.002” kind of note) | Job travelers with margin notes, not a separate manual |
| Medium | Rules of thumb: “if the spindle sounds like X, it means Y”; which suppliers' castings need an extra facing pass | A running notes file — capture in the person's own words |
| Low | History and context that's nice to know but doesn't stop a job if missing | Skip if time runs out — this is what a 4-week plan sacrifices first |
Critical and High are the only two rows a genuinely time-boxed 30 days can guarantee. Say so explicitly to the departing machinist and the successor, so nobody assumes Medium and Low got captured when they didn't.
Documentation alone does not transfer judgment — this is the same point this section makes throughout, and it is the reason weeks 3-4 are hands-on rather than more writing. Week 3: the successor shadows the machinist on the Critical and High jobs from week 2's list, watching and asking the questions that surface reasoning, not just steps — “what made you decide to approach it that way,” “what would make you worried about this job.” If a smartphone is handy, record the walkthroughs using the method in our video SOP guide; a recording captures tone and hesitation that notes don't. Week 4: reverse the roles — the successor runs the job while the machinist supervises and corrects, which is where judgment actually gets tested rather than just observed. Close week 4 with the machinist reviewing the successor's independent run of at least one Critical job with no intervention, as a rough go/no-go check before the departure date.
Be honest with the team about the trade-off: a 4-week plan is roughly a third of the shortest “short notice” timeline in the published general framework this guide adapts, which itself describes 2-4 weeks as already compressed relative to the 6-12 month ideal for planned departures (source: ShiftFlow, cited above). What a 4-week version reliably delivers is the Critical and High rows above, transferred to one named successor. What it does not reliably deliver is redundancy — a second and third person cross-trained, or the Medium/Low knowledge that makes someone excellent rather than merely competent. If the retirement date is known 3+ months out, do not use this compressed plan by default; use the fuller skills matrix and tacit-knowledge capture methods elsewhere in this section instead, and save this playbook for the notice periods that don't leave a choice.
Last updated: 2026-08-02 | Primary sources referenced: 1 | This playbook adapts a general HR knowledge-transfer framework to a shop-floor/tacit-knowledge context; it is not manufacturing-specific research, and we say so above. Spotted an error? Tell us via the contact page.