Our weekly to-do completion rate sits around 65 percent because the action items generated during IDS are written as open-ended, multi-week projects instead of concrete seven-day deliverables. How do we tighten our to-do creation so tasks can actually be completed in seven days?

Question

Tyler Smith · Accepted Answer

A to-do in the Level 10 Meeting™ is a binary commitment designed to be completed within seven days. When completion falls below 90 percent, the problem is almost always that you are logging mini-projects, research assignments, or ongoing operational habits instead of finished actions.

Every to-do must pass the seven-day test. If a leader cannot hand you the completed deliverable by the next meeting pulse, it is not a to-do. It is either an undocumented milestone or a quarterly Rock.

To fix this, the facilitator must enforce strict formatting before any item is recorded. Every to-do must have one single owner, a clear action verb, and a binary finish line. Replace vague entries like "Work on pricing model" with "Email redlined pricing model to John by Thursday." Replace "Review vendor options" with "Schedule demo with top two CRM vendors."

If an IDS® resolution requires a multi-week initiative, break it into seven-day chunks. The to-do for this week is only the first immediate step, such as gathering baseline data or drafting an outline. Once that step is checked off next week, the next seven-day action item gets created.

Hold the line during the conclude phase of the agenda. The scribe reads each to-do aloud. If the owner hesitates, asks for two weeks, or cannot define what done looks like, the facilitator stops the room and forces the team to slice the deliverable in half.