# ⇄ If being wrong costs status, nobody will be wrong out loud
The mindset · system · https://build-here.africa/book/chapters/01-10-if-being-wrong-costs-status-nobody-will-be-wrong-out-loud.html

## What you are asking for

> "Flag mistakes early enough for us to react."

You want problems to surface, including when the person who sees them took part in the decision.

## What the system hears

> "What will happen to me when I say what happened?"

## What that produces

Every report is a test. The team watches what happens to the person who spoke up. If they lose status, get taken off the subject, or become "the one who broke it", the next ones stay quiet. You will learn about your mistakes from your customers.

More mistakes reported is often proof that reporting has become safe. Watch the delay between the mistake and the alert above all: that is what tells you whether the system works.

A mistake almost always reveals something other than a person: an ambiguous instruction, a check nobody could run, too heavy a load. Look for that first. And always keep the person who raised the alert separate from what caused the problem.

Lead by example. Tell the story of one of your own mistakes, with the reasoning and the fix. It is the fastest proof that saying "I got it wrong" costs nothing here.

## The decision

On the next report, ask for two facts, not for someone to blame: the effect on the customer's side, and when it was noticed. Then look for what has to be protected and who can act. Thank the person, in front of the people whose opinion matters to them.

Keep the analysis of the facts out of individual assessment. After the review, check that the action decided was carried out, and ask the person whether they would report again.

## To discuss

On a recent incident, how long passed between the mistake and the alert?