tyler-smith.com · Questions & Answers

During our weekly To-Do review, team members frequently report that a task is almost done or eighty percent complete, keeping unfinished items lingering on the list. How do we restore strict accountability?

Accepting partial credit on weekly To-Dos completely destroys individual accountability. When leaders are permitted to report that an item is almost done, in progress, or waiting on someone else, your weekly Level 10 Meeting loses its teeth, and execution stalls.

In EOS, To-Dos are strictly binary. There are only two acceptable answers during the five-minute To-Do review: Done or Not Done. There is no middle ground, no explanation, and no storytelling.

If a leader was assigned to deliver a pricing proposal to a client and they drafted the proposal but did not send it, the To-Do is Not Done. If they completed ninety-nine percent of the work but the final deliverable was not executed, it is Not Done. The facilitator must not allow the leader to explain the circumstances. Cut them off cleanly: Is it done or not done? If it is not done, check it as incomplete and move to the next item.

Your leadership team should consistently achieve a ninety percent or higher completion rate on seven-day To-Dos. When a To-Do is marked Not Done, leave it on the list for one more week. However, if that same To-Do remains incomplete for a second consecutive week, you must instantly drop it to the Issues List.

A task that rolls over twice signals a real operational breakdown. Either the scope of the To-Do was too large and should have been scoped as an individual priority, the owner lacks the capacity to deliver on their seat, or there is an unaddressed bottleneck blocking execution. Treat chronic To-Do rollover as a systemic issue, not a minor slip.

Category: Level 10 Meetings

← All questions