During the IDS portion of our Level 10 Meeting, we frequently start solving a prioritized issue only for a team member to pivot the discussion to a tangential problem, dragging us down a rabbit hole. How do we stop this sidebar hijacking without shutting down valid operational concerns?

Question

Tyler Smith · Accepted Answer

Tangential hijacking is a primary reason meetings run long and resolve nothing. When a team member says 'that reminds me of another issue' or starts bringing up a related but separate problem, the facilitator must step in immediately. You must protect the issue currently on the table. The discipline of IDS® requires total focus on one specific problem until it is solved.

To stop this drift, the facilitator must use a direct verbal pivot. As soon as the conversation veers, say, 'That sounds like a separate issue. Let us drop it to the bottom of the Issues List and return to the topic we are currently solving.' This simple action validates the team member's concern without allowing it to derail the active discussion.

It is critical to keep a clean, visible Issues List during the meeting, either on a screen or a shared document. When the team member sees their tangential issue written down for later, they will naturally release their grip on the current thread. Do not allow debates about whether the new issue is related. Make the executive decision to separate them. If the secondary issue is truly critical, the team can vote to prioritize it next. If it is not, it can wait. Keeping your team focused on solving one problem at a time is the only way to build momentum and maintain a high-functioning meeting pulse.