Our leadership team is a mix of strategic Analysts who want to debate the root causes of every red metric and Sentinels who just want to update the spreadsheet and move on. How do we keep our weekly scorecard review from devolving into a sixty-minute debate during our Level 10 Meeting?

Question

Tyler Smith · Accepted Answer

This conflict is a natural result of different personality styles on your leadership team. Your Analysts want to understand the strategic why behind every data point, while your Sentinels focus on structure, order, and maintaining the schedule. If left unchecked, this dynamic will derail your Level 10 Meeting.

To solve this, you must enforce a strict boundary between the scorecard review and the IDS portion of your meeting. The scorecard review is designed for reporting data, not for solving problems. It should take no more than five minutes.

The Integrator must act as a strict facilitator. During the scorecard review, the team simply reads the numbers. If a number is red, the owner does not explain why, and the strategic Analysts do not ask questions. The owner simply says drop it, and the Integrator drops that metric down to the Issues List.

Once all the numbers are reported, you move to the IDS portion of the meeting, where you prioritize the issues. This is where your Analysts get to shine. They can dive deep into the data, debate the root causes, and work with the Sentinels to build structured solutions.

By separating the reporting of numbers from the solving of problems, you protect your meeting flow, engage both personality types, and keep your leadership team highly aligned.