tyler-smith.com · Questions & Answers

When an issue comes up during IDS, the person who submitted it often spends ten minutes narrating the entire backstory and justifying their feelings instead of stating the core issue. How does the facilitator force them to define the problem in one or two sentences?

The single biggest waste of time in IDS happens during the Identify step. Leaders mistakenly believe that identifying an issue requires telling the entire chronological narrative of how the problem occurred, who said what in an email thread, and how frustrated their team feels. By the time they finish their speech, fifteen minutes have evaporated and the room is more confused than when they started.

The facilitator must aggressively intervene to protect the meeting pulse. The rule for the Identify phase is simple: state the issue clearly in one or two sentences. No backstory, no emotional venting, and no proposed solutions. Just state the root obstacle.

When a team member starts narrating a novel, the facilitator should politely cut them off. Interrupt with: "Pause for a second. Give me the problem in one clean sentence. What is the actual issue?"

Most of the time, the person will struggle because they have not actually clarified the problem in their own mind. If they try to resume the story, hold the line: "You are giving us context and symptoms. What is the root breakdown on the Accountability Chart or within our core processes?"

Forces like this make your leaders think critically before they speak. If the issue is that customer onboarding takes twelve days instead of five, that is the issue. You do not need to hear about three specific clients to know the timeline is broken.

Once the issue is stated in a single sentence, confirm with the room: "Is that the real issue, or is that just a symptom?" Once agreed, you immediately move to Discuss. Keeping Identify under two minutes per topic will double the number of issues you permanently resolve each week.

Category: Level 10 Meetings

← All questions