tyler-smith.com · Questions & Answers

How do we build a systematic way of identifying the issue behind the issue during IDS® when our team is hesitant to call out bad processes or weak performance for fear of creating personal conflict?

Fear of conflict is the single biggest barrier to effective problem solving. When your team is polite instead of honest, you end up solving surface symptoms while the real problems continue to rot your operations.

To get to the root cause, the leader or facilitator must create an environment of healthy conflict. Start by separating the person from the issue. When an issue is placed on the board, it is no longer a personal failure; it is an organizational challenge that the team must solve together.

During the Identify step of IDS®, use the "five whys" technique. Do not accept the first explanation at face value. If the issue is "we missed our sales target," ask why. If the answer is "we did not get enough leads," ask why again. Keep digging until you reach a root cause, which is usually a broken process, a lack of resources, or a people issue where someone does not GWC™ their seat.

Encourage your team to enter danger. If you see someone holding back or looking uncomfortable, call on them directly. Ask them what they are really thinking. Once your team realizes that addressing the hard truths leads to permanent solutions rather than personal attacks, the fear of conflict will evaporate, and your IDS® sessions will become incredibly efficient.

Category: EOS Implementation

← All questions