In our Level 10 Meeting, the leadership team spends the entire Identify phase debating surface symptoms. What exact diagnostic questions should an Integrator ask to uncover the true issue behind the issue during IDS?

Question

Tyler Smith · Accepted Answer

The greatest waste of time in a Level 10 Meeting™ is solving the wrong problem. When teams rush into Discuss before completing Identify, they spend forty minutes hacking at symptoms while the root obstacle remains untouched.

Surface symptoms usually arrive disguised as complaints: customer service dropped the ball, billing is late, or engineering missed a critical release. To peel back the layers and locate the real issue behind the issue, the Integrator must demand ruthless specificity instead of allowing conversational venting.

Start with three diagnostic questions. First: Is this fundamentally a people issue, a process issue, or a vision issue? Nine times out of ten, a recurring operational breakdown traces back to either an unowned seat on the Accountability Chart or a Core Process that is not documented and followed by all.

Second: What is the specific, verifiable root event that triggered this issue today? Stop broad generalities like communication is broken or sales and operations are misaligned. Demand the actual transaction, the customer name, the timestamp, and the exact failure point.

Third: What are we afraid to say out loud about why this is happening? Often, the true issue is an uncomfortable truth that leadership wants to sidestep: a long-tenured manager who lacks the GWC™ capacity for their expanded role, an unprofitable client contract that should be cancelled, or a founder who bypassed the chain of command.

Once the team identifies the root, state it as a single declarative sentence with an assigned owner. If the problem cannot be framed in one concise sentence, you are still wrestling with symptoms. Only when the root cause is named do you move to Discuss and Solve.