Our leadership team treats the seven-day To-Do list as a rolling thirty-day task list, letting incomplete items roll over for two or three consecutive weeks without consequence. What is the strict protocol for handling To-Dos that are not completed within seven days?
In EOS®, To-Dos are single, actionable commitments designed to be completed within seven days. They are not multi-week projects, and they are not ongoing strategic initiatives.
When a To-Do stays on your Level 10 Meeting™ list for multiple weeks, accountability collapses. The team begins to accept missed deadlines as normal, and your weekly To-Do completion percentage becomes a useless metric.
Here is the exact protocol for handling an incomplete To-Do:
When reviewing the list, the owner reports the task as not done. The facilitator asks one question: 'Will this be completed in the next seven days, yes or no?'
If the owner answers yes, the task receives a single seven-day extension. It stays on the list for one more week.
If the task is still incomplete at the next meeting, it cannot roll over a second time. It must be dropped immediately to the Issues List as an issue for IDS®.
Processing the incomplete task through IDS® forces the team to identify why the work stalled. Did the owner take on a task that was actually a quarterly Rock in disguise? Does the owner lack the capacity, tools, or authority to finish it? Or is the owner failing to manage their calendar?
Do not let incomplete tasks become permanent wallpaper on your agenda. If a task cannot be completed within fourteen days, it is a operational issue that requires a permanent solution.
Category: Level 10 Meetings