When our department heads run their departmental Level 10 Meetings, the sessions quickly devolve into passive project status updates where managers simply read lists of completed work rather than doing IDS. How do we force frontline teams to actually solve operational issues?

Question

Tyler Smith · Accepted Answer

Frontline managers often default to project updates because traditional corporate culture conditions people to prove they are working. A Level 10 Meeting is not a status meeting. It is a problem-solving pulse designed to remove friction from execution.

To fix this behavior, have your Integrator train departmental facilitators to enforce the structural purpose of the agenda:

- Enforce the reporting clock. The Scorecard, Rock review, Headlines, and To-Do list should consume no more than twenty-five minutes combined. Reporting sections are strictly binary. The only words permitted during Scorecard and Rock reviews are on track or off track. Explanations, backstories, and victory laps are cut off immediately.
- Treat an empty Issues List as a red flag. If a department shows up to IDS with only one or two issues, do not praise them. Probe them. No operational department runs without friction. If their list is empty, they are either protecting turf, afraid of conflict, or measuring the wrong Scorecard metrics.
- Reframe the facilitator role. The department head must stop acting as a judge receiving reports. Their job is to pull issues out of the team. If a supervisor mentions that a project took twice as long as expected, the facilitator must immediately say: That sounds like a capacity issue. Let us drop that to the list and solve it.

When frontline teams realize that thirty to sixty minutes of their meeting is reserved strictly for eliminating headaches rather than reciting status reports, engagement shifts from passive compliance to active ownership.