How do you manage the room during a session day when two leaders reach an intense impasse or personal conflict during an IDS debate?

I lean into it. Conflict is not a bug in the EOS® model; it is an essential feature. When two department leaders hit an intense impasse during IDS®, it usually signals that your team has finally stopped being polite and is finally digging into a root cause that has been quietly draining operational profit for months.

My role as an EOS Implementer® is to maintain emotional neutrality while keeping the room focused entirely on the greater good of the company. When friction flares, I stop the cross-talk immediately and strip personal accusations out of the conversation. We do not litigate personal styles or past grudges. Instead, we anchor the debate to your Core Values, your Accountability Chart, and your numbers.

First, we clarify the root cause. Most leadership impasses stem from overlapping operational territory or vague seat definitions. If two leaders are fighting over a customer delivery issue, it is almost always because the Accountability Chart is fuzzy regarding who holds final decision rights. Second, I force both parties to state their proposed solutions clearly instead of continuing to restate the frustration. Third, if consensus cannot be reached, the Integrator breaks the tie. You do not leave the session day with passive-aggressive agreements to disagree. We stay in the room until the issue is solved, the decision is owned, and every member of the team commits to supporting the resolution publicly.

Category: Working With Tyler