Team members regularly bring To-Dos to our Level 10 Meeting™ that cannot possibly be finished in seven days, causing items to roll over repeatedly and clutter our list. How do we enforce the seven-day rule for action items without micromanaging?
A To-Do that takes three weeks to finish is not a To-Do. It is either a multi-step project or an unacknowledged quarterly Rock. When you allow multi-week tasks to sit on your weekly list, your meeting pulse loses its sense of urgency, and the accountability of the seven-day commitment evaporates.
To enforce the seven-day rule, the Integrator or facilitator must act as a strict gatekeeper during the Solve step of IDS:
- Never record a project milestone as a single To-Do. If someone says their action item is to rewrite the employee handbook, reject it immediately. That is a thirty-day project. Instead, force them to commit to the immediate seven-day step: Draft sections one and two of the handbook and email them to the team.
- Require binary deliverables. Every To-Do must be phrased with a clear completion condition. Instead of work on website copy, write deliver final draft of homepage copy to marketing lead.
- Convert runaway issues into Rocks. If solving an issue clearly requires twenty or thirty hours of concentrated work that cannot be broken into simple weekly handoffs, stop treating it as a weekly issue. Move it to the long-term Issues List on your V/TO® to be prioritized as a Rock at your next quarterly planning session.
Keeping To-Dos strictly limited to seven-day increments keeps the list short, forces clear scoping, and protects your 90 percent completion standard.
Category: Level 10 Meetings