Knowledge Check: Quick Quiz
Test your understanding. Answers and short explanations follow the questions.
- Why is it important to define verification metrics before implementing a countermeasure?
- a) To make the document look complete
- b) To ensure you can objectively measure whether the countermeasure removed the root cause
- c) To delay implementation
- Which tool is best for brainstorming multiple categories of potential causes?
- a) 5 Whys
- b) Fishbone diagram
- c) A3 (always)
- True or false: If a countermeasure reduces the symptom but creates another problem, it should always be rolled out company-wide.
- When using 5 Whys, what is the most important safeguard?
- a) Stop after exactly five whys
- b) Always blame the person who made the last action
- c) Seek evidence for each causal step and confirm before accepting it as root cause
- What is a quick sign that a problem is suitable for a small A3 and short test (<4 weeks)?
- a) The problem is clearly tied to a process or equipment element that can be changed and measured in the short term
- b) It requires a long organizational policy change that will take months
- c) No data exists and no one is willing to collect any
Answers
- b) Verification metrics let you objectively determine if the countermeasure removed the root cause rather than masking the symptom.
- b) Fishbone diagrams help teams consider multiple cause categories before drilling down.
- False. If a countermeasure creates other problems, it needs further testing and adjustment before any broader rollout.
- c) Evidence for each why prevents confirmation bias and premature conclusions.
- a) Problems that can be changed and measured quickly are ideal for a small A3 and a short test; longer policy issues need larger change management approaches.
Discussion
Comments and conversation will live here.