Skip to main content
All Writing
leadershiptrustcommunicationoperations management

Just Culture, Not Blame Culture: Why Your Safety Reporting System Isn't Getting the Reports You Need

Most teams claim psychological safety but still punish the people who report problems. Here's the Just Culture framework and how to respond to reports right.

August 7, 2026 · 3 min read  ·  Kestryl Edge

Just Culture, Not Blame Culture: Why Your Safety Reporting System Isn't Getting the Reports You Need

You say your team has psychological safety. Then someone files a near-miss report, and three weeks later they're quietly left off the next project, or their manager brings it up in a performance conversation "just for context." Nobody called it punishment. Everyone in the room knew what it was. And everyone who saw it now knows what to do next time: stop reporting.

Fewer reports is the warning sign

Every regulated operation assumes people will tell leadership about the near-misses, the almost-incidents, the moments where something could have gone wrong and didn't. That assumption holds only if reporting is safe in practice as well as on paper. Most safety-critical teams have the policy. Fewer have the practice. The gap shows up at the worst possible time: right before the incident that wasn't a near-miss. Culture starts with permission more than policy, and reporting is where that gets tested.

Just Culture as a framework

Aviation and nuclear power spent decades building a specific answer to this problem, called Just Culture. It draws a hard line between three categories of behavior and expects leaders to respond to each one differently.

Honest error is a mistake anyone in that role could have made under those conditions, with the preparation and information they had. At-risk behavior is a choice that increased risk, usually because the safer path was slower, harder, or less rewarded. Reckless behavior is a conscious disregard of a known, substantial risk. Treating all three the same, and punishing an honest mistake as hard as reckless disregard, is what kills reporting. People can no longer predict what happens when they raise their hand, so they stop raising it.

The decision your team is watching

When a report comes in, the question to answer is which of the three categories it falls into, and whether your response matches. An honest error gets a system fix and, ideally, public credit for surfacing it. At-risk behavior gets a direct conversation about why the safer path felt like the harder one, and what has to change so it doesn't. Reckless behavior gets a consequence, because letting it slide erodes the trust of everyone who made the harder, safer choice. Fixing the system first is the core of upstream accountability.

Most leaders who get this wrong aren't acting out of malice. They're inconsistent. They respond generously to a report on a good day and defensively to the same kind of report on a bad one, and their team learns to read the room instead of trusting the framework. Just Culture works only when it's applied the same way regardless of the leader's week and regardless of who filed the report. Giving people anonymous feedback channels helps while that consistency is being earned.

What it buys you

A safety or operations leader who runs this consistently won't see incidents drop overnight. What they get first is an accurate picture of what's happening on the floor, because people believe a report will be read as information and not as a confession. That picture is how you find a systemic risk before it finds you. The same dynamic applies when people hesitate to override a tool they suspect is wrong, which we cover in automation bias as a leadership problem.

If your near-miss numbers have been declining and nobody can explain why, don't start by asking whether your team got safer. Ask what happened, specifically, to the last three people who filed a report.


Kestryl Edge works with leaders who own safety, quality, or operations to build reporting cultures people actually trust. Learn how we work with organizations.


Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, trust, and how teams actually perform. Subscribe here.

Most leadership training happens without the leaders. Ours requires them.

Book a connection call