Where Tripod Beta Fits Among Investigation Methods

An investigation method is a tool for asking questions in a disciplined order. Every method has a shape, and that shape decides which causes the team will find and which it will miss. A practitioner who leads serious investigations has to judge which shape suits the event in front of them, and has to defend that choice to managers, regulators and the workforce.

Tripod Beta is a barrier-based, organisational method. It starts from the event, asks which barriers should have stopped it, and then follows each failed barrier back through the person at the workface to the organisational decisions behind them. Its output is a tree that links what happened on the day to conditions that the organisation created and can change.

Worked example: a forklift strike in a warehouse

A pedestrian was struck by a reversing forklift truck. A 5 Whys review stopped at "the driver did not look behind". A Tripod Beta analysis of the same event found three failed barriers: segregation of pedestrian and vehicle routes, the reversing alarm, and the driver's rear check. Behind the missing segregation sat a layout change made during a busy season with no review of traffic routes. Behind the inaudible alarm sat a maintenance plan that never tested alarm volume. Behind the missed check sat a loading target that rewarded speed. The second analysis produced three organisational actions; the first produced one retraining session.

Worked example: a recurring pump seal leak

A site had five seal leaks on the same pump in a year. Each was minor. A timeline method showed that every leak followed a restart after a short shutdown. A full Tripod tree would have added little here: the cause was technical and the fix was an engineering change to the restart procedure. The practitioner chose a lighter method and saved Tripod time for events that needed it.

Common mistakes when choosing a method

• Using Tripod Beta for everything. The method loses credibility when a sprained ankle on a kerb gets a forty-node tree.
• Using a quick method for a serious event because it is due tomorrow. The deadline is an incompatible goal of its own, and the quick method will usually stop at the individual.
• Choosing the method after the answer. Some teams pick the tool that will produce the conclusion they already hold. Choose the method from the event's potential and complexity, before analysis starts.