A Problem Is a Gap (and Most Operations Can't Have Problems Yet) — LLeanStore Journal

Here is the most useful definition of a problem you will ever carry onto a factory floor:

A problem is the gap between the standard and the current condition.

Read it slowly, because it quietly redraws everything. If the current condition has fallen below an existing standard — the machine that ran now stops, the defect rate that held now climbs — that is a restorative problem, and the countermeasure is to bring things back. If you deliberately raise the target above today's standard, you have created a creative problem — the gap of ambition, the raw material of kaizen.

But notice what both kinds require: a standard. A defined normal. A reference point.

If no standard exists, there is no gap. And if there is no gap, there is — in the precise sense — no problem. There is only weather: some days go better, some days go worse, and nobody can say why, because nothing defines what a day was supposed to look like.

This is what instability actually is. Not an abundance of problems — an inability to have them. The unstable operation's problems are all present, all expensive, and all invisible, because they have nothing to stand out against. The tolerated jam is not a problem; it's Tuesday. The operator-dependent result is not a problem; it's "how this line is." The waste has become normal, and normal is the one place the eye never looks.

The uncomfortable implication: most struggling operations believe they have too many problems, when the truth is closer to the opposite. Their real deficit is standards — the defined normals that would convert their fog into a list of visible, workable, prioritizable gaps. Stability work is the work of earning the right to see your problems clearly.

Book 2 of the Stability Series, The Stability Playbook, is that work made walkable: the 4M diagnostic (can the people, machine, material, and method each be trusted?), the hunt for chronic loss — the waste that has become normal — 6S as an instrument rather than housekeeping, standardized work as the engine that makes problems surface, and a capstone Stability Walk that ends with you writing your first standard, with the person who does the work.

You cannot improve what behaves differently every day. But the deeper truth is kinder: once it behaves the same way twice, improvement becomes almost inevitable — because at last, the gaps have somewhere to show.

Book 2 of the Stability Series. lleanstore.com/stability-playbook

[title](www.lleanstore.com/stability-playbook)