All Articles

SPEED: Great for the Movies. Dangerous for Incident Investigations

18 November 2026
SPEED: Great for the Movies. Dangerous for Incident Investigations

Why rushing an investigation can mean missing the very things we need to learn.


In the 1994 action movie Speed, starring Keanu Reeves and Sandra Bullock, a bus is rigged with a bomb that will explode if its speed drops below 50 miles per hour. The passengers are trapped, the driver has limited options, and the entire movie revolves around one simple requirement: whatever happens, the bus must keep moving.


It's a great premise for an action movie, but a terrible approach to workplace incident investigations.


Unfortunately, the pressure to keep moving, reach a conclusion and deliver a report can feel remarkably similar to the situation on that bus. An incident occurs, management wants answers, deadlines are established and the investigation team is expected to identify what went wrong as quickly as possible.


While timely investigations are important, there's a significant difference between acting with urgency and rushing through an investigation. When speed becomes the priority, the quality of the findings and the opportunity for organisational learning can suffer.


The Investigation Bus Has Left the Depot

Picture a familiar workplace scenario. A significant incident has occurred, an investigation team has been appointed and senior management has requested a completed report by Friday.


The team begins gathering evidence, but before the first round of interviews is complete, questions start arriving. Have the contributing factors been identified? When will the ICAM chart be ready? Surely we know what happened by now?


These questions are understandable. Organisations need information to manage risks, communicate with stakeholders and make decisions about returning to normal operations. However, the pressure to provide answers can unintentionally influence how an investigation progresses.


Investigators may begin developing conclusions before gathering sufficient evidence. Early assumptions can become accepted explanations, and information that challenges those explanations may receive less attention.


The danger is that an investigation starts working towards confirming what people already believe happened, rather than establishing what the evidence actually demonstrates.


Just like the bus in Speed, everyone wants to reach the destination. The problem arises when getting there quickly becomes more important than understanding the journey.


1. Don't Confuse Urgency with Speed

One of the most important distinctions in incident investigation is recognising when speed is necessary and when a more considered approach is required.


Following an incident, there are legitimate reasons to act quickly. Physical evidence can deteriorate, equipment may be moved, incident scenes can change and witness memories may become less reliable over time. Immediate action is also required to protect people, secure the scene and manage any continuing risks.


The ICAM investigation process recognises this by emphasising that investigations should commence as soon as practicable after an event. Early action helps preserve the information required to establish what happened.


However, commencing an investigation promptly does not mean the analysis should be rushed.


Once evidence has been secured, investigators need sufficient time to examine the information, identify inconsistencies, reconstruct the sequence of events and determine which factors contributed to the incident.


An investigation that begins quickly and follows a disciplined process is far more useful than one that races towards a conclusion simply to meet a reporting deadline.


The objective is to understand what happened and why, so that meaningful improvements can be made. Completing the paperwork is only one part of that process.


2. Don't Blame the Bus Driver Before You Understand the Situation

One of the more interesting comparisons with Speed involves Sandra Bullock's character, Annie, who unexpectedly finds herself driving the bus.

She wasn't trained to manage a vehicle carrying an explosive device. She didn't create the circumstances, determine the operating conditions or establish the rules under which she was expected to drive. Yet she suddenly became responsible for keeping the bus moving while responding to an extraordinary situation.


Imagine an investigation that focused entirely on her driving behaviour.


Why was she travelling so fast? Why didn't she stop at the traffic lights? Why did she drive through dangerous areas? Why didn't she follow normal road rules?


Without understanding the circumstances, those questions could lead to conclusions that completely misrepresent what was happening.

The same problem occurs in workplace investigations when attention focuses too quickly on the actions of an individual.


An operator makes an error, a maintenance technician misses a step or a supervisor makes a decision that appears questionable when reviewed after the event. These actions may be relevant to the investigation, but they rarely provide a complete explanation of why an incident occurred.


