When we prioritize our weekly Issues List during our Level 10 Meeting™, the loudest leaders or those with the most senior titles always get their issues pushed to the top of the IDS® list. How do we democratize the prioritization process so quiet but critical operational bottlenecks do not get ignored?

Question

Tyler Smith · Accepted Answer

When loudest-voice syndrome dictates your IDS® priority, your Level 10 Meeting™ becomes a tool for personal venting rather than strategic execution. The issues that get solved are simply those of the people who complain the loudest, while quiet, systemic operational failures continue to rot at the bottom of your list.

To eliminate this bias, you must separate the ownership of an issue from its priority. Prioritization is a collective team decision, not a local land grab.

Before you begin IDS®, the facilitator must read through the short-term Issues List. Instead of letting people pitch why their issue is the most important, use a blind or structured voting system to select the top three.

For example, have each team member quickly select their top three issues in their head. Then, go around the table and have everyone state their top choices. The three issues with the most consensus become issues one, two, and three for that meeting.

Alternatively, use your V/TO® and Core Focus as a filter. The facilitator should ask the team which three issues on this list, if solved today, will have the greatest positive impact on our quarterly Rocks or our current scorecard metrics.

By grounding the prioritization in data and strategy rather than emotional volume, you ensure that the leadership team focuses its collective brainpower on the constraints that matter most to the health of the entire business.