
The 5 Whys technique is a simple and powerful root cause analysis tool, which involves asking “why?” repeatedly (five times or more) to identify the real origin of a problem.
The goal is to go beyond the symptoms and find the technical and procedural root cause, enabling lasting corrective actions.
🧠 Why use the 5 Whys?
- Easy to apply, even without complex software or tools
- Encourages logical and collaborative thinking
- Helps avoid superficial or palliative actions
- Supports methodologies like 8D, Ishikawa, PDCA and Kaizen
🧩 Practical example with AJOLLY Testing
Problem: The electronic board failed the RS485 communication test.
- Why? → The board did not respond to the test command.
- Why? → The firmware did not initialize the UART correctly.
- Why? → The loaded firmware version was incorrect.
- Why? → The test system did not validate the firmware version.
- Why? → The test sequence does not include version verification.
➡️ Root cause: Lack of automatic firmware verification → technical and traceable corrective action.
🔧 How AJOLLY Testing applies the 5 Whys
AJOLLY Testing uses the 5 Whys technique integrated into its test engineering, CAPA, failure resolution, and continuous improvement processes.
📊 Data-driven application
- Analysis of automatically recorded failures in systems like TestStand, LabVIEW
- Association with logs, series, operators, and measurement data
- Integration with Ishikawa diagrams and 8D for greater depth
📄 Standardized documentation
- Digital 5 Whys templates linked to the non-conformity number
- Cross-validation with corrective and preventive actions (D5 and D7 of 8D)
- Reports accessible in MES, QMS, or internal dashboards systems
🤝 Training and problem-solving culture
- Training operators and engineers in the 5 Whys technique
- Mandatory inclusion in recurring or critical incidents
- Support for multifunctional teams in technical investigations
With AJOLLY Testing, the 5 Whys become a robust technical tool, connected to real data and applied with traceability, contributing to definitive solutions and organizational learning.