Our leadership team To-Do completion rate consistently sits below 80 percent because team members assign action items to their direct reports who are not in the room, resulting in missed handoffs and finger-pointing. How do we fix To-Do accountability when tasks rely on subordinate execution?
In EOS, there is an unbending rule for the Level 10 Meeting: an action item cannot be assigned to someone who is not sitting in the room. The moment you record a direct report's name on the leadership team To-Do list, you break accountability. The absent employee has no context on the IDS discussion, cannot push back on the scope, and never gave a personal commitment to hit a seven-day deadline.
Whoever sits at the leadership table owns 100 percent of the accountability for the To-Do. If the solution to an operational problem requires financial modeling from a junior analyst, the Head of Finance takes the To-Do. Their action item is not 'have analyst build model.' Their action item is 'deliver finished model by next Tuesday.' If the analyst gets sick or drops the ball, the Head of Finance still owns the failure because they accepted the commitment.
This simple rule forces department heads to scope seven-day commitments realistically. They stop treating the leadership To-Do list as an executive task-delegation board and start treating it as their personal commitment register. When a leader realizes their own completion percentage and reputation drop every time a subordinate fails to deliver, they manage their team with tighter urgency and only commit to deliverables they can personally inspect and guarantee within seven days.
Category: Level 10 Meetings