Delegate judgment with clear escalation boundaries
What This Concept Is
Delegation transfers an outcome and a bounded set of decisions to another person. The delegator supplies purpose, constraints, access to context, feedback and escalation support. Writing the implementation in advance and asking someone to type it transfers tasks but offers little room to practice judgment.
Why It Matters Here
The original grow-another-engineer lab needs observable evidence. An agreeable retrospective alone cannot show that another person can reason independently. Conversely, independent judgment may produce a different sound design from the one the mentor expected.
Concrete Example
Delegate a safe local replay pilot. The engineer can choose the local test layout and propose a batching policy. They cannot expand data access, replay real customer records or change production behavior. Agree on synthetic fixtures, a duplicate-effect guardrail, a two-hour investigation checkpoint and escalation when event identity is ambiguous. At review, ask the engineer to explain two alternatives and the evidence that would change their recommendation.
If the mentor repeatedly supplies answers, record the intervention. At a second session, use an unseen failure such as a delayed compensation acknowledgement. Ask the learner to decide when to stop and whom to consult. The evidence is their reasoning and action, not whether they reproduce the mentor's preferred architecture.
Common Confusion / Misconception
Delegation is not abandonment. Asking for help at a known boundary can demonstrate good judgment. Sponsorship is also distinct: providing visibility or opportunity does not prove technical competence. A fictional dialogue or an AI role-play can rehearse the conversation but cannot establish that another engineer learned.
How To Use It
Agree on a short brief: outcome, beneficiary, non-goals, decision owner, allowed decisions, safeguards, dependencies, evidence and escalation. Ask the receiver to explain it in their own words. Schedule a review proportionate to uncertainty, not constant monitoring. Preserve disagreement and explain which decisions changed because of it. Keep personal feedback consensual and remove identifying details from the portfolio.
Check Yourself
What can the receiver decide without you? What condition requires stopping? Who resolves a conflict between teams? Did you change the outcome requirement after seeing a different solution?
Mini Drill or Application
Use a consenting peer for the original delegation lab and a fresh transfer discussion at least 48 hours later. Capture an anonymized before/after reasoning sample and one improvement to your brief. If no peer is available, finish the rehearsal but mark the interpersonal gate pending; do not fabricate participation.
Read This Only If Stuck
Fundamentals of Software Architecture — leadership, negotiation and effective teams. Revisit the existing mentorship and feedback lessons before collecting peer evidence. Use Staff Engineer selectively for role scope; no additional book purchase is required.