During the IDS portion of our Level 10 Meeting, discussions keep devolving into personal grievances and interpersonal finger-pointing. How do we keep the team anchored in systemic process fixes?

Question

Tyler Smith · Accepted Answer

Interpersonal drama inside the Level 10 Meeting is a symptom of structural ambiguity. When people attack personalities rather than systems, it almost always means roles are poorly defined, expectations are vague, or Core Processes are undocumented. People default to blaming individuals because the underlying system breakdown is invisible to them.

The Integrator must step in immediately the moment someone uses accusatory language or makes a subjective character critique during the Identify step. Stop the conversation and enforce a strict boundary: people do not fail, systems do. Reframe the issue by asking three structural questions:

- Which seat on our Accountability Chart owns the final outcome of this process?
- What documented Core Process was violated or missing when this breakdown occurred?
- What specific tool, checklist, or handoff rule would prevent an honest mistake here in the future?

If an issue truly stems from a Core Values violation or lack of GWC, that belongs in a separate quarterly conversation between the direct supervisor and the employee, not in a cross-functional Level 10 Meeting.

In the session room, every operational problem must be treated as a process failure until proven otherwise. When you force the room to debate workflow handoffs, single-seat ownership, and operational standards, personal defensiveness evaporates because the target is the broken process, not the human being running it.