tyler-smith.com · Questions & Answers

During IDS®, our team constantly tries to solve surface symptoms instead of the root cause, leading to endless cyclical debates about process tweaks instead of tackling the uncomfortable human problem. How do we force the team to identify the true root issue before proposing solutions?

Most leadership teams fail at the I in IDS. When an issue hits the table, someone immediately jumps to a solution: We need a new software tool, we need to update our standard operating procedure, or we need to send a company-wide email. These are bandages applied to symptoms. They feel productive, but they leave the underlying rot completely intact.

The Integrator must act as a ruthless gatekeeper between Identify, Discuss, and Solve. Establish an explicit rule: nobody is allowed to propose a solution until the root cause has been clearly stated and agreed upon by the room.

When someone throws out a tactical solution within thirty seconds of an issue being introduced, the Integrator must cut them off: Stop. We are not solving yet. We are still identifying. What is the actual problem?

Use the five whys technique. If the stated issue is that client onboarding is delayed, ask why. If the answer is that marketing sent incomplete files, ask why. If the answer is that marketing lacks clear intake requirements, ask why. Often, the real issue has nothing to do with client onboarding. It is usually an Accountability Chart breakdown where an employee lacks GWC for their seat, or two leaders are avoiding an honest conversation about cross-functional friction.

You know you have reached the root issue when the room gets quiet and slightly uncomfortable. Root issues are almost always related to human behavior, unclear accountability, or poor structure. Once you dig down to that foundational reality, the actual solution is usually obvious and takes only a few minutes to finalize.

Category: Level 10 Meetings

← All questions