When we review our weekly To-Do list, our leadership team members spend two minutes explaining why a task is not done or describing the steps they took, turning a quick five-minute check into a lengthy status update. How do we keep this section strictly binary without the narrative?

Question

Tyler Smith · Accepted Answer

The To-Do review in your Level 10 Meeting is an accountability tool, not a story hour. It should take no more than five minutes to run through the entire list. When leaders start telling the story of why something is not done or explaining all the hard work they put into it, they are trying to avoid the discomfort of saying "not done." This narrative clutter wastes valuable time and dilutes accountability. To fix this, your facilitator must enforce a strict rule of binary reporting. When a To-Do is read, the person accountable is allowed to say only one of two words: "done" or "not done." No explanations, no excuses, and no context. If a To-Do is done, move to the next item. If it is not done, it immediately gets dropped to the bottom of the Issues List as an issue to be solved during IDS if time permits. This keeps the meeting moving and keeps the focus on results. It also forces a culture of high performance where leaders are highly motivated to avoid the public exposure of having their incomplete tasks dropped to the Issues List. Managing your weekly pulse with this level of precision sends a clear message to your team and any future buyer that your organization values execution over excuses. Keep the reporting binary and save the discussions for the IDS portion of the meeting.