When prioritizing the Issues List for IDS, our department heads each lobby aggressively for their own functional issues, leading to debates before we even start problem-solving. How do we break prioritization deadlocks cleanly?

Question

Tyler Smith · Accepted Answer

When department heads fight over which issue to solve first, they are operating with functional tunnel vision rather than enterprise leadership. The sales leader wants to fix lead flow, the operations leader wants to fix delivery capacity, and the finance leader wants to fix billing errors. If every leader only defends their own turf, your Level 10 Meeting™ stalls before IDS® begins.

The Integrator must eliminate lobbying and enforce an enterprise perspective. Under EOS®, the leadership team must wear their leadership team hats first, not their departmental hats.

First, stop asking the room what they want to tackle. The Integrator should evaluate the list against two clear criteria: company V/TO® goals and current quarterly Rocks. Ask the team: Which single issue on this board poses the greatest threat to hitting our company numbers and completing our Rocks this quarter?

Second, if the room cannot agree immediately, use a quick vote. Give every leader three votes to assign their top three priorities silently. Tally the votes in sixty seconds. The issues with the highest votes are numbers one, two, and three.

Third, if there is a tie, the Integrator makes the executive call. The Accountability Chart places the Integrator in charge of executing the business plan and running the meeting pulse. The Integrator does not need consensus on the order of priorities. They select issue number one, call the question, and move immediately into Identify.

Debating the order of the list is meeting waste. Pick the biggest fire, solve it completely, and move to the next.