In our departmental Level 10 Meetings, the department manager ends up assigned to nearly eighty percent of the weekly To-Dos generated in IDS, creating an operational bottleneck. How do we force delegation and accountability across the whole departmental team?

Question

Tyler Smith · Accepted Answer

When a manager absorbs eighty percent of the departmental To-Dos, it is usually evidence of one of two problems: either the manager refuses to let go of the vine, or the frontline team lacks the capability to execute their seats under GWC (Get it, Want it, Capacity to do it).

The purpose of rolling Level 10 Meetings down to departments is to build distributed accountability. If the manager walks out of every meeting with twelve new tasks while their team leaves with one apiece, the departmental pulse is actively reinforcing dependency rather than eliminating it.

To stop this bottleneck, the manager must change how issues are resolved during the Solve stage of IDS®. When an issue is tackled and an action step is identified, the default assumption must be that someone other than the department manager owns the deliverable.

During the Conclude section, enforce these rules:
- A single owner for every To-Do. No shared ownership between the manager and an employee.
- The manager may not accept more than two weekly To-Dos unless an emergency requires their direct executive authority.
- Frontline supervisors and specialists must define their own action steps.

If a frontline team member claims they cannot take a To-Do because they do not know how, that is not an excuse for the manager to take it. It is an immediate signal that the employee lacks training or does not belong in the seat. The manager's sole To-Do in that situation is to provide the training, not do the work.

Force accountability downward. If the team drops balls at first, let them experience the friction during the next weekly pulse. That discomfort is how operational independence is built.