Our team gets stuck in a loop during the Identify phase of IDS, trying to gather perfect data and context before we even agree on what the actual issue is. How do we define the issue quickly without getting bogged down in history?

Question

Tyler Smith · Accepted Answer

The Identify phase of IDS is often the most difficult because leaders love to tell stories. When an issue is raised, the owner frequently feels the need to share a long, historical narrative about how we got here, who said what, and why it is complicated. This narrative is a waste of your weekly meeting time.

To break this loop, the facilitator must enforce the rule of the three-sentence issue. When someone drops an issue, they must be able to state it in three sentences or less. They must clearly identify the gap between where things are and where they should be. For example: our client onboarding is taking fourteen days instead of seven, we do not know why, and it is causing client churn.

If the owner starts listing historical examples or defending their department, the facilitator must interrupt. Use phrases like: stop, what is the core problem we need to solve today? Do not allow the team to discuss solutions or dig into background details until the actual issue is agreed upon and written down.

Remember, you do not need perfect information to identify a problem. You only need to agree on what is broken. Once the root cause is clear, then you can move to the Discuss phase where relevant context can be shared. By keeping the Identify phase rapid and focused, you prevent the meeting from turning into an exhausting history lesson.