The same operational problem keeps reappearing on our Level 10 Issues List every three or four weeks under slightly different names, even though we supposedly solved it during IDS previously. How do we break this cycle of recycled issues?

Question

Tyler Smith · Accepted Answer

When an issue keeps returning to your Level 10 Issues List, your team is not solving problems during IDS. You are treating surface symptoms, kicking the can down the road, or assigning superficial To-Dos that give the illusion of progress without fixing the core breakdown.

This breakdown almost always happens during the Identify step of IDS. Teams rush to Discuss and Solve because debate feels productive, but they never isolate the true root cause. To stop an issue from recycling, the Integrator must implement a firm operational rule: if a problem returns to the list a second time, the team is prohibited from discussing previous solutions.

Instead, restart the process from scratch using the Five Whys. Strip away the immediate drama and ask why the breakdown occurred until you uncover the structural flaw. Recurring issues almost always point to one of three failures: an Accountability Chart issue where ownership is vague, a broken or undocumented core process, or a personnel issue where an individual lacks GWC for their seat.

Once the root cause is uncovered, verify that the resulting To-Do is structural rather than cosmetic. Assigning someone to apologize to an unhappy customer is a cosmetic fix. Redesigning the quality assurance checklist and retraining the department is a structural fix. Track the structural fix closely over the next 30 days to ensure the issue is permanently killed.