Problem-solving
Systematically closing the gap between the current and desired situation based on verifiable facts, with everyone in the organisation involved and the process never considered fully complete.
Identifying and closing the gap between the current and desired situation during a Lean transformation or any other process improvement initiative.
In a Lean management system, everyone is involved in problem-solving. Two principles guide this process:
- Everything described or claimed during the problem-solving process (the problem itself, the desired situation, the immediate cause and the root cause) must be based on verifiable facts, not assumptions or interpretations. The fact that the burden of proof lies with the problem-solver is reflected in questions such as: ‘How do you know? Did you first go to the gemba and see the current situation for yourself? How do you know there is agreement on your improvement plan?’
- Everyone recognises that problem-solving is a process that is never complete, and that it begins rather than ends with the implementation of an improvement plan. A plan is a theory about what will eliminate the cause of the problem, as well as what is needed to implement a countermeasure against that cause. The implementation process is a learning process for discovering what will actually be needed to take steps towards the desired situation.
Why problem-solving is at the heart of Lean
A Lean organisation makes deviations visible. Standard work defines how the work should proceed, an andon signals when it proceeds differently, and the board shows which results are falling short. All these signals only add value if someone acts on them. Problem-solving is the step in which a visible deviation leads to a lasting improvement. Without that step, the process stops at identifying issues, producing nothing more than a list of problems.
The first core principle in the definition, working with verifiable facts, prevents the common pattern of a team jumping straight to a solution. An interpretation such as “the department is too slow” sounds like a problem, but provides no point of action. A finding such as “last week, three orders were awaiting approval for more than two days” shows you where to look and gives you a starting point for determining whether the measure works. The figure in this example is illustrative. That is why problem-solving starts at the gemba: you gather the facts first-hand where the work takes place, not from a report or a story.
The second core principle, treating the plan as a theory, changes the role of execution. If a plan is a theory about what will eliminate the cause, implementation is the test of that theory. A countermeasure that does not work is then an outcome to learn from, not a failure. This is the thinking behind PDCA: you plan, carry out the work, check the result and adjust. This gives checking a distinct place in the process, because without it, you cannot know whether the theory was correct.
The root cause is the target. An immediate cause explains what happened, while the root cause explains why it was able to happen. A measure addressing the immediate cause often allows the problem to recur because the conditions that made it possible remain in place. Methods such as the 5 Whys, where Ohno described repeatedly asking why as the scientific basis of the Toyota system, help you move from the immediate cause to the root cause. An A3 gives the entire thought process a consistent, concise structure, from the problem statement to checking and follow-up actions.
The role of the leader
The definition states that everyone is involved in problem-solving. This means problem-solving is not reserved for specialists or a project team. Operators see deviations first, team leaders help organise them, and managers keep the process moving. Leader Standard Work provides structure for this: at the gemba, the leader asks the questions from the definition, such as “How do you know?”, rather than providing the answer. This allows an organisation to develop its employees’ problem-solving capability and prevents everything from being channelled through a small number of experts.
Where things go wrong
Common pitfalls include jumping to a solution before defining the problem, addressing symptoms and skipping the check. There is also a risk that a team sees a temporary solution as the end point, after which the problem returns later in a different form. A shared approach, consistent questions and discussion at the gemba reduce that risk.
Would you like to learn to tackle problems at the source in a structured way? In the Lean Green Belt training you solve a problem from your own work with an A3, using tools such as the problem funnel, the fishbone diagram and 5 whys. Would you like to practise this with your whole team? Then request the Workshop Problem Solving for your organisation.