The Easy Target Is the Person
Something goes wrong. A deadline slips. A form is filled out wrong. A customer complains.
The first reaction is predictable. Who messed up?
Blame feels fast. It feels decisive. It feels like leadership.
It is usually wrong.
Most repeated mistakes are not talent problems. They are system problems.
A study by the American Society for Quality found that over 85% of operational failures are tied to process issues, not individual negligence. That means most errors are predictable. And preventable.
If five smart people make the same mistake, the issue is not intelligence. It is clarity.
Why Blame Fails
Blame Hides the Root Cause
When you blame a person, you stop looking deeper. You fix the surface.
You retrain them. You warn them. You move on.
The same mistake shows up again.
In many regulated industries, recurring errors are tied to unclear documentation, confusing templates, or vague ownership. Not bad employees.
Paul Arrendell has seen this firsthand in global quality operations.
“We had a review step that kept failing audits,” he said. “At first, we thought the team wasn’t paying attention. When we walked the process, we found the checklist didn’t match the actual workflow.”
The people were doing their best. The system was broken.
The Cost of Blame Culture
Blame does more than miss the root cause. It creates fear.
- Gallup reports that only 3 in 10 employees strongly agree they can speak up about mistakes without fear.
- A Harvard Business School study found that teams with low psychological safety report fewer errors, not because they have fewer errors, but because they hide them.
- Companies with strong process discipline report up to 25% higher productivity than those relying on reactive fixes.
- McKinsey estimates process inefficiency costs organisations 20–30% of annual revenue.
Fear slows improvement. Hidden mistakes grow.
If your team is afraid to surface issues, your system is already at risk.
What Process Thinking Looks Like
Step 1: Assume the System Failed First
When something breaks, ask:
What in the process allowed this to happen?
Do not ask who failed. Ask what step failed.
Did ownership shift?
Was the instruction clear?
Was the template current?
Did two tools conflict?
Start there.
Step 2: Walk the Real Workflow
Most written processes look clean. Real workflows are messy.
Shadow the task. Watch how it actually happens.
Where do people hesitate?
Where do they improvise?
Where do they skip steps?
Those moments reveal system weakness.
As Arrendell once put it, “If someone has to create a workaround to survive the process, the workaround isn’t the problem. The process is.”
Common Process Weaknesses
Vague Ownership
“The team handles it” is not ownership.
Every step needs one accountable name. Not three. Not zero. One.
If something fails and no one knows who owned it, the system invited confusion.
Outdated Tools
Old templates. Conflicting versions. Different formats across teams.
This creates errors even when people try to follow the rules.
Standardise. Lock versions. Archive the old.
Missing Feedback Loops
If you never review where work stalls, you never improve.
Teams should review friction monthly. What slowed us down? What confused us? What got reworked?
Fix one thing. Repeat.
Replace Blame with a Simple Audit
Here is a fast, practical method.
1. Write Down the Process
List every step as it actually happens. Not the official version. The real one.
2. Identify Repeated Errors
Where do mistakes cluster? Which step produces the most confusion?
3. Ask “Why” Three Times
Example:
The report was wrong.
Why? The data field was empty.
Why? The form didn’t require it.
Why? The template was outdated.
The problem is not the person. It is the template.
4. Fix One Structural Issue
Change the template. Clarify the step. Assign ownership. Add a checkpoint.
Test it. Monitor it. Improve again if needed.
A Real-World Example
In one global operation, multiple sites were submitting slightly different compliance reports. Audits flagged inconsistencies.
Leadership initially blamed local teams for carelessness.
Instead of escalating discipline, they reviewed the process.
They discovered each region had modified the master form slightly over time. Small changes. No alignment.
“Everyone thought they were improving it,” Arrendell recalled. “What they created was five versions of the truth.”
The fix was simple. One standard form. Clear revision control. A single update channel.
Errors dropped. Audit prep became smoother. No reprimands needed.
Build a Process-First Culture
Reward Reporting, Not Hiding
If someone surfaces a flaw in the system, thank them.
Do not ask why they did not catch it sooner. Ask what allowed it to slip.
Separate Accountability from Blame
Accountability means owning outcomes and fixing root causes. Blame means punishing symptoms.
The difference matters.
Train for Systems Thinking
Teach teams to ask:
- Is this repeatable?
- Is ownership clear?
- Is the instruction precise?
- Would a new hire understand this step?
If the answer is no, refine the system.
When It Is a People Issue
Not every failure is structural. Sometimes behaviour needs correction.
But confirm the process first.
If the system is clear, documented, and supported—and someone still ignores it—then address performance.
Do not reverse that order.
Final Thought
Blame is quick. Process improvement is steady.
Quick reactions feel strong. Structural fixes create strength.
If the same issue repeats, stop pointing. Start mapping.
“People rarely wake up planning to fail,” Paul Arrendell has said in discussions about quality culture. “If the mistake keeps happening, the system made it easy.”
Make the right action easier than the wrong one.
Fix the process.
The results will follow.
