A major reason our weekly To-Do completion rate drops below ninety percent is that our leaders claim they are constantly waiting on other departments to finish their part of the task first. How do we stop this cross-departmental finger-pointing during our reviews?

Question

Tyler Smith · Accepted Answer

When a leadership team member misses a weekly To-Do and points the finger at a colleague, you have a breakdown in both accountability and task design. Allowing this excuse to pass without consequence destroys trust and teaches your team that they can escape accountability simply by blaming others.

In your Level 10 Meeting™, you must enforce a foundational rule: only one name can be accountable for a To-Do. If you accept a To-Do, you own the outcome, not just your individual contribution. If you need input from a colleague to complete your task, it is your job to chase them down, set internal deadlines, and escalate the issue early if they do not cooperate.

To eliminate this finger-pointing, you must change how you write To-Dos during IDS®. If a project requires cross-departmental collaboration, do not create one massive, shared To-Do. Instead, break it down into sequential, highly specific individual To-Dos.

For example, if the marketing lead needs data from sales to build a campaign, do not write a To-Do that says: 'marketing team launch campaign'. Instead, write two distinct tasks. First: sales lead deliver data to marketing lead by Friday. Second: marketing lead build campaign by next Tuesday.

Each leader is now solely accountable for their specific link in the chain. If the sales lead misses their Friday deadline, they own the miss. The marketing lead is protected because their task was dependent on an input that did not arrive, and they can show they actively managed the process. This structural clarity stops the blame game and keeps your execution metrics clean.