A single leader on our team regularly completes only half of their weekly To-Dos, always blaming unpredictable operational emergencies in their department. How do we hold one chronic underperformer accountable during the Level 10 Meeting without burning IDS time?

Question

Tyler Smith · Accepted Answer

The weekly To-Do review is binary: done or not done. It is not an invitation to explain why something failed to happen. When a single leader routinely delivers at 50 percent and begins justifying the miss with fire drills, the Integrator must cut off the storytelling instantly.

During the Level 10 Meeting, simply mark the item not done, leave it on the list for one more week, and move on. Do not allow the room to get dragged into a ten-minute debate during the reporting block. Once the meeting reaches the Issues List, drop that seat chronic To-Do failure onto the list as a priority issue for IDS.

When you IDS the problem, focus on root cause:
- Is the leader committing to tasks that take longer than seven days? If so, the tasks must be scoped down into seven-day bites.
- Are they operating without delegated authority, forcing them to personally fight frontline fires instead of leading their seat? That is an Accountability Chart problem.
- Are they agreeing to tasks in the room just to please the group, knowing they have no bandwidth to execute? That is a lack of open honesty.

If this pattern persists past two consecutive quarters, this ceases to be a scheduling friction and becomes a GWC issue. Capacity means having the mental and physical bandwidth to do the job. A leader who cannot deliver seven-day commitments consistently does not have the capacity for their seat.