During IDS, our team often brings operational bottleneck issues to the table that are actually masked personnel failures where someone lacks GWC. How do we peel back the operational symptom to expose the true human accountability issue without turning the meeting into an ambush?
Teams naturally prefer to blame vague process failures or poor communication rather than confront a peer who is failing in their seat. When an operational issue surfaces repeatedly on your Issues List, look past the workflow and test the human seat.
Use this simple diagnostic during the Identify step: if our highest-performing team member were executing this exact workflow, would the system still break down? If the answer is no, you do not have a process breakdown. You have an Accountability Chart or GWC issue.
To raise this without creating an ambush, strip emotion and personality out of the conversation. Reframe the issue around the Accountability Chart rather than personal critique. Have the Integrator read aloud the five major roles defined for that seat. Ask the team whether the seat is properly designed to deliver the outcome or if the execution of those roles is breaking down.
Give the person sitting in that seat the floor first by asking directly: looking at your five roles, where do you feel the breakdown is occurring, and do you feel you have the capacity and tools to own this fully? Most leaders who are struggling with GWC will openly admit where they are stuck when the conversation centers on role clarity and seat capacity rather than personal attack.
Category: EOS Implementation