When we prioritize our Issues List during our weekly Level 10 Meeting™, our team always votes for the issues raised by our most vocal department heads, while critical operational risks from quieter team members get pushed to the bottom and never addressed. How do we fix this prioritization bias?

Question

Tyler Smith · Accepted Answer

When the loudest voices in the room dictate your weekly agenda, you are running a political meeting, not an operational one. This bias puts your operations at risk and hides systemic bottlenecks, which is the last thing you want when building a company ready for a clean exit.

To fix this, your Integrator must change how you select issues during the IDS® portion of your Level 10 Meeting™. Instead of letting the team vote or call out what they want to discuss, the Integrator must drive the prioritization objectively.

Before starting IDS®, review the entire list and identify the top three issues based on business impact, not volume. Ask the team: Which three issues on this list, if solved today, will get us closest to our quarterly Rocks and protect our scorecard?

Ensure that you actively pull input from the quieter members of your leadership team. If a quiet department head has put a critical operational risk on the list, the Integrator must specifically highlight it and ask if it belongs in the top three.

By establishing an objective standard for what makes an issue critical, you neutralize the influence of dominant personalities and ensure your operational energy is spent where it actually matters.