Mentor designers by handing over decisions

Mentor designers by handing over decisions

Mentor designers by handing over decisions

Design process

The short answer

If every screen waits for your sign-off, you're approving, not mentoring. Ask designers to bring a decision, the evidence behind it, what they're unsure of and the feedback they want. Then hand over one kind of decision at a time, and say out loud how far each one is handed over.

If every screen waits for your sign-off, you're approving, not mentoring. Ask designers to bring a decision, the evidence behind it, what they're unsure of and the feedback they want. Then hand over one kind of decision at a time, and say out loud how far each one is handed over.

Original mobile concept in charcoal and bright yellow-green. A team app called Reviews shows a review request from a designer about onboarding order, at the Advise level: you decide, I advise. Decision: move account setup after the first project. Evidence: test users stalled at setup. Unsure: whether admins need setup first. Feedback wanted: is the admin risk worth it? Next: test the new order with admins. Who decides: you, the designer. Lead: advises, then steps back. Note: no sign-off needed at this level. Buttons: Add evidence and Ask for feedback. Beside the phone, a dithered staircase of seven steps with a solid yellow-green block on step five and a dotted outline of the block on step six. Text: Illustrative concept. Bring the decision. Then hand it over, one step at a time.
Original mobile concept in charcoal and bright yellow-green. A team app called Reviews shows a review request from a designer about onboarding order, at the Advise level: you decide, I advise. Decision: move account setup after the first project. Evidence: test users stalled at setup. Unsure: whether admins need setup first. Feedback wanted: is the admin risk worth it? Next: test the new order with admins. Who decides: you, the designer. Lead: advises, then steps back. Note: no sign-off needed at this level. Buttons: Add evidence and Ask for feedback. Beside the phone, a dithered staircase of seven steps with a solid yellow-green block on step five and a dotted outline of the block on step six. Text: Illustrative concept. Bring the decision. Then hand it over, one step at a time.

Illustrative concept, not client work or measured results.

Approving isn't mentoring

When a junior designer shares a screen and asks "is this OK?", the quick answer is a yes or a redline. It feels like mentoring. Mostly it teaches them to wait for you.

The skill they need next is different. The UK government's interaction designer framework expects a junior designer to "explain design decisions" and "work independently after being given direction by more senior designers." One level up, a designer is "trusted to make good decisions" and can "recognise when to ask for further guidance and support." Senior and lead designers mentor others. Read as a ladder, the path runs from explaining decisions to being trusted with them.

So a mentor's job isn't to become a faster approver. It's to move decisions across, at a pace the designer can handle. That's my view from hiring designers at entry level, in game studios and in enterprise software, and seeing some of them grow into senior roles while they reported to me. It's an opinion, not a measured result.

Approving isn't mentoring

When a junior designer shares a screen and asks "is this OK?", the quick answer is a yes or a redline. It feels like mentoring. Mostly it teaches them to wait for you.

The skill they need next is different. The UK government's interaction designer framework expects a junior designer to "explain design decisions" and "work independently after being given direction by more senior designers." One level up, a designer is "trusted to make good decisions" and can "recognise when to ask for further guidance and support." Senior and lead designers mentor others. Read as a ladder, the path runs from explaining decisions to being trusted with them.

So a mentor's job isn't to become a faster approver. It's to move decisions across, at a pace the designer can handle. That's my view from hiring designers at entry level, in game studios and in enterprise software, and seeing some of them grow into senior roles while they reported to me. It's an opinion, not a measured result.

Change what people bring to a review

Start with the request itself. The GOV.UK "Get Feedback" crits, a pilot described by Jeremy Yun and Kara Kane in May 2021, used "project summary cards to help presenters define their work and the type of feedback they want." Each session also gave people roles: a facilitator, a presenter and feedback givers.

That's a crit format, not a mentoring programme, but the card idea travels to a one-to-one. Ask for the decision they made, the evidence behind it, what they're unsure about, the feedback they want, and what they'll try next. When the designer writes that down, your feedback answers their question instead of replacing their thinking.

Hand over one kind of decision at a time

Management 3.0's Delegation Poker makes the handover visible. "Delegation is not a binary thing," it says, and "Delegation is a step-by-step process." It names seven levels, from Tell ("I will tell them") through Consult ("I will consult and then decide"), Advise ("I will advise but they decide") and Inquire ("I will inquire after they decide") to Delegate. A delegation board lists decision areas against those levels, so everyone can see how far authority goes in each one.