Investigators also need to understand the conditions influencing those actions. Was the equipment suitable for the task? Were procedures practical and understood? What information was available at the time? Were workers operating under conflicting priorities, and what controls had the organisation established to manage the risks?


This is where the Incident Cause Analysis Method (ICAM), developed by Gerry Gibb at BHP, provides a structured approach.


ICAM examines the interaction between Individual or Team Actions, Task or Environmental Conditions, Absent or Failed Defences and Organisational Factors. By examining these areas together, investigators can understand how the broader system of work influenced the event.

Focusing exclusively on the person operating the equipment may identify what happened at the point of failure, but it can leave the conditions that made the incident possible completely unaddressed.


Article content


3. The First Explanation Isn't Necessarily the Right One

Rushed investigations are particularly vulnerable to premature conclusions. When an explanation appears obvious, there can be a temptation to accept it without examining whether the available evidence supports it.


Consider a workplace vehicle incident where a driver loses control of a truck.


The initial incident notification might state that the driver failed to maintain control of the vehicle. While this describes the immediate event, it provides little insight into the contributing factors.


A more thorough investigation might identify that the vehicle had experienced recurring steering problems, that previous maintenance reports had documented the defect and that repairs had been deferred because replacement equipment was unavailable.


These findings would significantly change the understanding of the incident.


The driver's actions may still form part of the analysis, but the investigation could also identify deficiencies in maintenance management, equipment availability and the effectiveness of existing risk controls.


If the investigation had been completed based solely on the initial explanation, these broader organisational issues might never have been identified.


This is one of the greatest risks associated with rushing an investigation. The organisation may implement corrective actions that address the most visible part of the event while leaving the underlying contributing factors unchanged.


The report gets closed, the statistics are updated and everyone moves on. Meanwhile, another worker may encounter the same conditions because the system itself hasn't improved.


4. You Can't Skip the Investigation Process and Expect Quality Findings

Imagine trying to navigate the bus in Speed without knowing what obstacles were ahead, where the road was going or what options were available.


Continuing to drive without understanding those conditions would make an already difficult situation considerably more dangerous.

Incident investigations face a similar problem when teams skip important stages of the process in an effort to save time.


ICAM follows four investigation phases, commonly referred to as GOAL: Gather, Organise, Analyse and Learn. Each phase builds on the information and outcomes of the previous stage, providing a structured pathway from the initial incident through to organisational improvement.


Gather: Establish what happened

The first phase involves gathering relevant information using PEEPO, which considers People, Environment, Equipment, Procedures and Organisation.


This structured approach encourages investigators to examine the broader system of work rather than limiting their attention to the most obvious evidence. Witness interviews, physical evidence, records, procedures and other relevant information all contribute to establishing the facts.

Rushing this stage can result in important evidence being overlooked, particularly information relating to organisational decisions or conditions that existed well before the incident.


Organise: Reconstruct the sequence of events

Once the information has been gathered, investigators need to organise it into a logical timeline.


This helps establish what occurred before, during and after the incident, while identifying gaps, inconsistencies or information requiring further verification.


A well-developed timeline also helps investigators distinguish between established facts and assumptions. Without this step, there is a greater risk of drawing connections between events that may not be supported by the evidence.


Analyse: Understand why the incident occurred

The analysis phase examines the contributing factors using the ICAM framework.


This requires investigators to consider the actions taken, the conditions that influenced those actions, the effectiveness of risk controls and the organisational factors that contributed to the event.


Analysis should be driven by the evidence gathered during the investigation. Starting the ICAM analysis too early, or attempting to make the evidence fit an already established explanation, can undermine the reliability of the findings.


Learn: Turn findings into improvements

The final phase involves developing recommendations that address the identified contributing factors and improve the organisation's ability to manage similar risks.


Recommendations should be practical, proportionate and directly linked to the investigation findings. They should also focus on strengthening the system of work rather than relying solely on reminders, retraining or increased supervision.


