How can an Integrator identify when an outspoken leader is manufacturing surface issues during IDS just to distract the leadership team from operational failures in their own department?

Question

Tyler Smith · Accepted Answer

Defensive leaders often use the Issues List as smoke. When their department is slipping, they flood the agenda with minor cross-functional annoyances, external market conditions, or process complaints about other teams. This keeps the leadership team busy solving procedural noise while the real fire burns unaddressed.

An experienced Integrator spots this pattern by watching the intersection of the Scorecard and the Issues List.
- Track issue origination. If a department head consistently logs issues pointing fingers at peers while their own weekly measurables are red, reject the distraction. Move their missed measurable to the top of the IDS list first.
- Interrogate the Identify step relentlessly. When this leader introduces an issue, do not allow the room to discuss solutions. Force the owner to state the problem in one clear sentence: who, what, and the quantifiable operational cost. If they spend three minutes framing context and attributing blame, cut them off and demand the root cause.
- Require departmental accountability before corporate intervention. If the issue is something the leader has the authority and seat to fix internally, kick it off the leadership team Issues List and direct them to solve it inside their departmental Level 10 Meeting.

The Level 10 Meeting is built to solve root causes, not provide airtime for corporate politics. Keep the team focused on hard metrics and cold facts. When you remove their ability to posture, underperforming leaders are forced to fix their seat or exit the business.