For a designer, that might mean copy and spacing within the design system sit at Inquire, a new flow sits at Advise, and a scope trade-off with product stays at Consult for now. After a run of good calls in one area, move that area one step. The page also warns that delegation is context-dependent: go too far and "chaos might unfold."

Handing over a decision isn't leaving. Keep crit open, so the designer still gets feedback without needing your approval.

Change what people bring to a review

Start with the request itself. The GOV.UK "Get Feedback" crits, a pilot described by Jeremy Yun and Kara Kane in May 2021, used "project summary cards to help presenters define their work and the type of feedback they want." Each session also gave people roles: a facilitator, a presenter and feedback givers.

That's a crit format, not a mentoring programme, but the card idea travels to a one-to-one. Ask for the decision they made, the evidence behind it, what they're unsure about, the feedback they want, and what they'll try next. When the designer writes that down, your feedback answers their question instead of replacing their thinking.

Hand over one kind of decision at a time

Management 3.0's Delegation Poker makes the handover visible. "Delegation is not a binary thing," it says, and "Delegation is a step-by-step process." It names seven levels, from Tell ("I will tell them") through Consult ("I will consult and then decide"), Advise ("I will advise but they decide") and Inquire ("I will inquire after they decide") to Delegate. A delegation board lists decision areas against those levels, so everyone can see how far authority goes in each one.

For a designer, that might mean copy and spacing within the design system sit at Inquire, a new flow sits at Advise, and a scope trade-off with product stays at Consult for now. After a run of good calls in one area, move that area one step. The page also warns that delegation is context-dependent: go too far and "chaos might unfold."

Handing over a decision isn't leaving. Keep crit open, so the designer still gets feedback without needing your approval.

Illustrative concept: How far each decision is handed over. A delegation board with seven levels: 1 Tell, 2 Sell, 3 Consult, 4 Agree, 5 Advise, 6 Inquire, 7 Delegate. Copy and spacing in the system is at Inquire, next Delegate. Choosing a library component is at Advise, next Inquire. A new flow is at Agree, next Advise. Scope trade-offs with product are at Consult, next Agree. Note: move one area one step after a run of good calls; crit stays open at every level.
Illustrative concept: How far each decision is handed over. A delegation board with seven levels: 1 Tell, 2 Sell, 3 Consult, 4 Agree, 5 Advise, 6 Inquire, 7 Delegate. Copy and spacing in the system is at Inquire, next Delegate. Choosing a library component is at Advise, next Inquire. A new flow is at Agree, next Advise. Scope trade-offs with product are at Consult, next Agree. Note: move one area one step after a run of good calls; crit stays open at every level.
Illustrative concept: How far each decision is handed over. A delegation board with seven levels: 1 Tell, 2 Sell, 3 Consult, 4 Agree, 5 Advise, 6 Inquire, 7 Delegate. Copy and spacing in the system is at Inquire, next Delegate. Choosing a library component is at Advise, next Inquire. A new flow is at Agree, next Advise. Scope trade-offs with product are at Consult, next Agree. Note: move one area one step after a run of good calls; crit stays open at every level.
Illustrative concept: How far each decision is handed over. A delegation board with seven levels: 1 Tell, 2 Sell, 3 Consult, 4 Agree, 5 Advise, 6 Inquire, 7 Delegate. Copy and spacing in the system is at Inquire, next Delegate. Choosing a library component is at Advise, next Inquire. A new flow is at Agree, next Advise. Scope trade-offs with product are at Consult, next Agree. Note: move one area one step after a run of good calls; crit stays open at every level.
Illustrative concept: How far each decision is handed over. A delegation board with seven levels: 1 Tell, 2 Sell, 3 Consult, 4 Agree, 5 Advise, 6 Inquire, 7 Delegate. Copy and spacing in the system is at Inquire, next Delegate. Choosing a library component is at Advise, next Inquire. A new flow is at Agree, next Advise. Scope trade-offs with product are at Consult, next Agree. Note: move one area one step after a run of good calls; crit stays open at every level.

Before your next review

  • Ask for the decision first, then the screens.
  • Ask what evidence supports it, and what would change it.
  • Ask what kind of feedback they want.
  • Say who decides this one, and at which level.
  • Pick one decision area to move one step toward them this month.
  • Keep crit open, so a handover never means working alone.

Before your next review

  • Ask for the decision first, then the screens.
  • Ask what evidence supports it, and what would change it.
  • Ask what kind of feedback they want.
  • Say who decides this one, and at which level.
  • Pick one decision area to move one step toward them this month.
  • Keep crit open, so a handover never means working alone.