When we run our weekly IDS session, our leadership team frequently gets stuck in polite, circular debates because we rely on subjective opinions rather than hard data to define the problem. How do we use our weekly Scorecard and operational metrics to strip the emotion out of our meetings and find the real issue behind the issue?

Question

Tyler Smith · Accepted Answer

The fastest way to break through subjective debates during IDS is to anchor every discussion in your weekly Scorecard. When an issue is put on the list, the first question the facilitator should ask is which weekly metric or Rock this issue is affecting. If you cannot tie the issue to a measurable metric or a specific accountability on the Accountability Chart, you are likely dealing with a symptom or an interpersonal grievance rather than a systemic operational bottleneck.

To find the issue behind the issue, look at the historical trend of your Scorecard. If a metric has been red for three consecutive weeks, the problem is rarely the immediate excuse given by the owner of that seat. It is usually a failure in a core process, a resource constraint, or a capacity issue. Use the data to ask why five times.

By forcing your team to look at the hard numbers before they start proposing solutions, you strip the defensive emotional charge from the conversation. The numbers do not have feelings, and they do not lie. When you make it a rule that every operational issue must be defined by its impact on a specific number, you shift the team mindset from defending personal turf to solving the structural bottlenecks that are holding back the entire organization.