Toyota-style problem solving is a disciplined approach for developing a clear understanding of a problem before acting. It is closely connected to PDCA and A3 thinking.
Different Toyota publications and training systems may describe the sequence with slightly different labels, but the core logic is consistent: clarify the problem, understand the current condition, identify causes, test countermeasures and verify results.
Clarify the problem
Problem solving begins by comparing the current condition with a standard, target or expected condition.
The gap should be specific enough to investigate.
A broad statement such as “productivity is low” should be translated into a measurable condition that identifies where and when performance differs from expectation.
Break the problem down
Large problems often contain several smaller patterns.
The team can stratify the gap by product, machine, shift, location, time or another relevant factor.
This helps identify where the problem is concentrated.
Breaking the problem down prevents the team from trying to solve an entire system with one vague countermeasure.
Set a target
A clear target defines the expected improvement.
The target should be connected to the problem and the required business or customer outcome.
It should also have a time frame.
The target provides a reference for evaluating whether the later countermeasure actually worked.
Analyze the root cause
The team investigates why the gap exists.
Gemba observation, 5 Whys, fishbone diagrams, data analysis and technical testing may all contribute.
The emphasis is on evidence.
A plausible story is not enough.
Develop countermeasures
Countermeasures should address the verified causal mechanism.
The team may consider several options and evaluate feasibility, risk and expected effect.
The word countermeasure is useful because it suggests a response to a known cause rather than claiming that the first action is a permanent solution.
Implement carefully
Implementation should include ownership, timing and any support required.
Where uncertainty is high, a smaller test can reduce risk.
The team should predict what result the countermeasure is expected to produce.
This strengthens the later Check step.
Evaluate results and process
After implementation, the team compares actual results with the target.
If the target was not achieved, the learning should be used to revisit the cause or countermeasure.
The team should also reflect on the problem-solving process itself.
What assumptions were wrong? What evidence was missing? What could be improved next time?
Standardize successful learning
When the countermeasure works, the new condition should become part of normal work.
Standard Work, visual controls, maintenance plans, training or other systems may need updates.
This protects the gain.
Problem solving develops people
Toyota-style problem solving is not only about resolving technical issues.
The repeated process develops observation, logical thinking, evidence-based decision making and coaching capability.
This is why leaders often use A3s and PDCA conversations as development tools.
The long-term objective is an organization in which people can recognize gaps, think through causes and improve the system repeatedly.