Our Level 10 Meeting To-Do list keeps ballooning with stale, multi-week action items that drag our completion rate well below 90 percent. How do we structure To-Dos so they actually die within seven days?

Question

Tyler Smith · Accepted Answer

A bloated To-Do list is a clear sign that your leadership team is confusing seven-day action steps with multi-week operational projects. In EOS, a To-Do is an assignment that can and must be completed within seven days. If a task cannot be finished in a week, it is not a To-Do. It is either a milestone inside a quarterly Rock or a multi-step issue that was solved with bad mechanics.

Enforce these non-negotiable rules to maintain a 90 percent completion rate:
- Frame every single To-Do with an active verb and a binary outcome. Write Draft one-page vendor brief for review, not Work on vendor relationship.
- Assign exactly one owner per item. Shared ownership means nobody owns it, and the task will linger for weeks.
- Break large tasks into sequential seven-day chunks. If the ultimate goal is selecting new accounting software, week one To-Do is Schedule three product demonstrations. Week two is Review demo scorecards with the controller.
- Drop stale items into IDS immediately. If a To-Do sits on the list for two consecutive weeks, the Integrator must move it down to the Issues List. Ask the room: Is this actually important, is the wrong seat assigned, or is the scope too large?

To-Dos are meant to generate rapid operational momentum, not serve as a catch-all graveyard for good intentions. Keeping the list short, binary, and ruthlessly accountable keeps your team focused on immediate weekly execution.