Team members frequently drop vague, hypothetical worries onto our Level 10 Issues List like 'company morale feels off' or 'what if the market shifts,' wasting thirty minutes debating hypotheticals. How do you filter out phantom issues before entering IDS?

Question

Tyler Smith · Accepted Answer

Hypothetical worries, philosophical complaints, and vague anxieties are meeting killers. When a leadership team spends forty minutes debating abstract anxieties like company culture feels heavy or what if interest rates rise again, nobody solves anything because there is no concrete problem to resolve.

To eliminate phantom issues, the facilitator must force the issue owner to frame the topic into one of two categories before it is accepted for IDS®:
- A specific operational problem that has already happened.
- A specific, predictable risk that requires an immediate, tangible contingency plan.

If a leader cannot articulate the issue in two concise sentences that point to observable facts, data, or individuals, it is not ready for the Level 10 Meeting™ Issues List.

When someone puts morale feels low on the board, the Integrator must immediately ask: what specific data or observable events demonstrate this? Did turnover spike in customer service? Did two senior engineers resign? Are Scorecard metrics missing? If the answer is just a general vibe, push the issue back to the owner: go gather the facts, identify the specific department or breakdown, and bring it back when it is actionable.

Similarly, for macro-worries like market shifts, the question is: what specific operational decision do we need to make today? If there is no immediate action to take, it belongs in quarterly or annual planning during the V/TO® review, not in the weekly meeting pulse.

Filter for facts and actionable decisions. Everything else is conversational noise that drains the team's energy.