TPS Relationships #2 - 5S and Problem Solving: Seeing Is Not Fixing
5S makes abnormalities visible, but seeing a problem does not mean it has been solved. This article explores the relationship between 5S and problem solving: one practice helps us recognize the deviation; the other helps us understand its causes, learn from the process, and turn that learning into sustainable improvement.
TPS RELATIONSHIPSPROBLEM SOLVINGTPS FUNDAMENTALS
TPS Relationships #2
5S and Problem Solving: Seeing Is Not Fixing
5S does not solve problems.
Problem solving cannot begin when problems remain hidden.
On their own, each practice has a limited reach.
Together, they create one of the most important relationships within the Toyota Production System: one makes the abnormality visible; the other helps us understand it and act on its causes.
5S helps us see.
Problem solving helps us learn from what we see.
A Workplace Can Be Organized and Still Perform Poorly
When an organization implements 5S, the changes are usually easy to notice.
Unnecessary items are removed.
Tools receive a defined location.
Materials are identified.
Aisles are marked.
Equipment is cleaned.
The workplace begins to look more organized and professional.
However, an orderly area can still suffer from waiting, defects, rework, unnecessary motion, breakdowns, and excess inventory.
Order does not prove that the process is working well.
It only allows us to observe it with less interference.
That is why 5S should not be understood as the final result of an improvement. Its most powerful role is to establish a condition in which it becomes easier to distinguish normal from abnormal.
A missing tool leaves an empty space.
Excess material crosses a visual limit.
A leak appears on a clean surface.
An empty container reveals a replenishment failure.
An obstruction breaks an established condition.
The problem becomes visible.
But it has not yet been solved.
Seeing Is Not the Same as Understanding
When an abnormality appears, it is tempting to immediately correct what we can see.
The leak is cleaned.
The tool is returned.
The excess material is removed.
The container is refilled.
The aisle is cleared.
The visual condition returns to normal, and the area recovers its orderly appearance.
But if we do not understand why the deviation occurred, it will probably appear again.
Cleaning the oil does not repair the machine.
Returning a tool does not explain why it was removed from its place.
Moving inventory does not correct the reason it accumulated.
Replenishing a part does not necessarily improve the system that allowed it to run out.
These actions may be necessary to restore the immediate condition, but they do not replace problem solving.
Restoring the standard and eliminating the cause are two different actions.
The first allows us to continue.
The second allows us to learn.
5S Raises the Question
A good 5S condition acts as a permanent question:
What is out of place, beyond the required quantity, outside the expected condition, or outside the standard?
Problem solving begins with another question:
Why did it happen?
The first directs our attention toward the deviation.
The second forces us to investigate the process that produced it.
This difference may seem simple, but it profoundly changes how an organization responds.
When we only try to restore order, we correct symptoms.
When we use the abnormality as a reason to investigate, we develop knowledge about the system.
A tool that repeatedly disappears may indicate that its assigned location is not where it is actually used.
A container that empties too early may reveal variation in consumption, an incorrect quantity, or a failure in the replenishment process.
A constant accumulation of materials may show that two processes are operating at different rates.
A recurring leak may indicate wear, insufficient maintenance, or an operating condition outside what was expected.
The visible abnormality is the point of entry.
It is not necessarily the complete problem.
The Relationship Is Not Linear
It may seem that 5S is implemented first and that a problem-solving method is used afterward.
In practice, the relationship is more dynamic.
5S reveals a deviation.
Investigation helps us understand its cause.
Improvement changes the process.
New knowledge changes the standard.
And 5S helps keep that new condition visible.
The cycle could be represented as follows:
5S → visible abnormality → investigation → learning → improvement → new standard → 5S
The relationship does not end when the problem is solved.
The solution creates a different condition that must also be defined, visualized, and sustained.
For that reason, 5S and problem solving are not separate activities that simply occur one after the other.
They continuously reinforce each other.
5S allows the system to speak.
Problem solving teaches us how to listen to what it is saying.
When Auditing Replaces Learning
One of the most common risks appears when an organization measures 5S only through audits.
Are the tools in their assigned places?
Are the floor markings visible?
Are the shelves identified?
Is the area clean?
These questions can be useful, but they are not enough.
An organization can receive an excellent score and continue facing the same problems every day.
It can also develop habits that preserve appearances without improving the process.
Before an audit, materials are hidden.
Leaks are cleaned.
Objects are rearranged.
Labels are replaced.
For a few hours, everything appears to be under control.
Then the abnormalities return.
The audit confirmed the appearance, but it did not create learning.
A deeper evaluation would ask:
What abnormalities were detected because of 5S?
Which ones appear repeatedly?
What did we learn by investigating them?
What process conditions were changed?
Which standards changed as a result?
These questions connect the condition of the workplace with the organization’s ability to solve problems.
The true maturity of 5S is not visible only in the orderliness of the area.
It is also reflected in the quality of the conversations that this order creates.
A Visual System Requires a Response
Making a problem visible and failing to respond can be worse than not seeing it.
When people point out a deviation and nothing happens, they learn that showing problems has no value.
When a leak remains for weeks, it stops looking abnormal.
When an inventory limit is constantly exceeded without consequence, the limit loses its meaning.
When missing tools never trigger an investigation, empty spaces become part of the landscape.
The abnormal becomes normalized.
A visual system preserves its credibility only when it leads to a consistent response.
That response does not always mean launching a complex project.
Some problems can be corrected immediately.
Others require observation, data collection, experimentation, or support from different functions.
What matters is that the deviation does not disappear from the conversation simply because someone temporarily restored the expected appearance.
5S must make the problem visible.
The management system must ensure that someone takes it seriously.
Problem Solving Also Improves 5S
The relationship works in both directions.
5S supports problem solving, but problem solving also prevents 5S from becoming an ever-growing collection of rules, labels, and assigned locations.
When we investigate why a tool does not return to its place, we may discover that the assigned location is inconvenient.
When we analyze why materials accumulate, we may realize that the marked space legitimizes a quantity that should never have existed.
When we question why a document is repeatedly found outside its assigned place, we may discover that several people need it at the same time.
In those cases, demanding greater discipline does not solve the problem.
The 5S design itself needs to improve.
Visual standards are also hypotheses.
They represent the best-known way to organize a condition at a particular moment, but they must change when experience shows that they do not work.
Discipline does not mean indefinitely obeying a poorly designed location.
It means maintaining the agreed condition while continuing to learn how to improve it.
From a Clean Workplace to a Learning System
A superficial implementation of 5S seeks clean workplaces.
A mature implementation seeks visible problems.
An organization that solves problems uses those abnormalities to develop knowledge, improve standards, and strengthen people’s capabilities.
That is where the relationship lies.
5S without problem solving can become order without learning.
Problem solving without visual conditions can become delayed investigation based on symptoms that are difficult to reconstruct.
One practice improves the ability to observe.
The other turns observation into understanding and action.
Neither replaces the other.
The TPS Relationship
5S and problem solving perform different functions.
5S establishes conditions that allow a deviation to be recognized quickly.
Problem solving investigates how that deviation was produced and what must change to prevent it from happening again.
One makes the gap visible.
The other transforms that gap into learning.
That is why the relationship is not:
Organize so everything looks good.
It is:
Organize so we can see. See so we can ask. Ask so we can learn. Learn so we can improve.
An organized workplace is not necessarily an improved workplace.
But when order reveals problems and people have the capability to investigate them, the workplace can become a system that learns every day.