Fix the system, not the person

People make mistakes. Some mistakes are personal. Some are caused by a broken process. A mature team learns to tell the difference before it assigns fault.

Ask about the system first

When a problem happens, run through the system questions before the people questions:

• Was the request clear?
• Was the deadline clear?
• Was the owner clear?
• Was there a working process?
• Did the tools work?
• Was the team overloaded?
• Was there a handoff problem?
• Was a decision missing?

If the same problem happens more than once, stop treating it as individual error and treat it as a system signal.

Old way vs. better way

A delayed order:

Old way:

Who messed this up?

Better way:

Where did the order get stuck? Was the status visible? Who owned the next step? Did anyone know it was blocked? What change would make this easier to catch next time?

The old question produces defensiveness and hidden risk. The better questions produce facts and a fix.

This is not “no accountability”

This is the part people get wrong, so be clear about it: fixing the process first does not remove personal accountability.

If someone lies, hides risk, ignores clear steps, or repeats the same issue without changing, that must be addressed directly. The rule is simply about sequence: understand the facts first, then decide whether this was a system gap or a personal one.

Try it on real work

Take a recent problem and write the escalation as facts: what happened, where it stuck, the impact, the options, and the recommended next step — not who to blame. The Issue Escalation template structures exactly that.