# Delegation

The deliberate transfer of responsibility and appropriate decision authority while the delegating leader retains overall accountability.

- Type: practice
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/delegation/>)

## What it means

Delegation assigns a meaningful outcome to another person and gives them enough authority, information, resources, and support to deliver it. It is not merely distributing tasks or abandoning responsibility. The leader remains accountable for choosing suitable work, setting boundaries, monitoring proportionately, and intervening when risk exceeds the agreed limits.

## Why it matters

Without delegation, leaders become bottlenecks and team members lack opportunities to build judgment. Effective delegation expands capacity, places decisions closer to relevant knowledge, and develops future leaders. It also reveals whether roles, controls, and expectations are clear enough for work to proceed without constant permission seeking.

## When to use it

Delegate when another person can own an outcome with reasonable support and the work offers useful development or better proximity to information. Use more structure for unfamiliar, regulated, irreversible, or high-impact work. Do not delegate duties that law, policy, or role accountability requires the leader personally to perform.

## How it works

1. Choose an outcome suitable for delegation and assess its risk, reversibility, urgency, and development value.
2. Select a person based on capacity and readiness, then discuss interest and support rather than simply assigning extra work.
3. Define the desired result, constraints, decision authority, stakeholders, resources, and evidence of completion.
4. Agree checkpoints according to risk and experience, leaving room for the person to choose methods within the boundaries.
5. Provide access, coaching, and timely decisions while resisting unnecessary takeover or invisible shadow work.
6. Review both the outcome and the delegation process, recognize learning, and adjust future authority.

## A practical example

An engineering manager delegates ownership of a service migration to a senior engineer. They agree on reliability thresholds, budget limits, security review points, and decisions requiring escalation. Weekly checkpoints focus on risks and blocked dependencies. The engineer chooses the sequencing and coordinates stakeholders, then presents lessons that improve the next migration.

## Where it breaks

Delegation can become exploitation when workload increases without authority, recognition, or reprioritization. It may also expose someone to unreasonable risk if expectations are ambiguous or support is withheld. Leaders should account for unequal access to visible assignments and should not use delegation to evade difficult conversations or dump undesirable work repeatedly.

## Common mistakes

- Assigning a task without transferring the authority or context needed to complete it.
- Micromanaging the method after agreeing on an outcome and boundaries.
- Delegating only routine work, denying people meaningful opportunities to develop judgment.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/delegation/#visualization-delegation>)

## Sources

1. [Effective Delegation](<https://www.sussex.ac.uk/organisational-development/leadership-management/delegation>) — University of Sussex · University leadership guidance
2. [Do Your Team a Favor and Start Delegating More](<https://atlassian.com/blog/leadership/how-to-delegate>) — Atlassian · Professional leadership guidance

## Related topics

- [Competency Matrix](<https://wiki.soroush.uk/topic/competency-matrix/>)
- [One-on-One Meeting](<https://wiki.soroush.uk/topic/one-on-one-meeting/>)
- [Team Charter](<https://wiki.soroush.uk/topic/team-charter/>)
