Members of our leadership team consistently show up to our weekly Level 10 Meeting unprepared, spending the first ten minutes updating their Scorecard numbers and Rock statuses on the fly. How do we enforce pre-meeting preparation so we do not burn meeting time on administrative updates?

Question

Tyler Smith · Accepted Answer

Spending the first ten minutes of a Level 10 Meeting watching executives scramble to update their Scorecard metrics and Rock statuses is an egregious waste of executive payroll. The ninety-minute meeting pulse is designed for analysis and problem solving, not administrative data entry.

The leadership team must enforce a strict pre-meeting deadline. All numbers on the weekly Scorecard, all Rock updates (marked strictly as on track or off track), and all completed To-Dos must be logged into your system at least two hours prior to the meeting, or by the end of the preceding business day.

To eliminate the habit of updating numbers on the fly, adopt a binary rule: if a metric or Rock is not updated by the deadline, it is automatically marked as off track or red, and it is instantly dropped to the Issues List.

When leaders know that incomplete reporting will be highlighted publicly as a failure of accountability, their behavior changes fast. If a department head claims they did not have time to pull their numbers, that is not a reporting glitch; it is an operational capacity or process problem that belongs in IDS.

Running an elite leadership team means treating the weekly pulse with the same rigor you would treat a board meeting or a client pitch. Arriving unprepared signals disrespect for your peers' time. Set the deadline, hold the line, and use automation or delegation to ensure data is populated before anyone enters the room.