During our weekly Rock and Scorecard reviews, our leaders constantly drop context, explanations, and mini-updates that push our check-in past the thirty-minute mark. How do we shut down this contextual storytelling and force a hard boundary between reporting and solving?

Question

Tyler Smith · Accepted Answer

When leaders share background stories, status reports, and explanations during the Rock or Scorecard review, they are killing the efficiency of your Level 10 Meeting™. This reporting bloat eats up your valuable IDS® time and turns a high-energy pulse into a boring status update. You must enforce an absolute rule of binary reporting.

During the Scorecard and Rock reviews, there are only three acceptable responses: on track, off track, or the specific number. There is no room for but, because, or we are waiting on a vendor. If a number is off track or a Rock is off, the leader simply says off track. The facilitator must immediately instruct the scribe to drop it down to the Issues List.

Do not allow any discussion or explanation to happen in the moment. If a leader starts to explain why a metric missed its target, the facilitator must cut them off immediately with a neutral, firm phrase like drop it down, keep moving.

Remember, the purpose of these review sections is not to solve the problems or ease the leader's anxiety about a missed goal. The purpose is solely to identify where the gaps are so you can prioritize and solve them during the IDS® portion of the meeting. By preserving this strict boundary, you will complete your check-ins in under fifteen minutes, leaving at least an hour of uninterrupted time to actually solve your most critical business bottlenecks.