The Kaizen way of questioning is a simple root cause method: you state a problem, ask "why" it happens, then ask "why" again of each answer, usually about five times, until you reach a cause you can actually fix. You then switch to "what" can remove that cause and "how" to put the fix in place. Known as the 5 Whys, it grew out of the Toyota Production System and is still one of the quickest ways for a team to move from symptoms to a real corrective action.
Key takeaways
- Kaizen is a Japanese word usually translated as "continuous improvement" or "change for the better".
- The 5 Whys is a questioning habit, not a formula; five is a guide, not a rule.
- After "why", ask "what" can remove the root cause and "how" to implement the fix.
- Base each answer on evidence, not opinion, and involve the people closest to the work.
- Stop at a cause the team can control and verify; check afterwards that the problem has really gone.
What Kaizen means
Kaizen is a philosophy and a practice that aims at steady, incremental improvement in every aspect of work and life. It was popularized outside Japan by Masaaki Imai's 1986 book Kaizen: The Key to Japan's Competitive Success. One of its best-known tools is the way of questioning, based on asking "why" five times to get to the root cause of any problem or situation. The technique is often credited to Sakichi Toyoda, founder of the Toyota Group, and is widely attributed to Taiichi Ohno, who built the Toyota Production System; the Institute for Healthcare Improvement's 5 Whys tool page credits Ohno.
The Kaizen way of questioning is not just a technique, but a mindset that encourages curiosity, learning and innovation. It helps to avoid superficial or quick-fix solutions, and instead fosters a deeper understanding of the underlying issues and potential solutions. It can be applied to any domain, from personal development to business management, from product design to customer service, and, in semiconductors, to yield excursions, test escapes and tape-out slips.
The process, step by step
- Start with a problem or a goal that you want to achieve or improve.
- Ask "why" the problem exists or the goal is not met.
- Based on the answer, ask "why" again.
- Repeat this process until you reach the root cause or the core reason.
- Once you have identified the root cause, ask "what" you can do to eliminate or prevent it.
- Based on the answer, ask "how" you can implement the solution.
- Repeat this process until you have a clear action plan.
Example 1: improving customer satisfaction
Here is how the Kaizen way of questioning can be used to improve customer satisfaction.
Problem: customers are unhappy with our product quality.
| Question | Answer |
|---|---|
| Why are customers unhappy with our product quality? | Because our products are defective or damaged. |
| Why are our products defective or damaged? | Because our production process is not standardized or controlled. |
| Why is our production process not standardized or controlled? | Because we lack proper training and documentation. |
| Why do we lack proper training and documentation? | Because we do not have a dedicated quality assurance team or system. |
| Why do we not have a dedicated quality assurance team or system? | Because we do not prioritize quality as a core value of our company. |
Root cause: we do not prioritize quality as a core value of our company.
What can we do to prioritize quality as a core value? Create a quality assurance team and system that monitors and improves our production process and product quality.
How can we create that team and system? Hire qualified quality assurance professionals, provide them with adequate resources and authority, train them on our products and processes, establish clear quality standards and metrics, implement regular audits and inspections, collect and analyze customer feedback, and take corrective and preventive actions.
Action plan: the same list, each item with an owner and a date.
Common mistakes
- Stopping at a person: "the operator made an error" is rarely the root cause. Ask why the process allowed the error.
- Guessing instead of checking: each answer should be backed by data, logs or observation.
- Following one chain only: real problems often have several contributing causes. Branch the questioning, or pair it with a fishbone (Ishikawa) diagram.
- Going too far: "because the market is competitive" is true but not actionable. Stop at a cause the team can change.
- Not verifying the fix: measure afterwards to confirm the problem has gone and has not moved elsewhere.
Tips for applying it at work
- Identify a problem or a goal that is relevant to your work or your role.
- Use the Kaizen way of questioning to analyze the problem or the goal from different perspectives.
- Involve other stakeholders who are affected by or involved in the problem, such as colleagues, managers, customers and suppliers. Ask for their input on the problem, the possible solutions and the action plans.
- Document your findings and conclusions. Use visual tools such as diagrams, charts and tables to illustrate your logic and reasoning.
- Communicate your findings to the relevant stakeholders. Explain how you used the Kaizen way of questioning to arrive at them, and seek their approval and support for implementing the solutions.
- Monitor and evaluate the results. Use data and evidence to measure the impact of your actions, and ask stakeholders how they perceive the changes.
- Celebrate your achievements and share your learnings with others. Recognize everyone's contributions, then pick the next problem or goal to tackle.
Deep dive: the numbers and details
This part holds a technical worked example, how to measure whether a fix worked, and how the method fits with heavier quality tools. Skip it if the overview is all you need.
Example 2: a semiconductor test escape
A second example from chip development shows the method on a technical problem. The details are illustrative.
- Problem: a customer returned parts that fail at cold temperature.
- Why did they reach the customer? Production test passed them.
- Why did test pass them? Final test runs only at room and hot temperature.
- Why is there no cold test? Cold insertion was removed to cut test time after characterization showed no cold fails.
- Why did characterization show no cold fails? The characterization lots came from the typical process corner only.
- Why only the typical corner? The characterization plan had no rule requiring corner lots before removing a test insertion.
Root cause: a gap in the test-reduction procedure, not a bad tester or a careless engineer. What: require corner-lot data before any test insertion is removed. How: update the procedure, add a review gate, restore cold screening for affected lots until corner data is in, and check field returns over the next quarters.
Measuring whether the fix worked
The last step of the method, checking the result, needs a number agreed before the fix. In semiconductor quality the usual measure for field returns is defective parts per million (DPPM):
DPPM = (failing parts / parts shipped) x 1,000,000
Worked example with illustrative numbers: 120 confirmed cold failures out of 2,000,000 parts shipped is 120 / 2,000,000 x 1,000,000 = 60 DPPM. If the next 2,000,000 parts, shipped after cold screening was restored, show 4 such failures, the rate is 2 DPPM, a 30-fold improvement. Two cautions apply. Field returns arrive months after shipment, so the "after" figure needs enough time in the field to be fair. And very small counts are noisy: 4 failures could easily have been 2 or 7, so set a review date and keep watching rather than declaring victory on the first quarter.
Branching the questions
Real failures often have more than one cause. In the test escape above, a second chain could start from the same symptom: why did the customer's incoming inspection not catch the parts? Writing each chain as a separate column, and marking each answer as confirmed by data or still a hypothesis, keeps the analysis honest. When three or more chains appear, a fishbone (Ishikawa) diagram is usually easier to read than a list.
How it fits with other quality methods
The Kaizen way of questioning can help you achieve continuous improvement in any area of your work and life. By asking "why" five times, you can uncover the root cause of a problem, and by asking "what" and "how", you can devise effective solutions and action plans. It can help you build critical thinking, problem-solving, creativity and communication skills, and it can foster a culture of learning, innovation and excellence in your organization or team. It also fits naturally into structured methods such as PDCA (Plan, Do, Check, Act) and the 8D problem-solving process used widely in automotive and semiconductor quality.
FAQ
Do I always have to ask why exactly five times? No. Some problems reach a fixable cause in three questions, others need more. Five is a reminder not to stop at the first answer.
Is the 5 Whys enough for complex failures? For complex technical failures it works best alongside other tools, such as fishbone diagrams, fault tree analysis or 8D, because several causes may combine.
Who should take part? The people who do the work and see the problem first hand, plus someone who can approve the fix. A facilitator helps keep the answers factual.
Try it on one real problem this week and see the results.



Your comments will be moderated before it appears here.