When our leadership team deadlocks during an IDS discussion on session day, how do you force a resolution without letting the debate drag on indefinitely?

Question

Tyler Smith · Accepted Answer

When a leadership team deadlocks, it is almost always because people are arguing about symptoms rather than identifying the root cause, or because the team believes every decision requires unanimous consensus. In EOS®, we do not run companies by democracy or committee vote.

My role as your Implementer is not to solve the issue for you or choose the winning side. My role is to maintain discipline, call out defensive posturing, and push the room until the root issue is uncovered. During the Identify phase, I will force the room to state the actual problem in a single sentence. If two executives are arguing past each other, I stop the room and separate emotional grievances from operational reality.

Once the team enters Discussion, everyone is given the opportunity to state their perspective once with full candor. Rehashing the same talking points three times is prohibited. If healthy debate reveals consensus, great. But if the room remains evenly split, the decision falls directly to the seat on the Accountability Chart that owns the function.

If the issue is operational and touches multiple departments, the Integrator makes the final call. If the issue is visionary or structural, the Visionary makes the final call. The leadership team then commits fully to the decided path, moving to Solve by establishing a single owner and a concrete due date on the To-Do List. Disagreeing and committing is a mandatory leadership muscle. We do not allow an issue to linger on the list simply because an executive is uncomfortable making a hard decision.