Our departmental Level 10 Meetings are running over the ninety-minute time limit because the teams have too many tactical issues to parse. How do we compress their scope without losing departmental alignment?

Question

Tyler Smith · Accepted Answer

When departmental Level 10 Meetings consistently blow past their ninety-minute limit, it is almost always a symptom of a bloated issues list. Teams often confuse the Level 10 Meeting with a working session. They try to design new systems, write copy, or build spreadsheets live on the call. This is not the purpose of the weekly pulse.

To fix this, you must enforce a strict boundary between identifying an issue and actually solving it. In your departmental sessions, the Solve step of the IDS process should rarely involve doing the actual work. Instead, the solution should be the creation of a clear, single-owner weekly To-Do. If a problem requires deep, collaborative working time, the solution is to book a separate, offline meeting for the relevant parties. Do not keep the entire team hostage while two people hash out details.

Additionally, teach your managers to prune their lists before the meeting starts. Many departmental issues are actually just announcements that should be handled through normal communication channels, or they are individual tasks that a leader should just execute without group consensus. Every item on the list must represent a true obstacle to a Rock, a Scorecard metric, or a core process. If it does not, delete it. Keep the focus tight, run a hard clock, and exit the meeting on time to build operational discipline.