Our Level 10 Meeting To-Do List routinely rolls over with dozens of open items that take weeks to complete. How do we regain control of weekly To-Do accountability?

Question

Tyler Smith · Accepted Answer

In EOS®, a To-Do has a strict definition: a specific action item that must be completely finished within seven days. It is not an ongoing operational duty, an open-ended project, or a 30-day mini-Rock.

When a To-Do List balloons to thirty or forty open items week after week, the team is using the list as a digital archive to avoid immediate execution. To restore discipline, enforce three rules during the weekly meeting pulse.

First, every To-Do must have a single assigned owner and a strict seven-day due date. If an action cannot be completed within seven days, break the task down until you isolate the single step that can be executed this week.

Second, during the To-Do review segment of the Level 10 Meeting, the Integrator permits only two responses: done or not done. If an item is not done, it may remain on the list for one additional week. If it is still incomplete after two consecutive weeks, it is immediately dropped to the Issues List for IDS®. The team must discover why the commitment failed: lack of capacity, poor prioritization, or an Accountability Chart misalignment.

Third, measure completion against the EOS standard: at least 90 percent of all To-Dos must be marked done every single week. When team members know that incomplete To-Dos result in public root-cause analysis, execution rates rise sharply.