We keep resolving the same delivery bottleneck or customer churn issue during weekly IDS, but it reappears under a different name three weeks later. How do we dig past the operational noise to find the root architectural issue?

Question

Tyler Smith · Accepted Answer

When an issue resurfaces repeatedly, your team is not solving the root problem during IDS. You are treating the visible friction because it is easier and less uncomfortable to address than the structural failure underneath.

To break this cycle, the person running the Level 10 Meeting must stop the team from jumping into solve mode within the first thirty seconds. Demand clarity on the Identify step. Ask three direct questions before anyone proposes a solution:

- Whose seat on the Accountability Chart owns the final outcome of this process?
- Is this a people issue where someone lacks GWC, or is this a broken process step that relies on tribal memory?
- What specific metric on our Scorecard would permanently normalize if this issue were truly dead?

Most operational churn comes down to one of two realities: either the process is not documented and Followed by All, or the seat owner lacks the capacity or desire to hold their people accountable. When you name the person or the missing process step out loud, the room often gets quiet. That silence means you finally hit the real issue. Solve that structural problem once, assign a single owner and a hard due date to the To-Do, and the symptom disappears for good.