28 October 2026 · 12 min read

Blame culture: why the best-rated teams report more mistakes

People hide a mistake once they have watched what happened to the last person who didn't.

That is most of what a blame culture is, and it is why the mistakes you hear about are the cheap ones.

The email Ayo has not sent

Ayo manages accounts at a firm where everyone knows whose desk is whose. On Thursday afternoon he scrolls back through the proposal he sent a client this morning and sees that the rate card is last year's. The price is lower than it should be. The client has not noticed. Nobody else has either.

He knows the fix. One short email today, "quick correction on the attached", and the client would shrug. He opens a new message and types the subject line. Then he remembers Monday's meeting, when Dani's mis-keyed delivery date came up and the director asked, pleasantly, "Who signed this off?" The room went very quiet. Everyone left knowing Dani's name. Nobody left knowing how the date had got through.

Ayo deletes the draft. He tells himself he will sort it out when the renewal comes round.

By then the client will hold a signed price, and a correction that would have cost nothing on Thursday will be a difficult call in the spring.

How many people hide mistakes at work?

45% of UK employees feel unable to raise a mistake or a risk at work, and 15% say they have made a preventable mistake because they felt unsafe speaking up (Mental Health First Aid England, The cost of workplace silence, February 2026). The survey spoke to 2,000 UK working adults.

The first figure is a mood. The second is a mistake that, by the respondent's own account, did not need to happen.

What causes a blame culture?

Amy Edmondson found that hospital teams rated best by their own staff reported more errors, not fewer, and read it as a sign that saying so was safe. She was careful about the limit: the paper itself says that errors made and errors detected cannot be told apart. From the outside, a team that reports nothing and a team that does nothing wrong look identical.

Ron Westrum's research on how organisations handle information gives the pattern a name. In what he calls a pathological culture, bad news is punished, so it stops travelling. His bureaucratic culture fails more politely: it is rule-oriented, and when something goes wrong it looks for justice rather than inquiry. Both describe how news moves. A blame culture is a problem with how news travels, dressed up as a question of right and wrong.

That is why it survives. Nobody running a blame culture thinks they are running one. They think they are holding people to account, and "who signed this off?" feels like rigour. It works more like an anaesthetic: once there is a name, the analysis stops, the room relaxes, and the cause is still sitting in the process for the next person. Nobody at Monday's meeting raised their voice. The director's question did the whole job in four words, because the first word of the first question teaches everyone what this team does with failure.

That is also why the cost lands where it does. A mistake said aloud on Thursday is an email. The same mistake found by someone else in the spring is an incident. The mistake is the same; it just ran unseen for longer.

The wider evidence points one way. Across 136 independent samples covering more than 22,000 people, psychological safety is linked with how well people perform their tasks (Frazier, Fainshmidt, Klinger, Pezeshkan and Vracheva, Personnel Psychology, 2017). In Edmondson's research, psychological safety is a shared belief that speaking up is safe. And in Google Cloud's State of DevOps report, teams with generative cultures had 30% higher organisational performance than those without, in research drawing on more than 36,000 professionals over nine years (DeBellis and Harvey, Google Cloud, October 2023). The report means by generative that people felt included and like they belonged on their team. These are links, not proofs, and they come from different kinds of work.

How to spot a blame culture in one meeting

You can usually hear it without asking anybody a question.

• The first question is "who". Lots of people can tell you whose mistake it was, and few can tell you how it happened.
• "How did this happen?" meets a long silence. People are working out what it is safe to know.
• Nobody mentions a near-miss. Nothing happened, so there was nothing to report, and the same mistake waits for a day when nobody catches it.
• People apologise where an analysis should be. "I broke it" closes the subject.
• Blame arrives quietly. A colleague's manager is copied into a reply, a review lists names, somebody asks a pointed "who approved this?".
• Some people keep private records. The screenshots and saved sign-offs are insurance.
• The finger points across teams. When something goes wrong at a boundary, the first instinct on every side is to look the other way.

How does a blame culture affect a team?

Dani pays first, and the bill is small enough to miss. By Friday she has a folder of sign-offs, saved in case. By the end of the month she has stopped volunteering for the awkward client, because that is the work where mistakes happen, and she has learned what a mistake earns. Nobody would call that a resignation. Her work is still good. It has simply got safer.

Then the team pays in information. A meta-analysis of 72 independent studies (4,795 groups, 17,279 people) found that information sharing within a team was positively related to team performance, and to cohesion, decision satisfaction and knowledge integration (Mesmer-Magnus and DeChurch, Journal of Applied Psychology, 2009). It is not a study of blame. But what a blame culture puts a price on is exactly that sharing, and the price goes up on the things a team most needs to hear.

The manager may pay most, and last. Near-misses are the cheapest lessons there are, failures that cost nothing if anyone dares to mention them, and a blame culture throws them away. So the next incident gets investigated on poorer evidence, for longer, by someone who honestly believes things were going well.

Does a no blame culture work?

There are two easy wrong answers.

The first is the sentence on the wall: "we learn from failure", or the starker "no blame". A no-blame slogan has a worse problem than being ignored. Everyone knows it is not quite true. James Reason's research on how organisations fail draws the line: honest mistakes get analysis, and a reckless choice is a different conversation. The true version of the slogan is longer than a poster, and the short version is a promise the first awkward Monday will break.

