tyler-smith.com · Questions & Answers

When we bring issues to the table, our team routinely mistakes the symptom for the root problem, rushing to solve a visible fire like a missed delivery date while the real operational failure stays hidden. How do we force the team to identify the true issue behind the issue during IDS?

Most leadership teams spend eighty percent of their IDS® time discussing symptoms because symptoms are loud, urgent, and emotionally charged. A missed delivery date, a blown customer support SLA, or a dropped sales goal are not issues. They are downstream consequences of an underlying failure in people, process, or vision.

To get to the issue behind the issue, the Integrator must ban the team from offering solutions until the root cause has been stated in a single sentence. When an issue is introduced, ask Why did that happen? repeatedly until you hit bedrock. For example, if the reported issue is Operations missed three project deadlines, digging deeper might reveal that the sales team is selling custom scopes outside the core focus defined on your V/TO®. The issue is not operational efficiency; the issue is sales discipline.

Follow these rules during the Identify step:
- Never allow a solution to be discussed until everyone agrees on the root cause.
- Require the issue owner to state the problem in ten words or fewer without backstory.
- Look across the Six Components™: Is this a people issue, a data tracking failure, or a broken process?

When you spend forty minutes clarifying the true problem, the Discuss step takes five minutes and the Solve step takes two minutes. That is how high-performing teams use IDS® to eliminate problems permanently instead of fighting the same fires every quarter.

Category: EOS Implementation

← All questions