We are running our weekly Level 10 Meetings™ but the IDS® portion always gets bogged down in personal opinions and finger-pointing. How do we introduce data-driven objectivity into our problem-solving?

Question

Tyler Smith · Accepted Answer

When the IDS® portion of your Level 10 Meeting™ devolves into finger-pointing and subjective opinions, it is because your team is solving symptoms rather than root causes. To run an efficient problem-solving session, you must introduce data-driven objectivity and enforce the strict discipline of the process.

Start by requiring that any issue brought to the table is defined with objective facts rather than emotional narratives. If a team member brings an issue about poor communication, force them to provide a specific example, the operational impact, and any relevant Scorecard metrics. This instantly grounds the conversation in reality.

During the Identify stage, do not allow anyone to propose solutions. The goal is solely to get to the root cause of the issue. Ask why the problem occurred at least three times.

Once the true issue is identified, move to Discuss. Keep this section brief. If the team starts repeating the same points, the facilitator must step in and move the team to the Solve stage.

The Solve stage must result in a clear, actionable to-do with a single owner and a due date. If the solution requires more than two weeks, it is likely a Rock and should be tabled for your next quarterly session. By keeping the focus on objective data and clear actions, you eliminate the emotional drama and solve issues permanently.