In our Level 10 Meetings, issues brought to the table are almost always vague emotional complaints like poor interdepartmental communication or low team morale. How does an Integrator force the room to IDS the real operational breakdown behind these feelings?

Question

Tyler Smith · Accepted Answer

Vague emotional labels like poor communication or bad morale are never the real issue. They are symptoms of undefined processes, broken accountability, or unaddressed personnel mismatches. An Integrator must reject these generic entries before the room wastes twenty minutes talking in circles.

When a team member enters bad communication on the Issues List, the Integrator must demand an exact operational example before opening IDS. Use this line of questioning:
- What specific project, client, or financial deliverable stalled because of this?
- Who was the person accountable on the Accountability Chart, and what specific standard did they fail to meet?
- Which step in our documented Core Process was skipped or mismanaged?

If the issue owner cannot point to a specific breakdown, an accountable seat, or a tangible operational failure, the item is removed from the list until they can. Communication problems usually boil down to one of three root causes: two seats have overlapping responsibilities on the Accountability Chart, a handoff between departments lacks a clear binary deliverable, or a team member does not GWC their role and avoids hard conversations.

Once the issue is reframed from feelings to operational reality, the team can use IDS to solve it permanently. You are not trying to make everyone feel better in the abstract. You are identifying the missing standard, clarifying seat roles, or updating a core process so the breakdown cannot happen again. That is how you turn fuzzy frustration into clean operational traction.