tyler-smith.com · Questions & Answers

During the IDS® portion of our Level 10 Meeting™, our team constantly jumps straight into assigning To-Dos and debating solutions before we have even finished identifying the true root cause. How do we stop this premature solution drift?

Jumping straight from the headline of an issue to a proposed solution is the most common time-waster in corporate meetings. It feels productive because people are taking action, but it guarantees you will solve the same symptom again six weeks later. Action without root-cause clarity is just expensive movement.

To stop premature solution drift, the meeting facilitator must enforce strict stage gates between Identify, Discuss, and Solve:

First, do not leave the Identify step until the issue owner states the problem in one or two clear sentences. If someone says our billing process is chaotic, that is not an issue; it is a complaint. The facilitator must ask: What is the specific breakdown, who owns it, and what is the measurable impact? Keep asking until the root cause is stated plainly.

Second, silence solution proposals during the Discuss phase. If a team member blurts out we should buy new software or we need to assign this to Sarah before the team agrees on the root cause, the facilitator must cut in immediately. Say: We are not solving yet; we are still determining if everyone sees the same problem. Let the whole team state their observations first.

Third, only move to Solve when the team agrees on the real bottleneck. Once root cause is established, the solution phase usually takes less than two minutes because the right answer becomes obvious. An issue is only solved when there is an agreed action item with one owner and a seven-day deadline.

Category: Level 10 Meetings

← All questions