Five whys: stay with the evidence

Repeating why can open an investigation, but each step needs support.

An elegant chain without evidence can move away from how the process actually works.

How do you connect conclusions with verifiable change?

A plausible explanation is not a demonstrated cause. At each step, separating facts, interpretations and missing information helps the team look beyond the first visible error. If an assumption lacks support, reopen the question rather than adding another why simply to complete the diagram.

During field discussion, ask how a foreseeable difficulty is handled: who can be involved and which information supports a decision? Connecting observations, ownership and feedback helps establish whether a control is workable as well as documented. The review should consider actual conditions rather than assume that the same arrangement fits every task.

For the next discussion, choose a concrete situation and ask which evidence would help explain it. Follow up the observations by making ownership of open questions visible and explaining how feedback will be provided to the people involved.