This article is for plant managers, production managers and shop floor supervisors who feel that “the teams don’t follow instructions,” without knowing exactly why.
- Before talking about engagement, look at what operators work around every day.
- A recurring pain point ends up as waiting, slowdown or micro-stops.
- Data tells you where to go, listening tells you why.
- A quick answer, even a no, beats silence.
Before concluding it is a commitment problem, it is worth looking at what operators work around every day. These small recurring obstacles have a name in lean: pain points, or irritants. And they cost more than they seem.
Thirty minutes with Mehdi
In He was fed up with his employees (in French), continuous improvement consultant Anne-Laure Delpech describes a morning at a small manufacturer. The owner, Antoine, is considering sanctions: his operators supposedly don’t follow instructions. She suggests something else: “What if we went to see Mehdi?”
In half an hour at the paint station, three issues come up. Mehdi has been asking for a cart to move heavy paint cans for a long time, and carries them by hand in the meantime. Two rules contradict each other, and nobody told him which one takes priority. Finished parts pile up because there is no room to move them out. Three decisions are made on the spot.
The article’s conclusion is blunt: “It wasn’t that Mehdi was a bad operator.” He was working in an environment of contradictory rules and unanswered requests, where nobody asked him how he saw his job.
What a pain point is, and why it ends up as downtime
A pain point is a recurring obstacle the operator works around to keep producing. Taken one at a time, it seems minor. Repeated every day, it turns into lost time, variability and sometimes risk.
Mehdi’s three issues illustrate the three most common families:
- The unanswered request. A tool, a piece of equipment or a layout change requested and never delivered. The workaround costs handling time and exposes people to strenuous movements.
- The contradictory rule. Two instructions that cannot both be followed at the same time. Everyone makes their own call, and the same station runs differently from one crew to the next.
- The blocked flow. No room to move parts out, no material at the right time. The line waits, or produces in clutter.
In production data, these pain points rarely show up under their real name. They hide behind “waiting” stops, slowdowns with no cause and speed gaps between crews.
Data doesn’t replace listening, it tells you where to go
Mehdi’s story shows something no sensor will ever do: understand why an operator works the way they do. Production data provides the other half: knowing where and when time is lost, so you can choose the station where those thirty minutes are best spent.
| What the data says | What the operator says | What gets decided |
|---|---|---|
| Frequent “waiting” stops at the end of a batch | Finished parts have no room to go | Organize continuous removal of finished parts |
| Lower speed on one crew | A rule is applied differently depending on the supervisor | Clarify which rule takes priority and write it down |
| Repeated micro-stops at the same station | A tool is missing or an adjustment is done by hand | Deliver the tool, standardize the adjustment |
Without data, you risk spending thirty minutes at the wrong station. Without listening, you see the loss without ever understanding its cause.
A short loop for dealing with pain points
- Collect them at the workstation. A few minutes a week with the operator, where they work, with a single question: what makes you lose time?
- Match them with the data. Link each pain point to the stops or speed gaps it causes, where possible.
- Decide fast. In a short start-of-shift meeting, make the call: fix it, schedule it, or explain why not.
- Respond within a known timeframe. An unanswered request is one more pain point. A quick no is better than silence.
- Check the effect. Follow the station over the following weeks. If the “waiting” stop disappears, everyone sees it, and trust follows.
This is the purpose of the shop floor routines TEEPTRAK supports with Daystream, its daily shop floor management app: pain points and stops are shared in the same place, and decisions stay on record.
Further reading
- He was fed up with his employees, Anne-Laure Delpech, Parcours Performance: the full story, and the question it asks every manager.
- Gemba walk: the key to continuous improvement on the shop floor
FAQ
What is a pain point in lean? It is a recurring obstacle that gets in the way of the operator’s work and that they have to work around: a missing tool, a contradictory rule, a cluttered flow.
How do you surface shop floor pain points? By going to the workstation regularly, asking a simple question about what makes people lose time, and above all responding quickly to every issue raised.
How are pain points linked to OEE? Pain points turn into waiting time, slowdowns and micro-stops, which lower the line’s availability and performance.
0 Comments