Respond non-punitively to mistakes

When someone brings you a problem or mistake, make your first move curiosity, not blame.

Why it works

Teams learn what to withhold from leaders by watching what happens when someone reports a problem. A single punitive response to an honest report teaches the team that bad news is punished — so future bad news is concealed until it is worse. This is how avoidable catastrophes (medical errors, financial blow-ups) accumulate undetected. Non-punitive response signals that the information is valued more than the blame.

How to do it

1. When someone brings a mistake, start with: "Thanks for telling me — walk me through what happened."
2. Separate the error analysis ("how did this happen?") from any consequences discussion, and do the analysis first.
3. Ask what they would do differently and what the team could learn — frame it as data.
4. Publicly acknowledge when someone’s candor about a problem led to a better outcome.

Evidence

Edmondson’s hospital study found teams with higher psychological safety reported more errors — not because they made more, but because they reported them. This is the core empirical case for non-punitive response as a learning mechanism. (observational)

The relationship between safety and error reporting is correlational. Causality is supported by theory and consistent across settings, but direct causal trials are limited.

Sources

• Edmondson (1996), "Learning from Mistakes Is Easier Said Than Done," Journal of Applied Behavioral Science

Common mistake

Saying "we don’t blame" while visibly becoming short or cold when problems surface — teams read affect, not statements, and a single frosty response can override months of stated policy.