Our team spends twenty minutes arguing about which issue on our Level 10 Meeting Issues List is the most important, leaving us with barely enough time to IDS anything. How should the facilitator drive the issue prioritization process?

Question

Tyler Smith · Accepted Answer

Teams waste massive amounts of time during the sixty-minute IDS section simply trying to agree on where to start. When the facilitator asks the room what they want to tackle first, everyone lobbies for their own departmental headache, burning ten minutes on meta-debate before solving anything.

The EOS framework eliminates this with a swift prioritization protocol: identify issues 1, 2, and 3. The facilitator must own this process decisively.

Scan the Issues List and quickly propose the top three priorities based on company impact. The criteria should be obvious: items affecting revenue, client retention, Rock execution, or major operational bottlenecks come first. The facilitator states: I see Issue A, Issue B, and Issue C as our top three. Does anyone strongly disagree?

Notice the wording. Do not ask for full consensus. Ask if anyone has a compelling reason why another issue must take precedence. If a leader speaks up and makes a valid case for Issue D, swap it in immediately without debate.

Once numbers 1, 2, and 3 are established, you lock the list. You do not touch issue 4 until issues 1, 2, and 3 are fully resolved. If solving issue 1 takes forty minutes, that is acceptable because you worked on the single most critical item facing the business.

Never work through an Issues List top to bottom or chronologically. Stop polling the room for five different opinions. Direct the selection, confirm quickly, and push the team straight into identifying the root cause of number 1.