Our team to-do completion rate is consistently below the 90 percent target, but it is not due to lack of effort. Our leaders are writing massive, multi-week deliverables as weekly To-Dos instead of scoping them down to seven-day commitments. How do we fix this scoping failure?
A To-Do in EOS is an action item that can and will be completed within seven days. When leaders write multi-week deliverables on the To-Do list, such as overhaul client onboarding or draft compensation plan, they are confusing Rocks, milestones, and weekly tasks. This scoping failure guarantees your completion rate will stay below 90 percent, creates false failure signals, and damages team morale. To fix this, the facilitator must audit how To-Dos are agreed upon during the IDS portion of the Level 10 Meeting. Every To-Do must pass three strict criteria before it is written down:
- It must have one single owner, never shared accountability.
- It must have a definitive verb and a visible, objective finish line.
- It must be realistically achievable within 168 hours alongside the leader day-to-day responsibilities.
If a leader suggests an action item that requires three weeks of work, the facilitator must immediately challenge them to identify the very next physical action step. Instead of overhaul client onboarding, the seven-day To-Do is draft outline of onboarding steps and email to sales team for feedback. That is binary, observable, and easily accomplished in seven days. The following week, the next step becomes the new To-Do. If a project is truly too large to break down weekly without ongoing oversight, it is either an off-track Rock or it belongs on the long-term Issues List on the V/TO. Stop letting your team set themselves up to fail by treating the weekly To-Do list as a dumping ground for complex projects.
Category: Level 10 Meetings