ENDE

Delegate well: hand over real ownership

Delegation transfers ownership and decision authority within clear boundaries, not just tasks.

  • Remove bottlenecks
  • Define decision latitude
  • Build ownership

Start a reflection about:

Also helps with:A new managerA reorganization

Delegate in 6 steps

Good delegation transfers more than tasks. It clarifies the outcome, decision latitude, support, and success criteria so ownership can truly shift.

  1. Identify the bottleneck

    Find decisions that wait for you or areas without a clear owner.

  2. Choose the responsibility

    Choose tasks, decisions, or areas you can meaningfully hand over.

  3. Match the owner

    Choose someone with the right skills, capacity, and development goals.

  4. Define the latitude

    Agree on the outcome, decision rights, boundaries, support, and escalations.

  5. Manage the transition

    Transfer responsibility in stages. Reduce support as confidence grows.

  6. Review success

    Define how you will recognize a good outcome and growing independence.

When this method helps

Use this method when decisions depend on you or someone is ready for greater ownership.

Key benefits

  • Builds judgment through real decisions
  • Removes recurring bottlenecks
  • Clarifies authority and escalations
  • Strengthens ownership of outcomes

Limits and when to pause

Without enough authority, context, capability, or support, delegation transfers risk—not ownership. Keep accountability and escalation boundaries explicit.

Delegation examples

The six steps stay the same whether you hand over a recurring task, a type of decision, or a whole area. What changes is how much latitude and support the person needs. Each example shows the steps separately and then how you could hand it over in one conversation.

A recurring task

Hand over regular work, including the decisions that come with it.

Illustrative scenario

Identify the bottleneck
Every customer update and follow-up question goes through the team lead. Last month, customer questions waited two days on average for an answer.
Choose the responsibility
Lena takes over preparing and coordinating the weekly customer update.
Match the owner
She knows the project data and wants to develop her customer communication skills. To free the hour a week it takes, the team lead moves her sprint report to a colleague.
Define the latitude
She decides the content and sends it herself. Schedule changes and pricing commitments need the team lead's agreement.
Manage the transition
They prepare two updates together. Lena then works independently with a short approval check.
Review success
The update goes out every Thursday. After four weeks, it needs no corrections, follow-ups go straight to Lena, and the approval check ends.
How you could hand it over
Lena, from next week I'd like you to own the weekly customer update. You decide what goes in and send it yourself. Only schedule changes and pricing commitments come to me first. We'll write the next two together, and after that I'll take a short look before you send it. If it goes out every Thursday for four weeks without corrections, I'll stop checking.

Decision rights

Hand over a type of decision that currently waits for you.

Illustrative scenario

Identify the bottleneck
Every bug priority for the mobile app waits for the team lead's weekly triage. 40 bugs are open, and a new bug waits nine days on average for a priority.
Choose the responsibility
Tom takes over bug triage: he sets priorities and decides who in the team fixes what.
Match the owner
Tom has worked on the app for three years and knows the code best. He wants to take on more lead responsibility next year.
Define the latitude
He decides priorities and assignments within the team. Bugs that would move the release date or need another team go to the team lead.
Manage the transition
They run the next two weekly triage sessions together. For the month after that, Tom runs them alone and the team lead reads the list once a week.
Review success
New bugs get a priority within two working days. After six weeks, the team lead no longer takes part in triage.
How you could hand it over
Tom, I'd like you to take over bug triage for the app. You decide the priorities and who fixes what. Only bugs that would move the release date or need another team come to me. We'll run the next two sessions together. After that, you run them, and for a month I'll read the list once a week. The goal is that every new bug has a priority within two working days.

An area without an owner

Give a neglected area one person who decides about it.

Illustrative scenario

Identify the bottleneck
Nobody owns the build pipeline. In six months, build time has grown from 12 to 25 minutes, and three people fix breakages whenever they happen to notice them.
Choose the responsibility
Priya becomes the owner of the build pipeline: its speed, reliability, and tools.
Match the owner
Priya has fixed most of the breakages so far and wants to move toward platform work. She gets up to one day a week for it, and her feature work shrinks to match.
Define the latitude
She decides on tools and changes within the existing budget. New costs over €500 a month, or changes that block merges for the whole team, need the team lead's agreement.
Manage the transition
She presents a plan within two weeks. For the first two months, they meet every two weeks, then monthly.
Review success
Build time is under 15 minutes by the end of the quarter. Questions about the pipeline go to Priya, not the team lead.
How you could hand it over
Priya, I'd like you to own the build pipeline: its speed, reliability, and tools. You can spend up to one day a week on it, and I'll reduce your feature work to match. You decide on tools and changes. New costs over €500 a month, or anything that blocks merges for everyone, we agree on first. Could you bring a plan in two weeks? The goal is under 15 minutes by the end of the quarter.

Each handover says what the person decides alone and what still comes to you. Match decision latitude, support, and review points to the person’s experience and the risk.

Assigned or delegated?

Assigning hands over work. Delegating also hands over the decisions that come with it, within clear limits. Often, one sentence makes the difference.

  • Assigned“Can you take care of the customer update from now on?”

    Delegated“From next week, you own the customer update. You decide what goes in and send it yourself.”

  • Assigned“Just run everything by me first.”

    Delegated“Bugs that would move the release date come to me. Everything else you decide.”

  • Assigned“Let me know if you need anything.”

    Delegated“We'll run the next two sessions together. After that, I'll read the list once a week for a month.”

