We have individual accountability, but when our overall leadership team to-do completion rate drops below ninety percent, we struggle to hold the entire group collectively responsible without playing the blame game. How does the Integrator address a collective drop in traction while maintaining team unity and respect?

Question

Tyler Smith · Accepted Answer

When your team's collective to-do completion rate falls below the ninety percent mark, it is easy to default to personal finger-pointing or defensive excuses. This reaction violates the Same Page pillar of your charter, which requires the team to operate as a unified front held by mutual respect.

The Integrator must address a collective drop in traction by focusing on the workflow, not the personalities. Start by reviewing the to-do list together during the next Level 10 Meeting and asking a simple question: Are we setting realistic weekly commitments, or are we overpromising to look good in the meeting?

Often, a drop in completion is a symptom of poor prioritization during the IDS process. The team may be creating too many low-priority tasks that distract from the main goals. Encourage the team to challenge each other during the Solve phase of IDS. Before a to-do is written down, ask if it is absolutely necessary to solve the issue, or if it is just busywork.

If the workload is realistic but execution is still lagging, the Integrator must remind the team that they win or lose as a unit. A drop in execution affects everyone. By shifting the conversation to shared operational standards rather than individual failures, you maintain trust while restoring execution.