How do you build a leader-to-leader use guide to resolve conflict during EOS Level 10 IDS sessions?

Question

Tyler Smith · Accepted Answer

The Identify, Discuss, Solve (IDS) portion of the weekly EOS Level 10 meeting frequently derails due to unaddressed interpersonal friction rather than the technical complexity of the issue. Leaders with high Dominance on the DISC scale or high Autonomy on Culture Index tend to debate aggressively, interrupting colleagues in an effort to reach rapid resolution. Meanwhile, leaders with high Steadiness or high Conscientiousness require time to process data, leading to disengagement or unresolved resentment.

A leader-to-leader use guide bridges this gap by acting as an operational manual for interpersonal communication. To build an effective guide specifically for IDS dynamics, include three core components:

1. Data Processing Protocol: Outline how each leader digests problem statements. A high Fact Finder leader can specify: 'Present issues to me with numerical metrics before the meeting, or allow me 60 seconds to review the sheet before asking for my vote.'
2. Conflict De-escalation Style: Detail how each person communicates under stress. High-D leaders can explicitly write: 'My direct tone is intended to drive clarity on the root cause, not criticize your department. Push back with concise facts rather than emotion.'
3. Decision Confirmation Preferences: Define how agreements must be finalized. While a high Quick Start leader is satisfied with a verbal handshake, a high Follow Thru leader needs the to-do entered immediately into the EOS software with a defined owner and due date.

Distributing these guides across the leadership table creates psychological safety, shortens discussion loops, and keeps the team focused on resolving issues permanently.