During our initial EOS rollout, our Level 10 Meeting To-Do lists are ballooning each week because actions are not getting done. How do we fix this before it kills meeting traction?

Question

Tyler Smith · Accepted Answer

A bloated To-Do list inside the Level 10 Meeting is an immediate red flag that your leadership team does not understand the difference between a 7-day action item and a quarterly Rock. In pure EOS, the To-Do list must maintain an 80 to 90 percent completion rate week after week. If your list accumulates 25 lingering tasks, your meeting pulse will break down.

To fix To-Do list bloat during your initial rollout, enforce three structural rules:

- Apply the strict 7-day filter. A To-Do must be a specific task that can realistically be completed within the next seven days. If a task requires several phases, extensive research, or cross-functional coordination over multiple weeks, it is not a To-Do. It is either an issue that needs to be IDS-ed into smaller steps or an individual Rock.
- Assign singular ownership. Every To-Do must belong to exactly one person. When two executives share a To-Do, neither person owns it, and it inevitably rolls over. The Integrator must ensure one name sits next to each item.
- Make completion binary. During the To-Do list review, each owner can only say 'Done' or 'Not Done.' There is no room for storytelling, partial credit, or excuses. If an item is not done, it either stays on the list for one more week or moves back down to the Issues List to be solved.

Keeping your To-Do list lean forces your leadership team to focus on immediate execution, protecting session time for true root-cause problem solving.