In short: Todd Conklin explains why blame stops organizations from learning from incidents. Meaningful learning starts by understanding how an incident became possible, then turning those insights into experiences that help frontline teams recognize risks and make safer decisions.
Todd Conklin describes a scene every safety leader knows.
A worker comes into the office, shuts the door and says: "I really screwed up. It's my fault. I know better. I should've locked it out. I didn't. I was in a hurry."
It's an honest moment. It can feel like the end of the conversation. According to Todd, it should be the start.
Todd spent around 30 years at Los Alamos National Laboratory and is one of the most respected voices in Human and Organizational Performance (HOP). When he sat down with Mousa Yassin on the Safety Heroes podcast, he explained why that confession, however sincere, is so often where the learning stops.
Self-blame closes the investigation early. Once a worker owns the mistake, nobody asks what set them up.
Todd's point is that taking the blame is often the easiest option for everyone. "It's oftentimes easier for the employee to take the blame, to take the guilt, because then they remove the guilt from their coworkers. They take their medicine faster." (32:45)
The file gets closed. The worker feels they've owned it. Everyone else is off the hook.
And almost nothing has been learned.
"If we stop there," Todd says, "all we've learned is that you screwed up. We want to understand how you got into a position where that failure was possible. How we set you up."
Those last four words move the question off the worker and onto the job: the plan, the equipment, the time pressure, the conditions on the day. That's where the useful answers are.
Blame gives an incident a tidy explanation, so the investigation stops before it reaches the conditions that made the failure possible.
Todd is blunt about it: "What worries me about blame is, what blame does is stop organizations from learning." (31:02)
Once an incident is explained as one person's mistake, the questions stop. The organization thinks it has found the problem. The conditions that set the worker up are still there, waiting for the next crew.
"The minute an organization stops learning," he adds, "then it's going backwards."
Anyone who has spent time with HOP will recognize this. Error is normal, and people respond to the conditions in front of them. When blame becomes the answer, a blame culture sets in. People get quieter about their mistakes, and the information you most need goes quiet with them.
Incidents can repeat when the lesson stays in the report and never reaches the crews doing similar work.
Even when an investigation does ask the right questions, there's a second gap.
Near the end of the episode, Todd made a point about speak-up programs: "It's not about the speak, it's about the up." (45:19) Telling workers to raise concerns is the easy half. The harder half is whether leaders have built a way to listen.
Todd was talking about speak-up programs, but his point travels well. With incidents, the report does go up. It's written, reviewed, filed and logged, and a safety alert goes around by email.
But the lesson rarely comes back down.
The people who most needed to understand what happened, the crews starting their next shift on a similar job, get a PDF or a toolbox-talk slide. They don't get the sequence of events or the decisions that made sense at the time. So the next crew is no wiser than the last, and a similar incident happens somewhere else.
This is one way repeat incidents happen. The investigation may have been thorough. The lesson just never reached the crews who needed it.
Learning from incidents works when crews can understand an incident from the inside: what the people involved saw, and why their decisions made sense at the time.
Put Todd's two points together and you get a fair test for any incident lesson. Does it take blame out of the room? And does it put the frontline inside the moment, so they understand why each decision made sense at the time?
It's a challenge we've been thinking about at Pixaera, too. How do you take what an organization has learned from an incident and make it meaningful to the people who could face similar conditions?
That's the thinking behind our Learning from Incidents (LFI) approach. Our expert-led AI engine rebuilds a real incident or near miss as a short, interactive experience, true to the site, hazards and PPE. Crews step into the moment and walk through how it unfolded, seeing the decisions the people involved faced and the conditions around them.
In a way, it's Todd's question asked across a whole workforce: how did we set them up? Because the scenes come from their own world, the reaction we're after is the one that makes a lesson stick. That could have been me.
Learner responses also show safety leaders how crews engage with the experience, where understanding may be limited and which controls might need more attention. The report proves it happened. LFI makes sure the lesson lands.
For more on how LFI turns a report into a lesson, read Turning reports into lessons that actually land.
Stop the repeat. Send us a real incident and we'll build it, so you can see your own lesson the way your crews would. See Learning from Incidents.
Learning from incidents is the process of turning what happened in an incident or near miss into lessons that change how people work. Done well, it focuses on the conditions that made the incident possible, not on who to blame, and makes sure the lesson reaches the frontline.
When an incident is put down to one person's mistake, the investigation usually stops there. As Todd Conklin explains, blame lets an organization believe it has found the problem, so the conditions that set the worker up go unexamined and can cause a repeat.
Often because the lesson never reaches the people doing similar work. Incident reports and safety alerts are written and filed, but crews rarely understand the sequence of events or the decisions involved, so the next crew is no better prepared.
A real incident report is uploaded and rebuilt as a short, interactive experience, true to the site, hazards and PPE. The client checks and approves it, then sends it to the right sites, roles or contractors. Every decision crews make is captured, showing whether the lesson landed.
Safety is about people, and the conversations around it matter.
Hosted by Mousa Yassin, Safety Heroes brings together HSE industry leaders, innovators, and experts to challenge conventional thinking, share real-world experiences, and explore what it really takes to make work safer.
From human behavior and safety culture to leadership, emerging technologies, and lessons learned on the frontline, each episode offers fresh perspectives and practical insights for anyone passionate about creating safer, smarter, and more resilient workplaces.
Join the conversation: