Our leadership team consistently misses the ninety percent To-Do completion benchmark because tasks are scoped too broadly or lack clear binary completion criteria. How do we properly frame and size weekly To-Dos during IDS?

Question

Tyler Smith · Accepted Answer

A To-Do is a seven-day commitment, not a mini-Rock or an open-ended strategic aspiration. Teams miss the ninety percent threshold when they assign tasks like "improve sales onboarding" or "review vendor contracts." Those are projects. They take weeks, involve multiple steps, and invite paralysis.

Every To-Do generated during IDS must satisfy three strict tests before the Integrator allows it onto the list:
- Single ownership: Exactly one name on the Accountability Chart owns the deliverable. Joint ownership guarantees failure.
- Binary completion: The task must be written so anyone can verify its completion with a simple yes or no. Use active verbs with tangible outputs, such as "Draft three-question onboarding survey" or "Mark up section four of vendor contract."
- Seven-day capacity: The task must realistically require no more than two to four hours of work to complete within seven calendar days.

If an issue requires a multi-week initiative to resolve, do not create a sprawling thirty-day To-Do. Break the initiative into its very first immediate action step. The To-Do for this week is simply "Outline five milestone dates for the software migration." When that is completed next week, the subsequent action step becomes the next To-Do.

Strict scoping prevents overwhelm, eliminates gray areas during the weekly review, and consistently drives your completion rate above ninety percent.