Marcus Andrey Study
Ler em português Library

Framework · People leadership · 3 min read

Delegation levels

A five-level scale for how much authority you hand over, from "look into it and report back" to "decide and act, no need to tell me", so you and the designer agree on it before the work starts.

  1. 1 Investigate
    You say
    Look into it and report back. I'll decide.
    For example
    Gather how other teams handle bulk edits
  2. 2 Recommend
    You say
    Recommend options. I'll decide.
    For example
    Two filter layouts with pros and cons
  3. 3 Decide, ask
    You say
    Decide, but tell me before acting.
    For example
    Pick the layout, show me before handoff
  4. 4 Act, tell
    You say
    Decide and act, then tell me.
    For example
    Ship the copy fixes, share them in our 1:1
  5. 5 Own it
    You say
    Decide and act. No need to tell me.
    For example
    Run the design system triage each week

Pick one level explicitly and say it out loud.

The five levels of delegation. Each step up moves more of the decision to the designer.

Use it when

  • You hand a designer a problem and want them to own it without you hovering.
  • A designer keeps asking for approval on decisions you expected them to make, or makes decisions you expected to see first.
  • You are delegating outcomes ("reduce time-to-find in the order list"), not tasks ("make the panel blue"), and need to say how far their authority goes.

How to use it

  1. Frame the outcome, not the task. Describe the problem, who it affects and what good looks like. Leave the solution to them. Output: one or two sentences that state the outcome.
  2. Check their experience with this kind of task. Rate the task, not the person: a senior designer can still be new to a type of work. This is the same idea as Situational leadership. Output: new, some, or proven for this task.
  3. Check the risk if it goes wrong. Think about users, deadline and standards. A mistake in a quiet internal screen costs less than one in a flow that 2,000 operators use every day. Output: low, medium, or high risk.
  4. Pick one level and say it. Use the exact sentence from the scale ("Decide, but tell me before acting"). Write it in your shared 1:1 doc. Output: an agreed level, in writing.
  5. Agree the checkpoints upfront. Set dates, for example "direction review Thursday, pre-handoff review next Wednesday". At each one, ask "what are you worried about?" before you give your opinion. Output: two or three dated check-ins.
  6. Raise the level when it goes well. After a task lands well, offer the next level for the next similar task. Only step in on the work if it threatens user outcome, deadline or standards, and say which one. Output: the level for next time.

Worked example

Pick the designer's experience with the task and the risk if it goes wrong. The widget recommends a level and tells you what to say.

A fictional designer is taking over a redesign of the exceptions list in an internal operations tool. Pick their experience and the risk to see which level to delegate at.

Their experience with this kind of task
Risk if it goes wrong
  1. 1 Investigate
  2. 2 Recommend
  3. 3 Decide, ask
  4. 4 Act, tell
  5. 5 Own it

Rule: experience points (new 0, some 1, proven 2) + risk points (high 0, medium 1, low 2) + 1 = level.

Watch out for

  • Leaving the level implicit. "Can you take a look at this?" could mean level 1 or level 5. Name the number or say the sentence.
  • Taking it back at the first wobble. If you delegated at level 4 and grab the work when it gets messy, you teach them that the level means nothing. Coach at the checkpoint instead.
  • Giving level 5 without context. Full authority without the goal, the constraints and the users is abandonment, not trust.
  • One level per person. The level belongs to a task. The same designer can be at level 5 for UI copy and level 2 for a stakeholder presentation.

Template

Copy this into your shared 1:1 doc each time you hand something over.

Outcome:          (what problem, for whom, what good looks like)
Owner:
Level:            1 Look into it and report back. I'll decide.
                  2 Recommend options. I'll decide.
                  3 Decide, but tell me before acting.
                  4 Decide and act, then tell me.
                  5 Decide and act. No need to tell me.
Why this level:   (experience with this task / risk if it goes wrong)
Checkpoints:      (date: direction review) (date: pre-handoff review)
I step in only if it threatens: user outcome / deadline / standards
Next time:        (level for the next similar task)

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close