Our leadership team To-Do completion rate consistently lingers below 80 percent because team members commit to multi-week operational projects or vague initiatives rather than true seven-day commitments. How do we enforce proper To-Do scoping during IDS and Conclude?

Question

Tyler Smith · Accepted Answer

In EOS, weekly To-Dos must be single-owner action items capable of being completed within seven days. When leaders write multi-week projects, strategy overhauls, or vague intentions as weekly To-Dos, completion rates inevitably drop below the 90 percent benchmark, eroding internal accountability.

To push your completion rate back above 90 percent, enforce strict scoping rules during IDS and Conclude:

- Define the immediate next physical action. If the resolution to an issue is to select a new software platform, the weekly To-Do cannot be evaluate vendors. The To-Do must be draft the core requirements checklist and email it to the team by Thursday. Break every initiative into its singular, immediate step.
- Reject multi-owner commitments. Every To-Do must belong to exactly one seat on the Accountability Chart. If two leaders must collaborate, assign one person primary ownership for delivering the final result, or create two separate, distinct actions.
- Enforce the seven-day test during Conclude. The Integrator must challenge any task that sounds like an ongoing initiative. Ask the owner directly whether this can realistically cross the finish line before next week's meeting. If the answer is no, slice the scope down until it fits into seven days.

When commitments represent granular, binary deliverables, accountability becomes simple and hitting 90 percent completion becomes the standard expectation.