tyler-smith.com · Questions & Answers

Our leadership team has developed a bad habit of rolling incomplete to-dos over to the next week, sometimes keeping the same task alive for three or four weeks. What is the strict EOS rule for dealing with a to-do that is not completed within seven days?

In the EOS framework, a To-Do is a seven-day commitment, not an ongoing aspiration. It is binary: it is either done or not done. If your team treats the To-Do list as a rolling project board, you are diluting accountability and masking capacity bottlenecks.

The rule is straightforward. When reviewing the To-Do list during the wrap-up, each person states done or not done. If a task is not done, it is allowed to carry over for exactly one additional week, provided the owner recommits to closing it in the next seven days.

If that same task remains incomplete on week two, it cannot simply be carried over a third time. At that point, the facilitator must take one of three actions:

- Drop it to the Issues List to identify why it is stuck, whether due to lack of time, lack of skill, or poor prioritization.
- Reassign it to the correct seat on the Accountability Chart if the current owner lacks GWC for the task.
- Kill it completely if the company functioned fine for two weeks without it being completed.

Allowing tasks to sit on the list for thirty days trains your leaders that weekly deadlines do not matter. That mindset infects your entire organization and erodes enterprise value. Keep To-Dos scoped to seven-day deliverables, maintain your ninety percent completion threshold, and kill lingering items before they stall your operational momentum.

Category: Level 10 Meetings

← All questions