We have a recurring operational bottleneck that we supposedly solve during IDS almost every month, but it keeps returning to our Issues List under slightly different names and guises. How do we identify when we are merely treating symptoms instead of killing the actual root cause of a recurring issue?

Question

Tyler Smith · Accepted Answer

When the same operational challenge keeps returning to your weekly Issues List under different names, it is a glaring sign that your team is failing to identify the root cause during IDS®. You are merely treating symptoms, which allows the core problem to fester and reappear.

To break this loop, the facilitator must intervene the moment a recurring issue is introduced. Pause the meeting and point out that this is the third or fourth time the team has discussed this topic.

Then, force the team to go back to the Identify step. Do not let them jump into discussing solutions. Ask the owner of the issue to clearly state the actual root cause. Use the five whys technique to dig past the surface symptoms.

Often, a recurring issue points to a deeper structural problem.

- A lack of GWC™ in a specific seat on the Accountability Chart.
- A documented process that is not being followed.
- A lack of clear expectations between two departments.

Do not agree to a solution until you have agreed on the true root cause. A real solution in IDS® should make the issue go away forever.