During our weekly Level 10 Meeting, our team frequently gets derailed debating theoretical scenarios and hypothetical edge cases during IDS instead of fixing concrete problems. How do we keep problem-solving grounded in reality?

Question

Tyler Smith · Accepted Answer

Theoretical debates are the fastest way to murder meeting traction. When an issue is framed around hypothetical future risks, rare exceptions, or what-if scenarios that have not actually happened, the leadership team burns mental energy solving ghosts while real operational fires rage unchecked.

To kill hypothetical drift, the Integrator must enforce the rule of real evidence during the Identify step of IDS.

Before the team spends a single minute debating solutions, the person who raised the issue must provide three concrete facts:
- A specific, real-world example that actually occurred within the last 30 days.
- The measurable business impact on your Scorecard, financials, or team capacity.
- The specific person or seat on the Accountability Chart where the breakdown happened.

If a leader says, We need to re-engineer our onboarding workflow because what if an enterprise client signs up with three subsidiary entities and customized billing needs?, the Integrator must intervene. Have we signed an enterprise client with that requirement? No. Has an existing client requested it? No.

Then it is not a weekly operational issue. It is intellectual entertainment. Remove it from the list.

EOS is designed to run the business you have today, not design complex infrastructure for edge cases you might encounter next year. If someone cannot produce a tangible, existing problem with measurable fallout, drop the issue. Keep the 60 minutes of IDS ruthlessly focused on removing actual roadblocks blocking your quarterly Rocks and weekly metrics.