During IDS, two department heads frequently lock horns over a tactical operational disagreement that only involves their two seats, holding the rest of the leadership team hostage. How do we take that issue offline without abandoning accountability?

Question

Tyler Smith · Accepted Answer

During the 60 minutes of IDS®, nothing kills team engagement faster than two department heads debating granular operational friction that only affects their two seats. While the rest of the leadership team stares at the ceiling, minutes bleed away from company-wide priorities.

The Integrator must step in the moment a debate shifts from executive-level strategy or systemic root causes into bilateral tactical details.

Use this protocol to take the issue offline while maintaining total accountability:
- Halt the debate: The Integrator stops the conversation and asks: Does solving this right now require input from the entire room, or does this belong strictly between the two of you?
- Define the required outcome: If the issue only impacts their departments, clarify the exact objective the business needs them to achieve. Do not leave the expected result ambiguous.
- Create a binary To-Do: Assign a specific 7-day To-Do to one of the two leaders. For example: Schedule working session with Head of Operations and deliver resolved inventory workflow by next Tuesday.
- Verify closure at the next pulse: At the following Level 10 Meeting™, the item is checked during the To-Do review. If they solved it, the issue is dead. If they failed to align or hit an unresolved roadblock, the issue returns to the Issues List for the full team to address.

The Level 10 Meeting is built to solve company-wide bottlenecks. Pushing bilateral operational friction to dedicated offline sessions protects the room's energy and keeps executive focus on enterprise value.