When should I use 5-Why and when 8D?

5-Why suits manageable deviations with a recognisable causal chain and is typically run by one person or a small team in a short time. 8D is the heavier process for customer complaints, safety-relevant defects and recurring problems — with a team, containment actions, verification and formal closure.

Is root cause analysis tied to audits?

No. An analysis can be started from an audit finding, but equally on its own — from a customer complaint or a process deviation, for example. The module is available portal-wide.

Do actions come directly out of the analysis?

Yes. Actions are created per analysis step and continue in the portal-wide action management, including ownership, due date and effectiveness check.

Root Cause Analysis Software: 5-Why and 8D, Structured

Why the method alone is not enough

5-Why and 8D have been established for decades and appear in nearly every quality manual. The problem is rarely knowledge of the method — it is where the result ends up. The analysis is produced in a spreadsheet template or a form, distributed by email, and then filed in a folder.

Three things get lost that both audits and the management review need:

The link to the triggering deviation. Which finding or complaint prompted this analysis?
The link to the actions. Which actions came out of it, and are they closed?
The traceability of the chain. Is the documented cause actually the systemic one — or did the analysis stop after the second why?

Two methods, one data model

5-Why models the causal chain step by step. Each level builds on the previous one, so it stays visible whether the chain reaches the systemic cause or breaks off earlier.

8D walks through all eight disciplines — from team formation through containment and root cause analysis to prevention and formal closure. qportal follows the structure of the VDA 8D volume, including separate causal chains for occurrence and non-detection.

Both methods share the same foundation: analyses optionally hang off a finding, create actions in the portal-wide action management, and log every change.

The difference between correction and corrective action

ISO 9001 clause 10.2 distinguishes clearly between the correction — eliminating the detected nonconformity — and the corrective action, which removes the cause so the nonconformity does not recur. In practice that line blurs regularly: a part is reworked, the item is marked done, and six months later the same finding is back in the report.

A structured root cause analysis is the mechanism that keeps those two levels apart. It is therefore not a formality but the precondition for corrective actions being effective at all.

The 8D analysis in the product: occurrence and detection chains are kept apart and every step carries a 6M category.

Status

The 5-Why and 8D applications are complete and available in the product. The detailed user documentation is being written — until then I am happy to walk through it directly.

Frequently asked questions

When should I use 5-Why and when 8D?: 5-Why suits manageable deviations with a recognisable causal chain and is typically run by one person or a small team in a short time. 8D is the heavier process for customer complaints, safety-relevant defects and recurring problems — with a team, containment actions, verification and formal closure.
Is root cause analysis tied to audits?: No. An analysis can be started from an audit finding, but equally on its own — from a customer complaint or a process deviation, for example. The module is available portal-wide.
Do actions come directly out of the analysis?: Yes. Actions are created per analysis step and continue in the portal-wide action management, including ownership, due date and effectiveness check.