tyler-smith.com · Questions & Answers

When cascading Level 10 Meetings down to department managers, their sessions quickly devolve into venting sessions without resolutions. How do we teach middle managers to run pure IDS?

When you cascade the Level 10 Meeting™ down to departmental tiers, middle managers often turn the meeting into a sixty-minute complaining session. This happens because front-line supervisors know how to identify symptoms, but they lack the discipline to isolate root causes and agree on actionable next steps.

To transform departmental Level 10 Meetings into productive traction engines, the leadership team must enforce three ground rules for departmental IDS®:
- Own the issue: An issue cannot be added to the departmental Issues List simply to complain about another department or executive leadership. The person raising the issue must state what part of the problem falls within their seat's control and what specific outcome they want from the room.
- Separate the symptom from the cause: Middle managers usually bring emotional symptoms, like morale is low or clients are demanding. The meeting facilitator must immediately challenge that framing by asking what broken process, missed Scorecard measurable, or role confusion generated that outcome.
- Require a binary To-Do: Discussion must terminate as soon as the root cause is named. The facilitator must immediately ask: What is the next action, who owns it, and will it be done in seven days? If a discussion does not end in a clear To-Do assigned to one individual, the issue was not solved.

Have the company Integrator or a trained leadership team member sit in on the first three departmental Level 10 Meetings as an observer. Their only job is to blow the whistle when supervisors start venting instead of identifying root causes. Once middle managers taste the efficiency of solving problems rather than talking about them, the culture permanently shifts.

Category: EOS Implementation

← All questions