How do we prevent our departmental Level 10 Meetings™ from just becoming dry status update sessions where supervisors read lists instead of actually executing IDS®?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings™ often fall into the trap of becoming dry, repetitive status reports. This happens because front-line supervisors and team members are naturally wired to prove they are working rather than solving systemic problems. To keep departmental meetings highly dynamic, you must change the expectations of the team. First, enforce a strict rule that the Scorecard and Rock review are for reporting only. If a metric is off or a Rock is not on track, it immediately gets dropped to the Issues List. No explanations are allowed during the first phase of the meeting. This saves your time and energy for the IDS® portion. Second, look at Julie Zhuo's management pillars of purpose, people, and process. The purpose of a departmental meeting is not to please the manager, but to clear obstacles for the team. Ensure that the issues on the list represent real operational bottlenecks, not just minor task updates. Encourage your department heads to focus on the things that prevent them from hitting their numbers. Finally, make sure everyone in the room understands how to write a clear issue. Instead of writing general topics like shipping, they must write shipping delay on order five hundred. This forces the team to spend their energy solving the root cause rather than debating what the issue actually is. When you run your departmental meetings with this level of discipline, the team will look forward to the session because it actually helps them get their work done.