In the assigned version, the decisions stay with you, and so do the questions. The delegated version says what the person decides, where the limit is, and when your support gets lighter.

Template: hand over ownership

Copy the template and replace each bracket with your own case.

From [date], I'd like you to own [task, decision or area]. Right now, [what waits for me and for how long]. I'm asking you because [why this person]. You decide [what they decide alone]; [what still needs my agreement] we agree on first. At the start, we [support and check-ins]; after [period], [what gets lighter]. It's working when [success criterion].

Check before you say it

  • Identify the bottleneck: Can you say what waits for you today, and for how long?
  • Choose the responsibility: Does it include decisions, not only the work?
  • Match the owner: Does the person have the time, or do you take something else off their plate?
  • Define the latitude: Is it clear what they decide alone and what comes to you?
  • Manage the transition: Is there a date when your support gets lighter?
  • Review success: Could both of you check it, for example against a date or a number?

Questions Reflacto asks

Delegation is a general management practice, not a published model with fixed steps. Four questions follow that practice: what you hand over, who takes it on, the authority and support they need, and a gradual transition. Reflacto added the first question, about where ownership is stuck today, and the last, about how you will know it worked.

Ownership clarity

Hand over tasks, decisions, or areas so that someone else truly owns them.

  1. 1What ownership or empowerment challenges are you seeing?Added by Reflacto
  2. 2What tasks, decisions, or areas can be delegated?Delegation practice
  3. 3Who is best positioned to own each delegated item?Delegation practice
  4. 4How will you set each person up for success in their new ownership?Delegation practice
  5. 5How will you transition ownership gradually and safely?Delegation practice
  6. 6How will you measure empowerment success?Added by Reflacto

After the last question, Reflacto shows a delegation plan with concrete next steps.

Questions about using delegation

Before you hand over

How do I know if I'm the bottleneck?

Decisions wait for you, projects slow without you, and people bring proposals for approval instead of completed work.

You could say
“Which decisions waited for me this week?”

For one week, write down what waits for you and for how long. That list is your first shortlist for delegation. Example: decision rights

What should I delegate first?

Something that recurs, where a mistake shows but can be undone, and that someone wants to learn.

You could say
“Would you like to take over bug triage? I'll still decide anything that moves the release.”

A task like that lets the person practise real decisions while the risk stays small. Widen the latitude once it works. Example: a recurring task

The handover

What's the difference between delegating and assigning work?

Assignment transfers work; delegation transfers decisions. If the person cannot choose another route, the work was only assigned.

You could say
“You decide which bugs get fixed this sprint. Only changes to the release date come to me.”

Name both: what the person decides and where the limit is. Assigned and delegated side by side

How do I delegate without micromanaging?

Control the outcome, not the route. Agree on the goal, quality bar, decision latitude, check-ins, and escalations before the handover.

You could say
“Let's talk it through every other Tuesday. In between, you decide.”

Agree on check-ins in advance and stick to them. Unplanned “quick looks” are what feels like micromanaging. Template for the handover

When it gets difficult

What if they do it worse than I would?

Check whether the result is good enough and mistakes are reversible. If so, let it stand and talk it through afterwards.

You could say
“What would you do differently next time?”

Early attempts may be weaker. Correct what matters for the result, not your personal style. Avoiding temporary learning costs can preserve a permanent bottleneck.

What if they bring every decision back to me?

Ask for their proposal first, and decide only what lies outside the agreed latitude.

You could say
“What would you do? If it's within the budget, go ahead.”

Frequent escalations usually mean the limits are unclear or the person fears the consequences of a mistake. Find out which it is. Example: an area without an owner

About the method

When shouldn't I delegate?

When the person lacks the authority, time, or context to decide, or when you only want to get rid of an unpleasant task.

You could say
“I'd like you to own this, and in return I'll take the release notes off your plate.”

Without authority and support, delegation transfers risk, not ownership. Decisions about pay, performance reviews, or confidential matters usually stay with you. Limitations

Is Delegation and Empowerment an established framework?

Not as a single model. Delegation and empowerment are general management practices with no single owner, and the six questions are Reflacto's own structure.

Research supports the underlying idea: in 1995, Gretchen Spreitzer defined psychological empowerment through meaning, competence, self-determination, and impact. Four of the six questions follow common delegation practice; Reflacto added the others. Origin and sources

Origin and Reflacto's adaptation

Delegation and empowerment are general management practices with no single owner. Gretchen Spreitzer formally defined psychological empowerment in a 1995 Academy of Management Journal study.

Also known as: employee empowerment, delegation of authority

What Reflacto changed

From delegation practice
From general delegation practice: what to hand over, who takes it on, the authority and support they need, and a gradual transition.
Added by Reflacto
Reflacto adds a look at where ownership is stuck today and indicators that show whether empowerment works.

See every question Reflacto asks

Primary sources and further reading

Editorially reviewed by Daniel Schmeiß

Last substantive review: September 29, 2026

Related reflection methods

Compare another method that approaches a similar situation from a different angle.

Compare all methods