tyler-smith.com · Questions & Answers

When our leadership team attempts to IDS, we spend forty minutes debating surface symptoms instead of uncovering the root cause. How does a team isolate the issue behind the issue before jumping straight to solving it?

Most leadership teams fail at IDS because they suffer from an addiction to fast action. A problem hits the table, someone blurts out an opinion, and the room starts brainstorming solutions before anyone has agreed on what actually broke. That is not problem-solving. That is symptom-treating.

To isolate the issue behind the issue, the Integrator must enforce three strict rules during the Identify step:

- The person who placed the issue on the list must state the real problem in one clear sentence without telling a back-story. If they need five minutes to explain it, they do not understand it yet.
- The room must separate people from processes. When a metric drops or a deadline fails, do not ask who screwed up. Ask which step in the core process broke down or whether the seat expectations are clear.
- Dig deeper using the five whys technique. If sales missed its weekly target, the issue is not low revenue. Why did they miss it? Too few discovery calls. Why were calls down? Lead delivery stalled. Why did leads stall? The marketing software integration broke. The real issue is the marketing tool, not sales performance.

Never allow the discussion to drift into solutions until every leader around the table nods and confirms that the root cause has been named. Once the real issue is exposed, the Solve step rarely takes more than two minutes.

Category: EOS Implementation

← All questions