How Do You Conduct an Incident Investigation? Kellie Andrews on Finding the Real Cause
Prefer To Watch?
When something goes wrong at work, the first question is almost always who did it. Kellie Andrews has spent her career teaching investigators to ask a different one. In a safety investigation, she says, the person involved matters only as a lens for understanding why it happened.
In this episode of the Safety Spotlight Podcast, we sit down with Kellie Andrews, Vice President of Safety, Security, Quality and Environment at Keolis Commuter Services in Boston, to talk about incident investigation, systems thinking, and why safe systems are profitable systems.
Kellie started out as an officer and air traffic controller in the Australian Air Force. Tower training was a struggle while radar came naturally, and about three months after she earned her endorsement, everything suddenly clicked. That moment showed her she had passed training without fully understanding what she was doing, and it shaped how she went on to train others: by making them prove the fundamentals. In her mid-twenties, posted to Sale in Victoria, she was one of the youngest leaders in her unit, responsible for training, issuing licences and investigating operational incidents.
Early on, a mentor told her to see opportunity when it presents itself and say yes, and that is what she did. In the UAE she worked alongside controllers from all over the world, each bringing different standards and habits. When a new two-person safety team presented its plans, her reaction was “not with two people, you’re not,” and she asked to join. Soon after, she was its lead investigator. She went on to work as an inspector at the Dubai Civil Aviation Authority, where her first day included a meeting about unmanned air taxis, then helped build a new safety system at Dubai Airports before moving into rail in 2021.
This conversation breaks down:
• The sandbox analogy for why we instinctively look for who to blame, and why a safety investigation uses the who only to get to the why
• Why incidents are never linear, and why she is careful with the term root cause
• Writing an investigation report like a lab report, so a leader can read the summary and recommendations without wading through the analysis
• Building enough trust that people hand over their records and tell you what else is going on
• The 5 Whys, AcciMaps and the seven or eight investigation models she teaches her team
• Why the brain’s habit of taking shortcuts is the reason safe systems are profitable systems
• Her advice for safety professionals early in their careers: own your mistakes
Kellie treats every investigation as a puzzle about the whole system. Did the worker have rules to follow, and were they good rules? What technology were they juggling at the time? Was the equipment maintained, and was it required to be? Each question becomes a strand in what she calls a spider web, and the strands connect in ways that are dynamic rather than linear. That is why she is careful with language. In an organization that is not yet mature, a neat list of root causes gives people the chance to say, “Wasn’t me. Look at them.”
The report has to be just as disciplined. “Investigation reports are not novels,” she says. “They’re like a science report.” The detail sits in direct observations and analysis, and the findings come out as simple statements of contributing factors and recommendations. Getting there depends on trust, because an investigator is “essentially marking someone’s homework for them without being in their department.” Confidential, well-structured interviews are a skill in their own right, and people will often share far more than the incident itself.
Kellie also makes the business case. The human brain likes to be efficient, so a shortcut that works once gets reinforced, and then another follows. Investigations help reoptimize the human so performance stays where it should be. “Safe systems are profitable systems,” she says, and she suggests any operation start by looking at its cost of damage and the labour hours lost to repairs.
You will also hear why she tells investigators “don’t race to be first, race to be right,” since what comes out in the first hours changes nine times out of ten, and how a broken piece of equipment can lead an investigation all the way back to a procurement problem. She talks about a friend who once told her she was “not everybody’s cup of tea, more like a strong coffee,” and about learning when to lean in and when to lean out. She also shares how her belief that competence wins in the end had to grow, as she became more senior, to include strategy, networking and getting comfortable talking to people she did not know.
If you investigate incidents, lead a safety team, or want a culture where people tell you the whole story, this episode is worth your time.
You can find Kellie on LinkedIn, and learn more about Keolis on their website.
Other Podcasts
Chris Vienneau of Clark Builders explains how crews are trained to spot the hazards that could kill them, sharing lessons...
Jason Ross of Bird Construction shares how a panic attack on a winter highway in northern Manitoba led him to...
Garrett Hill shares why crews take in the safety message once they know the person delivering it, and what ten...
Jacqueline Handy explains how she fell into safety from a marketing role, sharing lessons from New York City transit and...