Members of our leadership team frequently let incomplete To-Dos roll over from week to week, treating seven-day commitments as flexible deadlines. How do we eliminate casual To-Do rollovers without creating a toxic work environment?

Question

Tyler Smith · Accepted Answer

A To-Do in EOS is a firm commitment to complete an action item within the next seven days. When a leadership team tolerates rolling To-Dos over for two, three, or four consecutive weeks, accountability evaporates. If a commitment has no consequence for slipping, leaders will naturally prioritize daily operational firefighting over their weekly Level 10 commitments.

During the To-Do list review, the standard is binary: To-Dos are either reported as "Done" or "Not Done." There is no third category called "In Progress" or "Almost Finished." If a To-Do is not 100 percent complete, it is marked "Not Done."

When an item is reported as Not Done for the first time, it can stay on the list for one additional week if there is a legitimate operational roadblock. However, if the same To-Do is Not Done for a second consecutive week, it cannot simply be pushed forward again. The Integrator must drop it straight down to the Issues List.

In IDS, the team unpacks why the commitment failed. Is the person in the wrong seat? Was the task scoped unrealistically? Did a structural dependency block execution? Or did the owner simply fail to prioritize their commitment? By forcing repeat failures into IDS, you treat stalled execution as an operational defect to be solved rather than an acceptable habit to ignore.