A press goes down in the middle of a run. Within an hour, the story has been told four times, and every version is different.
Quality says the parts were drifting before the stop, so it was a process problem. Process says the tooling was past due, so it was a maintenance problem. Maintenance says the cell was never released for the PM window, so it was a production problem. Production says they ran what Quality approved, so we are back to Quality.
The circle closes. Everyone has an answer. Nothing changes. By the next shift, the same failure is back on the board.
I have watched this happen in plants with great people, good intentions, and real technical talent. That is the part most leaders miss. The doom loop is not a character problem. It is a design problem. When you put committed people inside a system with undefined boundaries, deflection stops being a flaw and becomes the rational move.
Blame is a symptom of unclear interfaces
Most organizations are good at drawing boxes on an org chart. Very few are good at defining what happens in the space between the boxes.
That space between the boxes is where work actually fails. The handoff from Quality to Process. The release from Production to Maintenance. The confirmation back from Maintenance to the floor. Each one is an interface, and most of them are governed by assumption rather than agreement.
When an interface is undefined, two things are always true. First, the work falls through it. Second, no single person owns the fall. So when something breaks, every department can point to the gap and honestly say it was not theirs. They are not lying. The system never told them it was.
Deming made this point decades ago, and it still gets ignored on most floors. The overwhelming majority of problems come from the system, not the person operating inside it. If you keep replacing people and the failure keeps returning, the failure was never about the people.
Why your best people deflect
Here is the uncomfortable truth. The doom loop is strongest in organizations full of capable, conscientious people.
A weak performer deflects because they want to avoid work. A strong performer deflects because they are protecting a system they are already overextended inside. They know their lane is covered. They know the failure came from somewhere they do not control. So they defend their box, because defending it is the only thing the system has actually equipped them to do.
That is why “hold people more accountable” almost never breaks the loop. You can raise the temperature on a group of people who are each doing their defined job correctly, and all you will produce is faster, more defensive deflection. You have added pressure without adding ownership. The loop just spins quicker.
Breaking it: own the failure mode, not the department
The fix is not a better meeting or a sterner email. It is a structural change in how you assign ownership.
Stop assigning failures to departments. Start assigning recurring failure modes to a single named owner who carries it across the boundaries.
When a vacuum fault keeps recurring across multiple cells, it does not belong to Maintenance, or Process, or Production. It belongs to one person whose job is to drive that specific failure mode to zero, with the authority to pull the right people across every interface it touches. That person cannot deflect, because the failure is defined as theirs regardless of which box it started in.
A few principles that make this work in practice:
- Replace the question “who caused this” with “what in our system allowed this.”
- Define the handoff, not just the role.
- Give the owner authority that crosses lines.
- Make the recurring failures visible and singular.
What changes when the loop breaks
The first thing you notice is quiet. The defensive energy that used to fill every post-failure conversation has nowhere to go, because the question is no longer about fault. The owner is not asking who to blame. They are asking what to redesign.
The second thing you notice is speed. Failures that used to live on the board for weeks start closing, because someone finally has both the responsibility and the reach to close them.
Accountability is not something you demand from people. It is something you build into a system and then earn the right to expect. Design the interfaces. Name the owners. Give them the authority to cross the lines the failure already crosses.
Do that, and the loop stops spinning. The people were never the problem. The space between them was.
