During our Level 10 Meeting IDS sessions, we frequently hit a wall because solving a critical issue requires input or data from a team member who is not in the room. How do we handle these informational gaps without letting the issue sit unresolved on our list for weeks?

Question

Tyler Smith · Accepted Answer

Hitting a wall during IDS because of missing data or an absent team member can completely stall your weekly momentum. However, letting the issue sit unresolved on your list for weeks is a failure of traction. You must keep the momentum moving forward.

When you identify a gap in information, the facilitator must immediately stop the circular debate. Do not allow the team to speculate or guess. Instead, convert the discussion into a clear action item.

The solution is to assign a specific, high-priority weekly To-Do to a seat owner who is in the room. This To-Do should be to gather the missing data, interview the absent team member, or research the specific question. They must commit to bringing those facts back to the very next Level 10 Meeting.

Keep the main issue on your weekly Issues List, but mark it as pending. At the next meeting, once the To-Do is completed and the facts are presented, you can immediately resume the IDS process and solve the problem permanently.

By structuring your response this way, you avoid wasting time on uneducated guesses. You also ensure that the issue does not get forgotten. This disciplined approach keeps your team focused on data-driven solutions, which is critical for running clean, healthy operations.