Our weekly To-Do completion rate regularly drops below ninety percent, but team members insist their carried-over tasks were blocked by other departments. How do we eliminate these excuses?
When a leadership team repeatedly misses the ninety percent To-Do threshold and blames external friction, you are dealing with poorly defined tasks, not cross-departmental blockages. A To-Do is designed to be a realistic, seven-day action step that a single person completely controls.
The first correction is how you write the To-Do during IDS. Tasks often fail because they are scoped as mini-projects rather than discrete commitments. Writing a task like fix billing friction invites failure. Instead, write call accounting manager and verify disputed line items. If a task requires input from another department, the owner of the task is responsible for securing that input within forty-eight hours, not waiting until day six and crying foul.
The second correction is holding a single neck accountable. In EOS, a To-Do can have only one name attached to it. If marketing needs sales data to finish an asset, do not create a shared task. Assign the data pull to sales with a deadline of Tuesday, and assign the asset review to marketing for Thursday.
Finally, treat the weekly review as a binary check. When reviewing To-Dos, the only acceptable answers are done or not done. Explanations and apologies are banned. If a leader says not done, the item drops straight to the bottom of the Issues List if it is critical, or it rolls over exactly once. If it is not done the following week, the leader must answer why they committed to an action they could not execute.
Category: Level 10 Meetings