Why do leadership teams stall during EOS IDS sessions based on DISC profiles?

Question

Tyler Smith · Accepted Answer

The Identify, Discuss, and Solve (IDS) component of the EOS Level 10 Meeting requires distinct behavioral transitions: diagnosing root causes, debating options transparently, and committing to action items. When an executive team struggles with IDS, the root cause is rarely the complexity of the issues. Instead, it is almost always behavioral mismatch driven by unmanaged DISC dynamics.

Here is how uncalibrated DISC profiles stall each phase of IDS:

• Stalling in 'Identify': High Dominance (D) leaders tend to rush this stage, mistaking visible symptoms for root causes so they can jump straight into solving. Meanwhile, High Steadiness (S) leaders may recognize interpersonal root causes but remain silent to preserve team harmony, preventing the real issue from surfacing.
• Looping in 'Discuss': High Conscientiousness (C) leaders require exhaustive data, historical precedents, and proof before feeling safe to decide. In contrast, High Influence (I) leaders turn discussions into brainstorms, introducing tangential ideas that distract from the core problem. The clash between C profiles demanding precision and I profiles seeking creative engagement causes teams to talk in circles.
• Failing at 'Solve': High S leaders may nod in agreement during the meeting to avoid conflict, only to withhold buy-in after the session ends. High D leaders may unilaterally assign action items without verifying whether the assigned seat possesses the bandwidth or buy-in to execute.

To eliminate this friction, create an IDS operating agreement tailored to your team's DISC map. Require High D leaders to ask two clarifying questions before proposing solutions, prompt High S leaders for input explicitly, and cap data gathering for High C members with strict time limits.