The second is the postmortem template. It is a good tool and it arrives late. By the time there is a form to fill in, the news has reached you, and how it reached you is what everyone saw. Blame lives earlier, in your face and your first sentence when someone says "that one was mine".

An independent listening exercise at a large hospital trust shows what a poster cannot reach. About three in four of the senior doctors who took part described fear of speaking up, of what follows, or doubt that anything would change (Transformation Partners in Health and Care, Medical voice: listening with purpose, July 2026). Fewer than one in five of the consultants and SAS doctors took part, so this speaks for people who chose to speak, not for the whole hospital. Still, look at the three fears. A poster can answer the first. The other two, what follows and whether anything would change, are answered only by what you do with the first piece of bad news you receive.

How to stop a blame culture: what to do tomorrow

None of this needs a product.

Thank first, then ask how

The next time someone brings you bad news, a missed date, a wrong figure, a check that quietly stopped running, make your first sentence "glad you caught it" and your second "walk me through what you saw." Leave any explaining of your own part until after. Edmondson's work gives the leader two jobs here, inviting people to speak and responding well when they do. The second is the one everyone is watching.

Go first, and say it as an event

This month, tell your team about one mistake of your own, as what happened rather than a confession: "my estimate assumed the supplier would deliver on time, and I knew that was uncertain when I gave it." No beating yourself up. Nobody will go first in a room where the person in charge has never been wrong.

Do not close the next review until one change has an owner and a date

"Be more careful" is blame in a helpful disguise, because it says the problem was a person. Ask how it happens here, not who did it, and keep asking until the answer is something in the process. Then finish on a change somebody owns.

All three fail the same way. They rely on you doing them on the Thursday when you are tired and the director is in the room.

Four questions about blame and accountability

What is the difference between blame and accountability?

Blame asks whose fault it was, and accountability asks who owns the fix. The same people stay responsible in both. What changes is what owning something gets them: in a blame culture a reputation, and in an accountable one a change to the process with their name on it. A team can drop the first and keep every bit of the second.

What if someone really was reckless?

Then it is a different conversation, and you should have it. Reason's line runs between honest mistakes, which get analysis, and a reckless choice, such as knowingly ignoring a clear and serious risk. Say where that line sits before you need it, so that the first real case does not become the excuse for going back to hunting names.

Should a manager apologise for their own mistake?

Yes, where the mistake was one of competence and it was yours. In two studies of how trust is repaired after an alleged violation, trust recovered more when the mistrusted party apologised for a violation about competence but denied culpability for one about integrity, and when the response matched the evidence that came later: an apology if guilt was later shown, a denial if innocence was (Kim, Ferrin, Cooper and Dirks, Journal of Applied Psychology, 2004).

Will more mistakes get reported if blame stops?

They should, and that is the sign to look for rather than the problem to fix. A rising number of near-miss reports means information is arriving before the damage does, which is how to read Edmondson's hospital teams too. It can look like things getting worse, which is usually when a director starts asking who signed what off.

How MeaningFuel helps with blame culture

Accountability and Trust, one insight at a time

A company chooses the values and skills it wants to work on, and each working day everyone gets one short insight on one of them. Blame culture is a problem, so it cannot be chosen for the daily culture. Accountability and Trust can, and so can Courage as a value and Continuous Improvement as a skill. In an ordinary week a reader might meet a line on owning a mistake on Tuesday and one on the cost of staying quiet on Friday, with nothing having gone wrong. A team that only talks about failure during a failure has picked the worst day for it.

Learning from Mistakes

Learning from Mistakes is the module for a team that has noticed its mistakes going quiet. It is a short course of daily lessons. Booked for a team, it invites the people on it, and those who join get one short lesson each working day: a small scene, a move, a check and an action. In one lesson a colleague reports a failure with "I broke it", and the move is to say what happened instead, "the step ran early and nothing stopped it", because a description invites analysis where a confession ends it.

Another lesson goes after near-misses: what almost happened, what caught it, and what would make it get caught every time instead of by luck. Near the end, the team agrees one small rule: when a conversation about something that went wrong opens with "who", anyone in the room may say "how first", lightly, and it counts. The module draws on research by Ron Westrum, Amy Edmondson and James Reason, and borrows five whys, a widely used root-cause method, along the way.

What Insights would and would not tell you

Insights shows how much of a team takes part and how the insights land, pooled, with nobody named. On this problem "nobody named" is the part that counts: a lead who could see who answered what would be the director asking "who signed this off?" with better data. So a lead sees that the team is doing the module, never anyone's answers. And Insights will not tell you how many mistakes are being hidden, because nothing can. A team can take part every morning and still delete the draft.

What it does not do

It promises no outcome. What it does is put the habit in front of everyone every working day, so that "how first" stops depending on one manager's memory and mood. If the person asking "who" sits above the team, ten lessons for the team will not reach them unless they are in it too, and the questions page says what a module asks of whoever leads it.

Before the draft is deleted

A firm like Ayo's looks fine on paper: little gets reported, so little seems to go wrong.

Ayo's email is still a draft. Whether it goes depends on what he saw happen to Dani, and on what the next person who brings you bad news sees happen to them.

• Blame Culture
• Psychological Safety
• Learning from Mistakes
• Team Leadership
• Workplace Culture