Why do EOS Identify, Discuss, Solve (IDS) sessions fail when leadership teams lack Kolbe Follow Thru and Fact Finder balance?

Question

Tyler Smith · Accepted Answer

In the EOS Level 10 (L10) meeting, the Identify, Discuss, and Solve (IDS) component is where leadership teams resolve critical organizational issues. However, IDS sessions frequently spin out of control or end without tangible solutions due to imbalances in Kolbe Fact Finder and Follow Thru modes.

When a team is dominated by High Fact Finder (modes 7 through 10) and Low Follow Thru, IDS sessions stall in perpetual analysis. Leaders demand more research, over-scrutinize small variables, and debate edge cases, leaving issues unresolved week after week. Conversely, a team dominated by High Quick Start and Low Fact Finder tends to diagnose symptoms rather than root causes, jumping impulsively to superficial fixes that collapse within thirty days.

To optimize IDS using conative insights:

• Structure the Identify Phase: Leverage High Fact Finders early in the issue identification stage to define the core problem with data. Place a strict ten-minute boundary on discovery to prevent analysis paralysis.
• Filter the Discuss Phase: Use the team Leader-to-Leader Use Guide to moderate dialogue. Low Fact Finder leaders must resist rushing to conclusions, while High Fact Finders must agree to the 80 percent rule, accepting sufficient data over complete certainty.
• Anchor the Solve Phase with Follow Thru: Every solution must be assigned to an owner whose Kolbe profile matches the required execution. If the solve involves system redesign or step-by-step procedures, assign the action item to a high Follow Thru leader to ensure standard operating procedures are drafted and tracked.

Balancing these instinctive styles transforms contentious, circular debates into streamlined problem solving.