Our leadership team generates dozens of to-dos during IDS, but our completion rate hovers around fifty percent week after week. How do we fix our To-Do List discipline so action items actually get executed?

Question

Tyler Smith · Accepted Answer

An EOS To-Do List completion rate below ninety percent is a symptom of weak accountability and poor issue resolution. In the EOS framework, a to-do is not a wishlist or a long-term project; it is a concrete, single-action deliverable committed to by one person that must be completed within seven days.

To fix low completion rates, enforce three clear rules during the Solve step of IDS:

- Ensure the to-do has only one owner. Shared accountability means zero accountability. If two people need to work on something, assign the to-do to one person to coordinate and deliver the result.
- Scope the task down to seven days. Teams routinely fail to complete to-dos because they create mini-Rocks disguised as weekly tasks. If an action step requires three weeks of research, the to-do for this week is simply to gather the first two data points or schedule the interview, not to complete the entire initiative.
- Make the deliverable binary and observable. Instead of writing 'review vendor contracts,' write 'email termination notice to vendor.'

When reviewing the To-Do List at the start of your Level 10 Meeting, keep it binary: done or not done. If a to-do carries over for two consecutive weeks, remove it from the to-do list and push it back onto the Issues List. It means the team either misdiagnosed the problem or assigned it to someone lacking the capacity to execute.