When leadership team members resist adding their real operational challenges to the Issues List out of fear of conflict, how do you build genuine IDS traction?

Question

Tyler Smith · Accepted Answer

When an Issues List is barren or populated only with superficial software requests, the problem is not a lack of business challenges. The problem is a lack of psychological safety. Team members are terrified that putting an operational breakdown on the board will result in public blame, defensive arguments, or retaliation.

To build genuine IDS traction, the owner and Integrator must lead by example. In the next Level 10 Meeting, the owner should place their own significant operational failure or blind spot at the top of the list. Showing the room that leadership welcomes scrutiny sets the standard for everyone else.

Second, the team must strictly follow the IDS protocol:

- Identify: Spend the majority of the time uncovering the real root cause rather than debating surface symptoms. Ask why five times before even discussing a fix.
- Discuss: Keep the conversation anchored to the systemic process failure or Accountability Chart gap. Forbid personal attacks, defensiveness, and interruptions.
- Solve: Agree on concrete action items with an assigned owner and a strict completion date.

When leaders realize that IDS is a clinical, supportive process designed to kill systemic friction rather than punish individuals, their reluctance disappears. The Issues List quickly transforms from an object of fear into the team's most powerful operational weapon.