During the Identify phase of IDS®, our team members often list vague, high-level challenges like communication issues instead of naming the specific person or process that is failing. How do we push past this polite avoidance to identify the real problem?

Question

Tyler Smith · Accepted Answer

Polite avoidance is the enemy of progress. When a team member lists communication issues as an operational block, they are hiding the real issue to avoid conflict. To solve this, you must demand absolute clarity during the Identify phase before you allow any discussion or solving to begin.

- First, the meeting leader must ask the owner of the issue to define the problem in a single, clear sentence.
- Second, you must identify the specific impact by asking who is being affected and what this is costing the company in time or revenue.
- Third, if the issue involves a person, you must name them. If an employee is not delivering, listing communication issues just delays the inevitable. Name the seat on the Accountability Chart™ that is failing to execute.

This requires a high trust environment where healthy conflict is encouraged. If your team is afraid of hurt feelings, they will continue to solve symptoms while the real bottlenecks remain untouched. Working with an experienced EOS Implementer® is critical here, as they provide the objective framework to push through this discomfort. Stop accepting vague generalizations and start demanding hard facts during every IDS® session.