Product changes keep resetting the learning: a fix for electronics companies

Revision C of a power supply board moves a flyback diode and swaps a resistor network for discrete parts. The ECN reaches stores, purchasing and the SMT programmer. It never reaches the hand-soldering bench, where operators keep fitting the diode the revision B way. Functional test catches one batch. A week later, the night shift repeats it.

Our overview of HR in electronics businesses lists this as a standing pattern. Each fresh board, part substitution or revised test sends technicians back to relearning, and without written instructions and quick refreshers the same slips return.

• Hand-fit parts whose orientation or footprint moved between revisions.
• Alternate components with unfamiliar markings, so a correct part looks wrong and a wrong one looks right.
• Revised test limits loaded on one tester but not on the second station.
• Changed torque, label or packing steps for one customer's variant of a common product.
• Firmware images flashed at end of line that must match the board revision exactly.

One slip after a change is a training signal. A repeat on the following shift is a system failure, and each repeat costs more. Boards go to rework, test queues swell and an urgent dispatch waits. In contract manufacturing, the customer's auditor may ask who was trained on the change and when. A shrug in reply lands on the whole unit. Operators feel it as well, because being corrected for a change nobody explained is a fast route to resentment.

In most electronics firms, change control serves engineering and materials. The ECN lists drawings and part numbers. It rarely lists which stations, shifts and people now need to learn something. Work instructions are updated last, sometimes weeks after the boards. Training follows a yearly calendar that has no idea a new product launches next month. And the skill matrix shows who is certified on a product, but not on which revision.

1. 1

   Trace the last three ECNs first

   For each, find out who on the floor heard about it, how and when, and whether errors followed. The answers show exactly where the chain snaps.

2. 2

   Add a people line to every ECN

   The engineer raising the change lists the stations and test steps affected. Without that line, the change is not released.

3. 3

   Refresh the work instruction before the first kit

   Photographs of the new part, its marking and its orientation go up at the station, and the old sheet comes down.

4. 4

   Brief each shift at the line

   A ten-minute talk by the line leader at shift start, using the change brief below, for every shift that will build the new revision.

5. 5

   Run a first-off check on every shift

   The first board after the change on each shift goes to quality before the batch continues.

6. 6

   Recertify on the altered step only

   Operators who fit or test the changed part demonstrate it once under observation. The skill matrix records the revision alongside the product.

Product and new revision: ________.
What changed, in one sentence: ________.
Stations affected: ________.
What the operator must now do differently: ________.
Photo of old and new attached: yes or no.
Test limits updated on every tester: yes or no.
Shifts briefed, with signatures: ________.
First-off board checked by: ________.

Where several customers' changes land in the same week, see skills planning at EMS providers. Where low volumes make relearning normal, see training at industrial electronics makers. Why sign-off sheets double as quality evidence explains what an auditor looks for.

Ask planning for the launch and revision dates for the coming quarter. Put each on the training calendar with the stations it touches. Book trainer time the week before each launch, not after the first faults. Keep a small library of photo instructions and clips sorted by product and revision, so a refresher takes minutes at the bench instead of a classroom morning.

Ask one more thing of engineering: an early warning. Even a rough note that a revision is coming next month lets the training lead prepare practice boards and update sheets in advance. Engineers who see their changes land cleanly on the line are usually happy to send that note.

• A golden sample of the current revision mounted beside the station, with the superseded board removed or marked void.
• Revision letters printed large on the traveller card and the kit tray, in a colour that changes with each release.
• A checksum or version readout at the programming jig, so the flashing operator can confirm the image before the board moves on.
• Superseded reels and loose parts quarantined in stores with a hold tag until engineering clears them.

These cues cost little and work at three in the morning, when nobody is around to answer a question. They also help a relief operator borrowed from another line, who missed the shift briefing entirely.

Add a revision column to the skill matrix for every product with frequent changes. When an operator is recertified on a new revision, the old entry stays visible with its date. Line leaders check the matrix before allocating stations at shift start, so nobody builds revision C on a revision B sign-off.