During our IDS sessions, we drop issues because the team gets defensive or agrees to a surface-level fix just to move on. How do we push past this polite avoidance and force the team to identify the true organizational breakdown?
Polite teams make poor companies. When your leadership team settles for easy answers during IDS, you are merely treating symptoms while the disease continues to rot your operations. To break through this pattern of artificial harmony, the meeting leader must adopt the role of an investigator rather than a facilitator. When an issue is raised, do not let the team jump straight to solving. You must spend the majority of your time in the Identify phase. Ask the team to define the problem in a single sentence that focuses on the root cause, not the personality or the symptom. If the team says the issue is that sales are down, ask why five times. Is it because the sales team is lazy, or is it because the handoff process from marketing is broken, or is it because the Accountability Chart has a GWC gap in leadership? The Integrator must call out the elephant in the room. If a team member gets defensive, the Integrator must redirect the focus back to the business issue, reminding everyone that we are attacking the problem, not the person. If you solve the wrong problem, you waste ninety days. Take the time to dig until you find the structural defect, even if it makes the room uncomfortable.
Category: EOS Implementation