How can leadership teams adapt the EOS IDS (Identify, Discuss, Solve) process to accommodate contrasting Kolbe Action Modes?

Question

Tyler Smith · Accepted Answer

The Level 10 IDS process is designed to permanently resolve organizational obstacles. However, teams often fail during IDS due to unmanaged conative differences. Teams with high Fact Finder profiles get stuck in endless research loops, while teams heavy in Quick Start profiles create premature, untested fixes that unravel within weeks.

Optimizing the IDS protocol according to Kolbe Action Modes ensures smooth problem-solving:

• Identify (Fact Finder vs. Quick Start Balance): High Fact Finders tend to frame symptoms as sprawling data dilemmas. A high Quick Start pushes to solve issues before root causes are isolated. Teams should implement a conative timebox: give Fact Finders three minutes to state core data points, then enforce an immediate root-cause definition before moving forward.
• Discuss (Protecting Conative Energy): In the Discuss phase, leaders with low Follow Through often introduce unrelated side problems, derailing focus. The meeting leader must establish ground rules that keep discussions bounded by the original problem statement, preventing brainstorming tangents.
• Solve (Follow Through and Implementor Activation): High Quick Starts consider an issue solved once a verbal agreement occurs. A true EOS solution requires an accountable owner, clear steps, and a strict deadline. The use guide mandates that action items must be formatted to satisfy initiating Follow Through requirements - documenting precise steps, measurable deliverables, and exact milestone dates.

Adapting the IDS protocol to honor conative wiring eliminates meeting fatigue and turns contentious issue resolution into sustainable execution.