Fault Tree vs Fishbone vs Five Whys: Which RCA Tool Fits SIF

A weak RCA can close an incident file while the same SIF exposure remains alive in the system. This comparison shows when Fault Tree, Fishbone and Five Whys should be used, and when each tool becomes a shortcut that hides causal depth.

Fault Tree vs Fishbone vs Five Whys is a practical RCA decision question. Fault Tree tests logical combinations of failures, Fishbone maps causal families, and Five Whys follows a narrow causal chain. The right choice depends on severity potential, evidence quality, system complexity and the decision the investigation must support.

Why does RCA tool choice matter after a SIF?

RCA tool choice matters because Serious Injuries and Fatalities rarely come from one visible act. James Reason's Swiss Cheese Model remains useful because it separates active failures from latent conditions, which is exactly where many incident reviews lose depth when the team chooses a tool that is too small for the event.

As Andreza Araujo argues in Safety Culture: From Theory to Practice, culture appears in repeated decisions under pressure. An investigation method is one of those decisions, because it tells the organization whether it wants a fast explanation, a defensible explanation, or a control decision that can survive operational pressure.

For EHS managers, the practical question is not which RCA tool looks more sophisticated. The question is whether the tool can connect evidence, failed controls, decision authority and corrective action in a way that prevents recurrence. If the incident had SIF potential, a narrow tool can make the organization feel finished before it has learned enough.

1. Fault Tree Analysis fits complex failure logic

Fault Tree Analysis starts with an undesired top event and works backward through logical gates, usually asking which combinations of failures had to align for the event to occur. It is strongest when the investigation needs to test interaction between equipment, procedures, alarms, permits, supervision, maintenance and human decisions.

Across 25+ years leading EHS in multinational operations, Andreza Araujo has observed that serious events often sit inside combinations, not isolated causes. A valve position, a bypassed alarm, a rushed handover and a weak permit review may each look survivable alone, although together they explain why the barrier system collapsed.

Use Fault Tree when the event involves energy release, process safety, confined spaces, lifting, electrical isolation or any operation in which multiple barriers should have prevented harm. Before the team starts the tree, build an RCA timeline that separates facts from assumptions, because the logic is only as good as the evidence beneath each branch.

The trap is false precision. A beautiful tree can still be wrong when investigators fill missing evidence with confident guesses, so each basic event needs a source, a witness, a record, an inspection result or an explicit uncertainty marker.

2. Fishbone fits broad causal mapping

A Fishbone Diagram, also called an Ishikawa Diagram, organizes possible causes into families such as people, process, equipment, environment, materials and management system. It is useful early in an investigation because it forces the team to look beyond the first visible failure.

The method fits Andreza Araujo's critique of compliance theater in A Ilusao da Conformidade, her Portuguese title usually translated as The Illusion of Compliance. A site may have a procedure, a training record and a checklist, while the Fishbone shows that the procedure is unreadable, the training never touched the critical variation, and the checklist does not test control quality.

Use Fishbone when the team is still opening the causal field and needs disciplined breadth. It pairs well with Fishbone investigation traps because the diagram can become a brainstorming poster if nobody validates each branch with evidence.

The trap is equal weighting. Fishbone makes every branch visible, but not every branch matters equally. After the map is built, the investigation leader must mark which causes are evidenced, which are plausible, which are disproved and which need further field verification.

3. Five Whys fits simple causal chains

Five Whys asks why repeatedly until the team reaches a deeper process or management-system cause. It works best when the incident has a relatively linear path, the evidence is stable and the question is narrow enough that a chain can be defended.

Andreza Araujo's work in more than 250 cultural-transformation projects shows a recurring weakness in this method. Teams use the fifth answer as if depth has been achieved by counting questions, although the real test is whether the final answer identifies a controllable condition rather than a person, attitude or generic lack of awareness.

Use Five Whys for low-complexity incidents, near misses with one dominant failure path, or as a first-pass screen before escalating to Fishbone or Fault Tree. For SIF potential, compare your chain with common Five Whys traps in SIF investigations before accepting the result.

The trap is causal tunneling. Once the team picks the first why, the method can pull everyone down one path and make adjacent failed barriers disappear, which is dangerous when the event involved multiple controls.

