How do you design a leader-to-leader use guide to prevent IDS gridlock between two High-D DISC leaders?

Question

Tyler Smith · Accepted Answer

During the Identify, Discuss, and Solve (IDS) portion of an EOS Level 10 meeting, collaboration can deteriorate when multiple executives have high Dominance (D) DISC profiles. High-D leaders are naturally competitive, direct, results-oriented, and driven to control outcomes. When two high-D leaders disagree on an operational issue, the meeting often stalls into a battle of wills rather than constructive problem-solving.

An ACDC leader-to-leader use guide sets ground rules to harness their driving energy without derailing meeting efficiency:

• Enforcing Accountability Chart Jurisdictions: High-D leaders naturally push into peer domains. The guide explicitly restates who owns the ultimate decision based on seat accountabilities. While all leaders provide input during the 'Discuss' phase, the designated seat owner always makes the final call in the 'Solve' phase.
• Timeboxing Advocacy: High-D executives often repeat their points forcefully to wear down opposition. The guide implements a strict protocol: each leader gets a two-minute window to state their position, followed by a mandatory inquiry phase before a resolution is proposed.
• Decoupling Intent from Tone: High-D communication is blunt and concise, which can be misread by other team members as hostility. The use guide establishes shared awareness of this style, keeping the focus entirely on objective business outcomes.
• Offline Alignment for Major Rocks: For complex strategic issues, the guide mandates a 15-minute alignment check prior to the Level 10 meeting to identify core points of friction in private.

These clear guardrails allow high-D executives to drive rapid execution without creating collateral damage on the leadership team.