During our IDS sessions, we constantly get derailed because a leader shares a symptom of an issue, and we spend thirty minutes solving that symptom only to realize we completely missed the actual root cause. How do we force the team to stay in the Identify phase longer before jumping to Discuss and Solve?

Question

Tyler Smith · Accepted Answer

Most leadership teams are terrible at identifying issues because they are addicted to jumping straight into solution mode. A leader raises a problem, and within thirty seconds, three other people are offering tactical fixes. This is a massive waste of time because you end up putting a bandage on a symptom while the actual disease continues to rot the business.

To fix this, the facilitator must strictly enforce the boundary of the Identify phase. When an issue is selected, nobody is allowed to offer a solution or debate the merits of a fix until the owner of the issue has clearly defined the root cause in one sentence.

The facilitator should use the rule of the three whys. Ask why the problem occurred, then ask why that reason happened, and ask why once more. For example, if the issue is that a client is angry about a delayed report, do not discuss how to appease that client. Ask why the report was late. If the answer is because a data pull failed, ask why it failed. If it failed because nobody monitored the automated pipeline, you have identified the real issue: a lack of clear ownership on data monitoring.

Only when the root cause is agreed upon by the team should you move to the Discuss phase. If anyone starts suggesting a solution too early, the facilitator must cut them off immediately. Keeping a hard line between Identify and Discuss will save you hours of circular debate and ensure you are building a scalable, exit-ready business.