4. Which tool handles evidence quality better?

Fault Tree handles evidence quality best when each node is treated as a claim that must be proven or marked uncertain. Fishbone handles evidence breadth well because it exposes gaps across categories, while Five Whys depends heavily on the quality of the first question and the discipline of the facilitator.

What most RCA summaries miss is that evidence quality is not only about documents. Photos, witness statements, equipment logs, permit records, inspection findings and supervisor notes each answer different questions. That is why an evidence plan should precede tool selection, especially when the investigation may influence investment, discipline, design or shutdown decisions.

For practical sequencing, collect and classify evidence first, then choose the tool. If the evidence is fragmented across many sources, read the comparison on photos, witness statements and equipment logs in RCA before forcing a causal method onto weak material.

Five Whys can still work with modest evidence when the event is simple, but it should not be used to compensate for missing facts. A short method does not make poor evidence acceptable.

5. Which tool gives leaders a better corrective action decision?

Fault Tree usually gives leaders the strongest corrective action decision because it shows which basic events and combinations must be controlled to prevent the top event. Fishbone gives leaders a broad portfolio of possible actions, while Five Whys gives a focused action if the chain is valid.

In Andreza Araujo's safety leadership work, the recurring failure is not that leaders lack action lists. The failure is that corrective actions are not tied to a restored control, an owner with authority, a verification date and a field test that proves exposure changed.

For high-potential events, the investigation should ask which action changes the risk pathway. If the final action is only retraining, rewriting a procedure or reminding workers to pay attention, the RCA has probably stopped before reaching control restoration.

The strongest decision is not always the most expensive one. Sometimes the best corrective action is a permit hold point, a design interlock, a supervisor escalation threshold or a maintenance acceptance test, because those changes alter the conditions under which the next job will be performed.

6. When should you combine the three tools?

Combining the three tools makes sense when the event is severe, uncertain or politically sensitive. A practical sequence is Fishbone for breadth, Fault Tree for logic, and Five Whys for selected branches where the team needs to deepen one causal path.

This sequence protects the investigation from two opposite errors. Fishbone prevents premature narrowing, while Fault Tree prevents a loose collection of causes from becoming the final story. Five Whys can then deepen a branch such as planning, maintenance, competence or supervision without pretending to explain the whole event alone.

For an EHS manager, the decision rule is straightforward. If the incident had SIF potential, start wider than Five Whys. If the event involved interacting barriers, use Fault Tree. If the team only needs to clarify one process failure after the evidence is stable, Five Whys may be enough.

Combination also helps when senior leaders need confidence. A board or plant manager can see the causal families, the logical path to the top event and the selected deep chain, which makes the final corrective action package easier to defend.

7. What should EHS managers avoid when choosing an RCA tool?

EHS managers should avoid choosing the tool based on habit, software templates or the easiest format to present. RCA is a decision process, not a paperwork style, and the wrong method can make weak causal thinking look organized.

The first trap is using Five Whys for every event because it is fast. The second is using Fishbone as a brainstorming exercise without evidence standards. The third is using Fault Tree to impress leaders while the basic events remain unsupported by records or field verification.

A stronger rule is to classify the incident first by severity potential, complexity and evidence maturity. Then choose the method that fits the decision. If corrective actions are already failing or recurring, connect the RCA to corrective action rebuilding after recurrence so the investigation does not become another closed file.

Andreza Araujo often frames this as the difference between compliance and real safety. The form may be complete, but if the investigation does not change the conditions that made the event possible, the organization has only documented its exposure.

Comparison matrix

Which RCA tool should you choose first?

Choose Fault Tree first when the event could have killed someone and several barriers should have prevented it. Choose Fishbone first when the causal field is still unclear and the team needs structured breadth. Choose Five Whys first only when the event is narrow, evidence is stable and the investigation decision is limited.

If your organization wants RCA to restore controls rather than close paperwork, Andreza Araujo's Safety School and ACS Global Ventures consulting can help leaders build investigation routines that connect evidence, causal depth and corrective action. Start with the resources at Andreza Araujo and use RCA as a safety decision, not as an administrative ritual.