We have rolled out Level 10 Meetings to our departmental teams, but their meetings are turning into long-winded status updates where everyone just reports what they are working on. How do we pull them back to rapid operational execution?

Question

Tyler Smith · Accepted Answer

When you push the Level 10 Meeting™ down to your departmental teams, their natural instinct is to fall back into comfortable habits. They will turn the ninety minutes into a round-robin status update where each person lists their daily activities to prove they are busy. This completely destroys the value of the meeting pulse. A Level 10 Meeting is designed to solve problems, not to serve as a status report.

To break this habit, you must teach your departmental teams to leverage their Scorecard and their weekly to-do list to show status. The first twenty-five minutes of the meeting are purely for reporting. If a metric is on track, if a Rock is on track, and if a to-do is done, there is absolutely nothing to talk about. There is no need for team members to explain how they did it or give background context.

The facilitator must aggressively cut off anyone who begins to report details during the review segments. If a team member starts explaining why a task was difficult, the facilitator must say, is it done, yes or no? If the answer is no, it immediately drops to the Issues List.

By keeping the reporting segments incredibly brief and binary, you force the team to spend sixty minutes of the meeting in the IDS® portion. This is where real operational execution happens. Train your managers to understand that the true value of their departmental meeting is solving the obstacles that are blocking their weekly metrics and Rocks, not discussing routine activities.