When our leadership team reviews an Issues List with forty items, we spend five to ten minutes debating and voting on which issues should be numbers 1, 2, and 3. How do we prioritize IDS issues quickly without consensus paralysis?

Question

Tyler Smith · Accepted Answer

Spending ten minutes debating what to solve is pure meeting waste. When teams run a democratic voting process on an Issues List, they burn cognitive energy on administrative ranking instead of actually solving root problems.

The Integrator must take ownership of issue prioritization. EOS is not a democracy, and the Level 10 Meeting agenda is not an open committee.

Follow this sixty-second protocol to lock in your top three issues.

First, before opening the floor, the Integrator scans the list against current quarterly Rocks and Scorecard health. The Integrator looks for the issues that represent the greatest systemic threat to company goals or cash flow.

Second, the Integrator unilaterally proposes the top three items: Team, our top three today are number 4 on billing errors, number 12 on supply chain lead times, and number 22 on technician turnover. Does anyone have a compelling operational reason why a different issue must supersede these three right now?

This shifts the burden of proof. Instead of five people lobbying for their pet topics, the room accepts the Integrator's list unless someone can demonstrate an immediate, catastrophic operational emergency that takes precedence. If a team member objects, the Integrator allows sixty seconds of rationale, makes the final executive call, and immediately begins Identify on issue number one.

Stop voting. Prioritize by executive clarity, tackle the most painful problem first, and let the rest of the list wait.