During our IDS® sessions, we frequently run into highly contentious issues where our leadership team simply cannot reach a consensus, resulting in us agreeing to disagree and pushing the issue to the next week, creating zombie issues that haunt our list for months. How do we break these deadlocks?

Question

Tyler Smith · Accepted Answer

Agreeing to disagree is a leadership failure disguised as polite consensus. In a healthy EOS company, healthy debate is encouraged during the Discuss portion of IDS, but when discussion ends, a decision must be made. If your team is stuck in a loop of endless debate, it is because your Integrator is failing to exercise their authority on the Accountability Chart.

The Integrator is the tie-breaker. While the goal is always to find a collaborative solution that aligns with your V/TO, consensus is not always possible, and waiting for unanimous agreement will paralyze your operations. When the team is deadlocked, the Integrator must step in, hear all perspectives, and make the final call. Once that decision is made, every member of the leadership team must fully support it outside the room, regardless of their personal stance during the meeting. There is no room for passive resistance or quiet sabotage.

If the issue is so complex that you truly lack the data to make a decision, the only acceptable To-Do is to assign someone to gather the necessary data within seven days. You do not push the issue to next week just because it is uncomfortable. Decide, commit, and move on.