ControlStandard.Tools Get a free report

Glossary

Just Culture

A just culture is an organisational approach to error that holds people accountable for reckless choices while treating honest mistakes as a signal to fix the system, not the person. Popularised by Sidney Dekker and David Marx, it replaces "who messed up?" with "what let this happen?" — so people report problems instead of hiding them.

A just culture is an approach to managing error that balances accountability with learning. It accepts that competent people make honest mistakes inside imperfect systems, and that punishing those mistakes simply teaches everyone to stop reporting them. The concept was popularised by safety scientist Sidney Dekker, whose book Just Culture (2007) framed it as a question of justice, and by David Marx, whose 2001 report for the US Federal Aviation Administration set out the now-standard distinction between three kinds of behaviour: human error (a slip), at-risk behaviour (a drift into unsafe shortcuts) and reckless behaviour (a conscious disregard of an obvious risk).12

The practical move is to treat each differently. Console human error and fix the system that allowed it; coach at-risk behaviour back on track; and hold reckless behaviour to account. What you do not do is punish an honest mistake, because that only buys silence.

Why it matters

A just culture matters because it determines whether problems surface early or stay hidden until they detonate. In a blame culture, the rational response to a mistake is concealment, so the organisation is blind to its own weak points. In a just culture, reporting is cheap and routine, which means the root cause of a recurring problem becomes visible long before it becomes expensive. The aim is not to be soft; it is to be accurate about where the fault really lies — usually in the system, occasionally in a choice.

Blameless, but accountable

The Control Standard uses a sharper phrasing of the same idea: blameless about people, demanding about system learning. A serious review does not let anyone off the hook — it redirects responsibility to the lever most likely to produce a different outcome next time, which is almost always a change to the mechanism rather than a change of attitude. When a problem keeps recurring, that is a signal the system needs work, not that the team needs to "be more careful". Deciding whether a repeated pain is worth a deliberate fix is exactly what the "Should you automate this?" diagnostic helps you judge.

The same instinct underpins crew resource management: make it safe for the person who sees the problem to say so.

  1. David Marx, Patient Safety and the "Just Culture": A Primer for Health Care Executives (Columbia University / MERS-TM, 2001) — psnet.ahrq.gov. ↩

  2. Sidney Dekker, Just Culture: Balancing Safety and Accountability (Ashgate, 2007) — sidneydekker.com. ↩

Frequently asked

Is a just culture the same as a no-blame culture?
No. A no-blame culture excuses everything, including reckless behaviour, which removes any sense of accountability. A just culture draws a line: honest mistakes and at-risk behaviour are treated as system problems to learn from, while a genuinely reckless disregard for an obvious risk is still answerable. The point is fairness, not the absence of consequences.
Who came up with just culture?
The idea grew out of aviation and healthcare safety science. James Reason's work on human error laid the groundwork, and the term was popularised by Sidney Dekker (Just Culture, 2007) and David Marx, whose 2001 report for the US Federal Aviation Administration set out the distinction between human error, at-risk behaviour and reckless behaviour.
How do you build a just culture at work?
Start by separating two questions every time something goes wrong: what in the system allowed this, and was anyone's behaviour reckless? Most errors answer the first question, not the second. Make reporting safe and routine, respond to honest mistakes with a fix rather than a reprimand, and reserve sanction for genuine recklessness. A blameless after-action review is a practical starting ritual.
Why does blame backfire?
Blame teaches people to hide problems. If admitting a mistake gets you punished, the rational move is to stay quiet — so the organisation loses the early warnings it most needs and the same failure recurs unseen. A just culture lowers the cost of surfacing a problem, which is what makes the underlying weakness visible enough to fix.

Related

Term

After-Action Review (AAR)

An after-action review is a short, structured debrief that asks four questions: what was supposed to happen, what actually happened, why was there a difference, and what will we change? Originally a US Army practice, it turns experience into improvement — and works best when it's blameless but accountable.

 Term

Root Cause Analysis (RCA)

Root cause analysis (RCA) is a structured way to find the underlying cause of a problem — not just its symptoms — so a fix stops it coming back. It uses tools like the 5 Whys, fishbone diagrams and Pareto analysis to move from "what happened" to "why", and ends in a change with a named owner and a date.

 Term

Fishbone Diagram (Ishikawa)

A fishbone diagram — also called an Ishikawa or cause-and-effect diagram — is a visual tool that sorts the possible causes of a problem into categories, so a team can see every contributing factor at once instead of fixing the first thing they notice. Created by Kaoru Ishikawa, it is a staple of root-cause analysis.

 Term

Crew Resource Management (CRM)

Crew resource management is a set of team practices, born in aviation after a string of 1970s crashes, that uses every crew member's knowledge to prevent error. Its central idea is flattening the authority gradient: making it safe and expected for a junior person to challenge a senior one when they see something wrong.

← Back to the glossary