How Do You Conduct an Incident Investigation? Keolis’ Kellie Andrews on Finding the Real Cause
Think back to the sandbox. Something gets broken, a parent asks who did it, and every sibling points at someone else. Kellie Andrews says most organizations still investigate incidents the same way, and that the who is the least useful place to start.
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 dig into systems thinking, how to write an investigation report leaders will actually read, and the link between safety and profitability.
Kellie’s path into safety began in an air traffic control tower with the Australian Air Force, where she worked as an officer and controller. She found tower training hard and radar easy, and three months after she was endorsed, the job finally made sense to her. Realizing she had gotten through training without truly understanding it changed how she trained others. In her mid-twenties she was leading training, issuing licenses and investigating operational incidents as one of the youngest leaders in her unit.
A mentor’s advice to say yes to opportunity took her to the UAE, where she worked with controllers from around the world. When the organization stood up a safety team of just two people, she volunteered, and she soon became its lead investigator. From there she joined the Dubai Civil Aviation Authority as an inspector, working on drone integration and even unmanned air taxis, then moved to Dubai Airports to help build a new safety system. In 2021 she crossed over into rail in the US.
Inside this episode:
Kellie describes investigation as following a thread. You keep a broad, open mind, find the thread, pull on it and go down the rabbit hole. Along the way you ask whether the rules existed and whether they were good, what systems the worker was managing at once, and whether the equipment was maintained. The answers form a web of causal factors rather than a straight line from A to B. For organizations still building their culture, she avoids root cause language that lets people point elsewhere, and she is deliberate about every word.
Her reports follow the same logic. “Investigation reports are not novels,” she says. “They’re like a science report.” Observations and analysis prove the case, and the findings, contributing factors and recommendations are written so anyone can act on them. None of that works without trust. People are being asked to hand over their records, so she makes it clear that where the investigation finds good practice, it will highlight that too.
She is just as direct about the business case. The brain likes to be efficient, so when a shortcut works, it keeps getting used. Investigations show where that is happening and how to bring performance back up to the bar. “Safe systems are profitable systems,” Kellie says, and a good place to see it is an operation’s cost of damage and the labor hours spent fixing things.
You will also hear why her first piece of advice to investigators is “don’t race to be first, race to be right,” how an investigation into a field incident can lead to supply chain and staffing decisions, and why she believes knowing when to stop digging is a skill too. She closes with advice for anyone early in their safety career: own your mistakes, don’t dwell on them, and keep moving forward.
If you investigate incidents, run a safety program, or want your team to stop asking who and start asking why, this one is worth the listen.
Kellie is on LinkedIn, and you can learn more about Keolis on their website.

