We have certain weekly to-dos that continuously roll over for three or four weeks without getting done, but the owners refuse to drop them because they claim they are still working on them. What is the hard rule for handling zombie to-dos that fail to clear within seven days?

Question

Tyler Smith · Accepted Answer

In the EOS framework, a To-Do is strictly a seven-day action item. The moment a task stays on the list for fourteen, twenty-one, or twenty-eight days, it is no longer a to-do. It is a zombie task that clutters your agenda, drains team energy, and hides a deeper operational failure.

Implement the two-week hard rule during the five-minute To-Do review. If an item is reported as 'not done' in week one, it carries over for one additional week, no questions asked. If that same item is reported as 'not done' in week two, the facilitator must force an immediate choice: it either gets killed immediately or it gets dropped directly down to the bottom of the Issues List.

Tasks chronically stall for three specific reasons. First, the task was actually a quarterly Rock disguised as a weekly to-do, requiring forty hours of work instead of four. Second, the person who volunteered for it does not have the capacity, skill, or genuine willingness to do it. Third, the task is simply not important, and the owner is using the 'in progress' excuse to avoid admitting it produces zero real business value.

When a stalled to-do drops to the Issues List, the team must IDS the bottleneck. Ask why the task failed to move. If it is non-essential, kill it permanently. If it is vital, break it into three distinct micro-steps, reassign it to someone with the capacity to execute, or make it an official Rock. Never permit a leader to let an uncompleted task linger on the weekly list for a month.