Our leadership team treats the 7-day To-Do deadline as optional, frequently carrying the same action items over for two or three weeks in a row without finishing them. How do we enforce a strict rule against rolling To-Dos without creating administrative gridlock?

Question

Tyler Smith · Accepted Answer

A To-Do in EOS® is a tactical commitment that can and must be completed within seven days. When leaders carry items over week after week, your weekly Meeting Pulse loses its urgency and your accountability culture begins to rot.

To stop the rolling To-Do habit, institute a firm two-week rule. When an item is not completed in seven days, it stays on the list for one more week only. If it is not done by the second week, it cannot remain a To-Do. The Integrator must force one of two decisions during the To-Do review: either the item is dropped entirely because it was not truly essential, or it is immediately converted into an issue and dropped to the bottom of the Issues List.

Pushing an uncompleted To-Do to the Issues List forces the team to confront the underlying constraint. Why did this commitment fail? Was the scope too large? Is the owner lacking the time or resources? Does the Accountability Chart need adjustment?

Do not accept updates like in progress or almost done during the To-Do review. The standard is binary: it is either done or not done. If a leader cannot complete a task in seven days, it was scoped incorrectly during IDS® or it belongs on a quarterly Rock plan. Enforcing this binary boundary quickly brings team To-Do completion back above 90 percent.