When our team runs IDS, we constantly jump straight to proposing solutions before we have even agreed on the real problem. How do we force ourselves to uncover the issue behind the issue?
Most leadership teams suffer from a bias toward fast action. When an issue hits the table, someone immediately shouts out a solution, another person argues with the tactic, and twenty minutes later the team has debated five different fixes for a symptom while the root disease remains untouched.
To find the issue behind the issue, you must spend at least sixty percent of your time in the Identify phase. The person who raised the issue must state it in one clear, concise sentence without telling a ten-minute background story. Once stated, the rest of the team must stop talking about solutions and start digging into root causes.
The most reliable tool is asking why multiple times. If the presenting issue is "our sales proposals are going out late," do not start discussing template software. Ask why they are late. The answer might be that sales needs custom pricing approval from finance. Why does finance take three days? Because there are no standard pricing guidelines. The real issue is not proposal turnaround time; the issue behind the issue is the lack of a defined pricing framework.
Never move to Discuss until every leader in the room agrees on the exact problem statement. Once the real root cause is isolated, the Discuss and Solve steps usually take less than five minutes, producing a clear to-do assigned to a single owner.
Category: EOS Implementation