Each phase of GOAL has a specific purpose. Skipping steps may create the appearance of efficiency, but it can also lead to incomplete analysis and recommendations that fail to address the problems identified.


5. The Deadline Shouldn't Determine the Findings

Investigation deadlines are a normal part of organisational management, and for good reason.


Leaders need timely information to make decisions, workers need confidence that incidents are being addressed and organisations may have specific reporting obligations. Establishing expectations for investigation progress is both reasonable and necessary.


However, a deadline should guide the management of the investigation rather than influence its findings.


If important evidence remains outstanding, investigators need to communicate that limitation. If a key witness has not been interviewed or the timeline contains unresolved inconsistencies, those matters should be considered before conclusions are finalised.


Investigation leaders have a responsibility to manage the process effectively, including identifying resource constraints, prioritising activities and keeping stakeholders informed.


Management also has a role in ensuring that investigation teams have the time, capability and support required to complete their work to an appropriate standard.


There is a difference between holding an investigation team accountable for progress and pressuring them to produce findings before the evidence has been properly examined.


A report delivered on time may satisfy an administrative requirement, but if the findings are incomplete or unsupported, the organisation may have gained very little from the investigation.


6. Don't Let the Investigation Crash at the Finish Line

In Speed, keeping the bus moving was never the ultimate objective. The real goal was to get the passengers out of danger.


Article content


The same principle applies to incident investigations. Completing the report is an important milestone, but the real objective is to reduce risk and prevent recurrence through organisational learning.


An investigation can be technically complete while achieving very little practical improvement.


For example, consider an investigation that identifies deficiencies in an organisation's maintenance management system. If the resulting recommendation is simply to remind operators to complete their pre-start inspections, the action may have little effect on the deficiency identified.

The recommendation needs to address the contributing factor. That might involve reviewing maintenance planning, improving defect escalation processes or strengthening the controls used to prevent equipment with unresolved safety-critical defects from remaining in service.


The specific action must be determined by the evidence and the circumstances of the investigation.


This is why the quality of recommendations matters just as much as the quality of data gathering and analysis. If recommendations fail to address the identified contributing factors, the investigation may be closed while the risk remains.


An organisation should measure the value of an investigation by what it learns and improves, rather than simply how quickly the report is completed.


So, How Fast Should an Investigation Be?

There is no single timeframe that suits every incident.


The depth and complexity of an investigation should reflect the actual and potential consequences of the event, the level of risk and the opportunity for organisational learning.


A relatively minor incident may be appropriately investigated using a structured 5 Whys approach, while a significant or high-potential event may require a more comprehensive ICAM investigation.


In either case, the principles remain consistent. Evidence needs to be gathered promptly, information must be verified, findings should be supported by facts and recommendations need to address the contributing factors identified.


Efficiency is important, but genuine efficiency comes from planning the investigation properly, using the right methodology and ensuring investigators have the capability to apply it.


A well-managed investigation can progress quickly without compromising quality. The challenge is recognising when the process needs more time and having the confidence to explain why.


The Final Destination Is Learning

The movie Speed works because the characters are forced to make decisions under extraordinary pressure, often without enough information or time to consider their options.


Workplace incident investigations should operate differently.


Investigators have an opportunity to examine the evidence, reconstruct events, understand decisions in context and identify where the organisation's controls or systems need improvement.


That opportunity is easily lost when the investigation becomes a race to produce a report.


The next time someone asks why an investigation hasn't been completed, it may be worth asking a different question: Have we gathered and analysed enough evidence to be confident that we're addressing the right contributing factors?


Because completing an investigation quickly might look good on a performance dashboard, but completing it properly provides the organisation with a much better opportunity to prevent a similar incident.


And unlike Hollywood, we don't get a second take when things go wrong.


Speed is great entertainment. It's a terrible investigation strategy.