During our Level 10 Meetings, our team repeatedly brings operational headaches to IDS that turn out to be symptoms of a leader who lacks GWC for their seat. How do we shift the IDS conversation from the surface mistake to the real personnel issue without causing defensive blowback?

Question

Tyler Smith · Accepted Answer

When an operational breakdown shows up on your weekly Issues List, the natural instinct is to dissect the operational symptom. Leaders debate software glitches, communication gaps, or bad customer behavior. If the same type of operational breakdown repeats under different names, you are not dealing with a process problem. You are dealing with an accountability problem.

To move the conversation from the symptom to the root cause, the Integrator must redirect the room using the Accountability Chart. Ask one direct question: Which seat owns this outcome, and does the person sitting in that seat genuinely get it, want it, and have the capacity to do it?

This framing removes personal drama. You are not attacking a colleague; you are evaluating whether the seat has clear ownership and whether the person in it possesses GWC for those five core roles. If the room is analyzing a missed delivery deadline, stop arguing about the shipping vendor. Ask whether the Operations Leader has the capacity to anticipate vendor delays or if they lack the skill set to build supply redundancies.

If the answer is a GWC deficit, stop solving the day-to-day shipping fire drill during IDS. Solve the real issue: either coach that individual through the Three Strike Rule to fix the capacity gap, or begin the process of finding the right person for that seat. Solving operational symptoms while ignoring seat misalignment is the most expensive mistake a leadership team can make.