During our weekly Level 10 Meeting, our leadership team wastes ten to fifteen minutes of our IDS time arguing over which issues should be prioritized as number one, two, and three. How do we streamline issue prioritization so we can get straight to solving?
Spending fifteen minutes deciding what to talk about is meeting waste disguised as collaboration. Prioritization in the Level 10 Meeting is not meant to be a consensus-building workshop. It is a quick operational assessment to ensure the room tackles the most critical items first. When teams debate prioritization endlessly, it is usually because individuals are lobbying for their own department pet issues rather than focusing on the greatest threat or opportunity facing the business. To cut this down to sixty seconds, the Integrator must take control of the prioritization mechanism:
- Scan the list for company-wide impact. Scorecard metrics off-track and off-track quarterly Rocks automatically take precedence over general operational issues.
- The Integrator or facilitator nominates the top three issues based on organizational urgency, not departmental politics.
- The facilitator asks the room one simple question: does anyone strongly object to this order?
If a leader objects, they must make their case in ten seconds or less by stating how their issue poses an existential, customer-impacting, or financial risk that supersedes the proposed top three. The facilitator then makes a definitive call, sets the order, and immediately launches into issue number one. The leadership team must remember that prioritization does not mean the other issues disappear. It simply means you solve the most important thing first. If your team cannot agree on what is most critical, you have an alignment problem around your Vision and quarterly Rocks, not a meeting problem.
Category: Level 10 Meetings