Delegation Ladder
Delegation breaks not because "people cannot handle it," but because the manager hands work over without structure: verbally, without result criteria, without an acceptance point. Then control is possible only one way — asking constantly. The delegation ladder is a sequence of steps: on each one the manager gives away more routine and keeps less manual control.
Climb the ladder gradually: each step relies on the previous one.
Step 1. An Assignment Becomes a Task
A verbal assignment is the most fragile form of work: it lives in the memory of two people and dies first. The rule is simple: a decision without a task does not exist. Every assignment is recorded as a task with an assignee and a deadline — at the moment it is given, not "in the evening."
What it gives you: assignments stop getting lost, and the "but I asked you" question disappears — there is a card, a deadline, and a history. How to assign a task properly is covered in Create a Task; how to keep assignments under control — in the scenario Manager Assignment Control.
Step 2. The Task Gets Acceptance Criteria
A "make a website" task delegates activity, but not a result. To hand over a result, the task must contain:
- a description of the expected result — what will be ready and how to verify it;
- a checklist of verifiable steps if the result is composite — see Add a Checklist;
- files and materials next to the work — see Attach Files to a Task;
- an acceptance point: the reporter checks the result and either closes the task or returns it for rework with a specific comment — see Review and Close a Task.
What it gives you: the "done / not done" argument is replaced by a check against criteria. The manager stops being the bottleneck during execution — they are needed only at the acceptance point.
Step 3. Repeated Work Becomes a Template
If a task is being assigned for the second or third time, its structure — description, checklist, roles, deadlines — should live in a template (see Templates, Recurring Tasks, and Automation), not in the manager's head. A template is a regulation in executable form: a new employee gets a ready work structure instead of a verbal briefing.
What it gives you: the quality of task setup stops depending on who assigns the task and in what mood.
Step 4. The Schedule Creates Tasks by Itself
Regular work — reports, reconciliations, checks, renewals — should not depend on the manager's memory. Recurring tasks are created on schedule with the right assignee and checklist.
What it gives you: the manager no longer "nudges" the regular routine. If a recurring task is overdue, it is visible in the slice like any other overdue work.
Step 5. A Staged Process Becomes a Workflow
When work passes through several roles and stages — contract approval, hiring, shipping — it is run by a workflow (see Workflows): a route, step owners, conditions, and branches. Critical points are closed by Operation guards: for example, a task cannot be closed without the final file.
What it gives you: the process runs the same way no matter who started it. Control is built into the route instead of relying on attentiveness.
Step 6. Control Through Slices Instead of Questions
The top step: the manager does not participate in the routine at all — they watch deviation slices (overdue, no assignee, acceptance, overload) in Task List, Filters, and Views as part of their Manager's Weekly Rhythm and intervene only in exceptions.
What it gives you: not only the work is delegated, but also the control over it. The manager's attention goes to development, not supervision.
Small team: reaching steps 3–4 is enough. Do not build workflows for the sake of two people — templates and recurring tasks cover most of the routine.
Large department or enterprise: steps 5–6 are mandatory. At the scale of dozens of people, only processes with operation guards and slice-based control stay stable; personal supervision does not scale. Appoint a process owner — someone who maintains templates, rules, and routes as a product.
Common Delegation Mistakes
- Delegated activity, not a result. The task has no criteria — acceptance turns into an argument.
- No acceptance point. The assignee closes the task "by feel," and the manager learns about the problem from the client.
- Reverse delegation. The assignee returns the work with a "but how?" question, and the manager does it themselves. The right answer is to clarify the criteria in the task and return the responsibility.
- Skipping steps. Automating a process that does not work manually means automating chaos.
- Delegation without permissions. The assignee lacks access to the client, files, or section — check access at handover, see Assign Participants.
How to Know It Is Time for the Next Step
- You repeat the same assignment — time for a template.
- You remind people about regular work — time for a schedule.
- Work gets lost between roles — time for a process.
- You ask status questions — time for slices.