Underused skills: the waste that eventually shows up as turnover

What a plant forfeits when thinking is a management job

The person at the machine sees every cycle, every abnormality and every workaround. Much of that never leaves the workstation. Individuals keep private notes of settings that work, informal fixes are made and not recorded, and the knowledge walks out at retirement. The visible symptoms are recurring faults that somebody on the floor could have predicted, engineering changes that fail because they ignore a practical constraint, and new equipment specified without asking the people who will run it. None of this is a motivation problem; it is a problem of there being nowhere for the information to go.

The conditions that make participation possible at all

Four things have to exist before asking for contribution is realistic. Time within the shift rather than at the end of it. Permission to stop or to raise something without an argument. A route to somebody who can act. And protection from being blamed for revealing a problem. Two further practical barriers are commonly overlooked: language, where a workforce operates in several languages and everything improvement-related is produced in one; and shift patterns, where sessions are always held on days so the night shift never participates. Agency and contract staff are frequently excluded by default and often do the work that matters most.

A skills matrix as a planning instrument rather than wall decoration

Most plants have a grid showing who can do what. Fewer use it to make decisions. Used properly it answers awkward questions: which operations depend on a single individual, what happens to that cell during holidays, who is capable of training others, and where the next qualification effort should go. It also makes visible whether people are progressing at all, which is closely tied to whether they stay. Keep it current, keep it honest about the difference between having been shown a job and being able to run it unsupervised, and review it when planning cover rather than after somebody resigns.

Why paid suggestion schemes tend to disappoint

Attaching a payment to ideas changes what people submit and why. Disputes arise over who thought of something first, contributions are held back until a scheme opens, and the message conveyed is that thinking about the job sits outside normal work. Schemes also generate administrative overhead that outlives the enthusiasm. What consistently matters more is response: an answer to every contribution, a visible change from some of them, and public credit that names the individual. Where a reward exists, keeping it modest and collective avoids most of the distortion while preserving the recognition.

Signals that capability is genuinely being used

Look for operators revising their own standards and being able to explain why, setters running small trials without being asked, handover conversations that discuss process behaviour rather than only output, and people from the floor attending equipment specification meetings and disagreeing with engineers. The counter-signal is turnover among experienced staff, which is expensive precisely because their knowledge is undocumented. Exit conversations that repeatedly mention not being listened to are evidence about the production system, not about individual attitudes, and are worth treating with the same seriousness as a quality trend.

Frequently asked questions

How do we involve shift workers who are never on site for meetings?

Stop relying on meetings as the route. Run short sessions at handover so both shifts overlap, hold some sessions on nights with the same seniority of management present, and make sure any board or log can be contributed to at any hour. Where a plant only ever consults the day shift, the night shift correctly concludes that its observations are not wanted, and the areas that run unsupervised at night are usually where the most useful knowledge sits.

Should temporary and agency staff take part in improvement activity?

If they are doing the work, their observations are as relevant as anyone's, and excluding them removes a large part of the plant's direct experience. The practical obstacles are contractual and administrative rather than principled: induction, agreements with the agency, and whether their time is charged. Settle those explicitly. A workforce split into people who are consulted and people who are not will not sustain any improvement approach for long.

How do we capture knowledge before an experienced operator retires?

Plan it well ahead rather than in the final weeks. Have them work alongside a successor on the real job, write or correct the standards for the operations they know best, and record the abnormal conditions and recovery actions that never made it into any document. Video of a difficult setup, narrated by the person doing it, is often more useful than written procedure. Treat it as a scheduled task with time allocated, not as something to be fitted around production.