Solve the Problem First: Why Sequence Matters in Operational Problem-Solving
You can solve the problem or determine who’s right. But you can’t always do both at the same time.
When something breaks in an operation, the natural reaction is often to start reconstructing the crime scene. Who missed it? Who made the wrong call? Who should have known? Those questions may eventually matter. The problem is the word eventually.
If a customer is waiting, material is stopped, a crew is idle, an order is wrong, or a supplier has failed, the first job is not to establish a verdict. The first job is to stabilize the operation.
Problem First
Operational problems have a clock attached to them. Every minute spent debating ownership while the problem is still active can add cost, delay, customer frustration, overtime, expedites, and another layer of confusion.
So start with a different set of questions: What needs to happen right now? What does the customer need? What is keeping the work from moving? Who has the information or authority to make the next decision? What can we safely contain while we investigate the rest?
This is not the same as ignoring root cause. In structured problem-solving, immediate containment and permanent corrective action are different jobs. Lean problem-solving similarly distinguishes rapid troubleshooting that restores an abnormal condition from deeper work that identifies causes and prevents recurrence.
Root Cause Second
Once the operation is stable, now ask why. Not the convenient why. Not the first explanation that points toward a person. Ask enough questions to understand the conditions that allowed the problem to happen.
Was the process unclear? Was the information late? Did the handoff fail? Was ownership ambiguous? Did someone have responsibility without authority? Did the system show inventory that was not actually usable? Did the supplier miss a commitment, or did we build a plan around an assumption that was never confirmed?
Those questions produce a very different conversation than “Who screwed up?” They also produce better data.
Accountability Without the Courtroom
None of this means accountability disappears. People own decisions. Standards matter. Repeated poor decisions need to be addressed. But accountability works better when it is based on facts gathered after the immediate pressure has been controlled.
There is also a leadership advantage to sequencing the conversation this way. If employees believe every operational problem begins with a search for the guilty party, they learn to protect themselves. Information slows down. Problems get softened before they travel upward. People spend energy proving why something was not their fault.
If the first question is “What do we need to do?”, people can focus on the work. Once the situation is stable, the team can examine what happened without pretending ownership does not matter.
Improvement Third
Finding the root cause is useful only if something changes. A problem-solving meeting that ends with “communicate better” has usually just renamed the problem.
The final questions should be practical: What changes in the process? Who owns that change? How will we know it worked? What should become standard work? Could the same failure happen somewhere else?
That is where a disruption becomes an improvement instead of merely becoming yesterday’s emergency.
The Sequence Is the Point
Problem first. Root cause second. Improvement third.
It is a simple sequence, but simple does not mean easy. Under pressure, organizations tend to compress all three conversations into one. The customer problem, the root-cause investigation, the accountability discussion, and the corrective action all collide in the same meeting.
Separating them creates clarity. Stabilize what is happening now. Understand why it happened. Then make the process stronger.
The next time something breaks, before asking who was right, ask a more useful question: What does the operation need from us right now?
Richard Enterprise LLC helps organizations improve supply chain, procurement, inventory, warehouse operations, and operating discipline through practical, measurable process improvement.



Comments