Problems are not faults: blame the process, not the person

The idea

Most office errors happen because the process makes them easy: a form that accepts a missing field, two tools that disagree, a rule nobody owns, a step that depends on memory. Put someone else in the same seat with the same process, on a busy day, and sooner or later they make the same mistake. That is why Lean looks at the process first. It is also simply fairer.

There is a practical reason too. Reporting a friction means saying "this does not work", often about work you or a colleague did. If the last person who raised a problem was criticised for it, nobody raises the next one. The team still has its problems; it just stops knowing about them. Safe to speak up (a term Lean borrowed from the study of teams: psychological safety) is therefore not a nicety. It is what keeps the supply of problems flowing, and problems are what improvement runs on.

Rewording blame takes three steps.

1. Say what happened, as a fact, without a name: "the invoice was paid twice", not "Sam paid it twice".
2. Ask what in the process allowed it: "the system accepts a second invoice with the same number from the same supplier".
3. Name the change that would make it hard for anyone: "warn on a duplicate invoice number at entry".

More rewordings:

• "She always forgets to update the tracker" becomes "the tracker is updated by hand after the work, so it falls behind on busy days".
• "Sales never fill in the form properly" becomes "the form can be sent without the billing contact".
• "IT is slow" becomes "access requests have no target date and wait in one general queue".

What no blame is not.

• Not "nobody is responsible". People still own countermeasures and standards. Owning a fix is different from being blamed for a problem.
• Not pretending nothing happened. You can say a step was missed. The next question is what let it be missed.
• Not about rare deliberate wrongdoing. That is handled by other means. Everyday frictions are not misconduct, and treating every error as if it might be stops people reporting.

Leads set the tone with their first reaction to bad news. Thank people for raising problems, above all their own mistakes. Meet a reverted change with curiosity. Say "we" and "the process". What happens the first time someone reports a problem decides whether there is a second time.

Common mistakes

• Hidden blame. "Some people" or "a certain team" still points at people, just without names.
• Confusing no blame with no ownership. Someone still owns the fix.
• Asking for openness, then reacting with frustration. People believe the reaction, not the request.

Words to know

• Safe to speak up (often called psychological safety): people in a team expect that raising a problem, a mistake or a doubt will not be punished.
• Ask what, not who (in Lean: blame-free problem solving): tracing a problem to the process that allowed it.