During our IDS® session, our team is quick to agree on weekly To-Dos, but we find ourselves dealing with the exact same operational issues three or four weeks later. How do we stop solving superficial symptoms and start identifying the true root causes during our Level 10 Meetings™?

Question

Tyler Smith · Accepted Answer

When the same issues keep reappearing on your Issues List, it is a clear sign that you are not actually practicing IDS®. You are identifying a symptom, skipping the deep digest phase, and jumping straight to a superficial solution. This is a common trap for action-oriented leadership teams who mistake speed for progress.

To break this cycle, the facilitator must slow the team down during the Identify phase. The person who raised the issue must state the problem in one clear sentence. From there, the team must ask why at least five times. For example, if the issue is that a client invoice was incorrect, do not just make a To-Do to credit the client. Ask why it was incorrect.

If the answer is that the sales team put the wrong data in the system, ask why they did that. If the system is too confusing, ask why we have not updated the system. Keep digging until you reach the underlying structural flaw or human resource issue. Only when you have agreed on the true root cause should you move to the Solve phase. The resulting To-Do must address that root cause, not just patch the immediate symptom. If you do this correctly, that issue will never show up on your list again.