Ask any plant head running a small aero-components shop who the shop cannot lose. The answer comes within seconds. Usually it is the CAM programmer who wrote the macros for the thin-walled impeller, the toolmaker who spots a fixture by blueing, or the solderer trusted with hot-air BGA rework. Everybody knows the names. Very few units have written down what those names carry.
How the dependency looks on the shop floor
- Repeat orders for a difficult part wait until one programmer returns from leave, because nobody else will run his datum and clamping sequence.
- Night-shift operators phone the same setter at home when chatter appears on a titanium pocket.
- The tool room cannot start a new drill jig until the senior fitter finishes the gauge he is lapping.
- In the avionics cell, every fine-pitch rework ticket queues for the one person with the steadiest hand.
- Juniors are handed loading and deburring, so they never see the subroutines, feeds and insert choices that make the hard job work.
Early signals that one name is becoming a bottleneck
Dependency rarely arrives in one go. It builds over a year or two as new part families land on the same desk. Watch for a few tell-tale habits.
- Quotations for new parts list a delivery date only after one person has looked at the drawing.
- The same name appears on every first-off report for a part family.
- Holiday requests from that person are refused or quietly withdrawn.
- Supervisors schedule around his shift instead of around machine availability.
- Juniors describe a job as 'his part' rather than by its drawing number.
Any two of these together mean the shop is exposed. Treat it as a planning matter, not a personality problem.
What that costs a supplier
The first cost is lead-time. A customer schedule built on one man's availability slips whenever he is away. The second is scrap. A stand-in proving an Inconel programme without the original author's notes will break inserts and spoil blanks. The third is bargaining power of the wrong kind. A key person who knows the shop cannot cope without him can ask for anything, and a rival plant knows it too.
There is a quieter cost as well. The expert is exhausted. He is pulled onto every crisis, has not had an unbroken week's holiday in years and cannot develop further. Many such people leave for that reason rather than for pay.
Why the pattern keeps coming back
Small-batch work rewards whoever solved the job first. Once a programme is proven, nobody wants to risk a second author. Production pressure always beats teaching time. Pay grades usually reward output, not the number of people an expert has brought up. And in a defence unit with controlled drawings, managers are cautious about widening access, so knowledge stays in fewer heads by design.
A step-by-step fix
- 1
List every single-point job
Walk each cell with the supervisor and note any part, process or test only one individual can manage unaided. Include programme proving, fixture fitting, five-axis set-up, BGA rework and flight-control board diagnosis.
- 2
Score each job for exposure
Mark how often it repeats, how much revenue rides on it and how long a stranger would need to learn it. Two or three jobs will stand out.
- 3
Name a second person for the top two
Pick someone one grade below, with patience for slow learning. Write the pairing into both role descriptions so it is not a favour.
- 4
Capture the job while it runs
During the next live run, the second person photographs the fixture, records the clamping sequence, tool-life notes and coolant settings, and the expert corrects the sheet.
- 5
Let the second person lead under watch
On the following repeat, roles swap. The expert stands beside the machine and only steps in when scrap is likely.
- 6
Reward teaching in the grade
Add 'has brought a second person to independent running on a named job' to the senior grade criteria and to the review.
- 7
Review the list every quarter
Strike off jobs that now have two names, and add new single-point jobs created by fresh orders.
First checks: willingness, and where the notes live
Check whether the expert is willing. Some fear that sharing makes them replaceable. Tell them plainly that a second name on their job exists so they can move to tougher work, and back that with the grade change. Check, too, that set-up sheets live somewhere controlled. In a defence shop, a photo of a fixture on a personal phone creates a different problem.
Clear role design helps here, because it names who covers whom. The CNC aero-parts grading notes shows how setters and programmers are graded in that trade. For the toolroom version of the same risk, see toolroom succession notes.
Keeping the expert while you spread the knowledge
Spreading knowledge should never feel like preparing for someone's exit. Couple it with a visible title, such as lead programmer or master fitter, and a voice in deciding which new jobs the unit accepts. People who hold scarce skill want to be consulted, not only relied on. The wider picture is in our sector overview for aero and defence suppliers.
