tyler-smith.com · Questions & Answers

Our leadership team scorecard is clean and visual, but our weekly scorecard review still takes fifteen minutes because people feel the need to explain or justify their numbers as we read them. How do we train the team to report in under five minutes without the commentary?

The weekly scorecard review in your Level 10 Meeting™ exists to identify problems, not to solve them or offer excuses on the spot. When a number is read and it is red, the only acceptable response from the seat owner is dropped or not dropped. There is no room for explaining why the number was missed, what the team is doing to fix it, or how a client delayed the process. That commentary is what kills your meeting rhythm and stretches a simple review into a fifteen-minute slog.

To enforce this, the Integrator must act as a strict gatekeeper. If an owner starts to explain a red number, cut them off immediately. Say, drop it to the Issues List, and move to the next row. If a metric is off track, it simply gets added to the Issues List for the IDS® portion of the meeting. This keeps the review under five minutes.

You must also train your team to prep their data beforehand. No one should be calculating numbers live during the meeting. The scorecard must be fully updated before the meeting starts. When the review begins, the team should look at the sheet silently or read the off-track numbers aloud rapidly.

Remember that the scorecard is a diagnostic tool. If a warning light flashes on your dashboard, you do not stop the car immediately to fix it while driving. You acknowledge it and address it when you pull over. Treat your red numbers the same way. Drop them down, move on, and solve them during the designated problem-solving segment.

Category: Scorecards & Data

← All questions