Our team members are checking off their weekly to-dos as complete during our Level 10 Meeting, but we frequently discover later that the actual work was only half-done or lacked the quality needed, causing operational friction. How do we enforce a strict standard for what done actually means?

Question

Tyler Smith · Accepted Answer

When team members check off weekly to-dos in your Level 10 Meeting that are actually incomplete or substandard, they are destroying the team's accountability. A to-do is not a task that was merely started, nor is it a draft that was sent without follow-through. Allowing this behavior to continue teaches the team that checking the box is more important than achieving the actual operational result.

You must establish a clear, non-negotiable definition of what done means for your weekly tasks. In the EOS framework, a to-do is only complete when the objective is fully realized and the outcome is delivered to the internal or external customer. If a task requires a document to be finalized, it is not done when the draft is written; it is done when the document is published and the stakeholders are notified.

During the to-do review section of your weekly Level 10 Meeting, the facilitator must audit the list strictly. Do not just read the task and accept a quick yes. If a critical task is marked complete, ask the owner to confirm the outcome in one sentence. For example, ask, is that process fully uploaded and live? If the answer reveals that there are still outstanding steps, the facilitator must change the status back to incomplete and keep it on the list for the next week. Enforcing this level of operational integrity ensures that your ninety percent weekly to-do completion rate is a real measure of progress, not a superficial metric.