Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Ask your best setup guy how he runs a particular part and he'll tell you in thirty seconds — feeds, the trick with the fixture, the spot where it always chatters if you rush it. Ask him to write it down and you get a blank page, or a paragraph that leaves out the three things that actually matter. The knowledge is real. It just lives in his hands and his head, and it walks out the door every time he takes a vacation, moves to nights, or retires. A work instruction isn't paperwork for the quality binder — it's the difference between a job that runs the same way no matter who's standing at the machine and a job that only runs right when one specific person is on shift.
Most small shops don't have bad instructions. They have no instructions, or instructions that describe the part instead of the process — a drawing and a router that assume the operator already knows the hundred small decisions in between. That gap is where scrap, slow first articles, and "why does second shift's stuff always come back" live.
WHERE THE KNOWLEDGE LIVES
veteran's head ──▶ [ the job ] ◀── veteran's hands
│ │
└──── never written ────┐ ┌─────────┘
▼ ▼
new operator ──▶ [ the job ] ──▶ guess, ask around, or scrap
│
└─ written down ──▶ runs the same, every shiftOwner symptoms
A job runs clean when your veteran runs it and rough when anyone else does.
New hires take weeks to get up to speed because everything is taught mouth-to-ear.
The "how" of your best-running parts exists nowhere but in one or two people's heads.
Why this happens
Tribal knowledge is the natural state of a shop that grew on skill. Your veterans learned the hard way, over years, and the learning is buried so deep they don't consciously know what they know — the fixture trick, the dwell before the cut, the deburr order — so they can't easily hand it over. Writing it down feels like busywork to people who'd rather be making chips, and it's genuinely hard: turning a fluid, felt process into words someone else can follow is a skill few operators were ever taught. So the shop keeps running on people instead of process, and every departure is a small fire.
Common mistakes
Describing the part, not the process — a drawing and a router that skip the actual decisions the operator has to make.
Writing for someone who already knows — leaving out the steps a veteran does without thinking, which are exactly the ones a new hire needs.
A wall of text no one reads — dense paragraphs at the machine lose to a two-minute question every time.
Writing it once and never touching it — the process drifts, the instruction goes stale, and people stop trusting it.
Having the veteran write it alone — they'll skip what's obvious to them; the gaps are invisible from the inside.
Business consequences
When the how-to lives only in people, your capacity and quality ride on attendance. A vacation, a resignation, a shift change, and suddenly a reliable job is producing scrap and burning first-article time while someone reverse-engineers what the veteran already knew. Quotes that assumed the fast, clean run don't hold when a slower operator is guessing. The shop that writes its jobs down turns one person's mastery into everyone's baseline — new hires get productive in days instead of weeks, quality stops swinging by who's on shift, and the knowledge stays in the building when the person leaves. The instruction is cheap; relearning a lost process on live parts is not.
How experienced operators think about it
They treat a work instruction as a tool for the next person, not a record for the file. The test is simple and brutal: could a competent operator who's never run this part make a good first piece from the document alone? That reframes everything. You write for the person who doesn't already know, you capture the small decisions the veteran makes on instinct, and you use pictures and the operator's own words instead of engineering prose. They also treat it as living — the first draft is written by watching the job actually run and gets corrected the first few times someone new follows it. The goal isn't a perfect document; it's a job that no longer depends on one irreplaceable pair of hands.
Practical actions
Write it by watching the veteran run it, not from memory at a desk. Have them talk through each step while they work; the offhand comments are usually the gold.
Capture the decisions, not just the sequence — the "if it chatters, back off the feed," the setup trick, the check that tells you it's right. That's the part that isn't on the print.
Write for someone who's never seen the job. If a step assumes knowledge, spell it out or add a photo. The obvious steps are the ones that cause scrap.
Use pictures and plain words. A photo of the correct fixture setup beats a paragraph. Keep it scannable at the machine, not readable at a desk.
Prove it with a new person. Hand the instruction to someone who's never run the part and watch. Every question they ask is a hole to fill.
Date it and fix it when the job changes. A stale instruction is worse than none, because people learn to ignore it.
Questions every owner should ask
If my best operator didn't show up tomorrow, could someone else run their jobs from what's written down?
Do my instructions capture the decisions and tricks, or just repeat the drawing?
When was the last time a new hire actually made a good first piece from an instruction alone?
Frequently asked questions
How detailed does a work instruction really need to be?
Detailed enough that a competent operator who has never run the part can make a good first piece from it without hunting someone down. That's the bar. It doesn't mean documenting how to hold a wrench — you can assume basic skill. It means capturing the part-specific decisions the print doesn't show: the setup order, the feed to back off when it chatters, the check that confirms it's right. If new people keep asking the same question, the answer belongs in the instruction.
My veterans resist writing anything down. How do I get them to do it?
Don't ask them to write — ask them to talk while they work, and have someone else capture it. Most veterans can't write a good instruction but can absolutely narrate a job they've run a thousand times. Framing helps too: this isn't about replacing them, it's about not being the person who gets called on their day off. Many take pride in being the one who finally got the shop's hardest job documented right.
Related articles
Running a Profitable Small or Midsize Manufacturing Business — the pillar.
Capturing What Retires When Your Veteran Machinist Does — getting the knowledge out before it walks.
Getting First and Second Shift to Run Jobs the Same Way — the instruction is what makes shifts match.
Why Jobs Take Longer Than You Quoted — the general problem this feeds.
Where Time Leaks on a Typical Job — relearning a process is a hidden leak.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.