Our team To-Do completion rate consistently falls below 90 percent because leaders accept action items with multi-week scopes or vague deliverables during IDS. How do we tighten To-Do creation so every commitment is genuinely executable in seven days?

Question

Tyler Smith · Accepted Answer

A To-Do completion rate below 90 percent points directly to sloppy issue solving. When teams leave IDS with broad aspirations instead of concrete action steps, execution inevitably collapses.

By EOS definition, a To-Do must be a binary, single-owner action item that can be completed within seven days. If a task requires three weeks of work, it is not a To-Do. It is either an off-track Rock or a complex project that the team failed to break down properly during IDS.

The Integrator must police To-Do formulation at the moment an issue is marked solved. Enforce a strict construction standard: verb, deliverable, owner. Banish vague verbs like explore, review, oversee, or research. Replace them with concrete commitments: call, email, draft, deliver, or approve.

For example, explore new shipping vendors is an unexecutable task that will sit open for three weeks. Email three vendor rate sheets to the warehouse manager by Monday is a crisp, seven-day action item. The former guarantees a sub-90 percent completion rate; the latter produces traction.

Additionally, assign each To-Do to exactly one name on the Accountability Chart. Never assign an item to two people or a department. When two people own a task, nobody owns it. If an action requires collaboration, assign the To-Do to the person responsible for initiating the first step. Keep the scope ruthlessly small, drive completion above 90 percent, and watch operational momentum return.