Delegation

Delegation

Delegation is how a leader scales impact and grows people, it is the job, not a distraction from it. The two failure modes are opposite and equally damaging: micromanaging (you delegate the task but not the authority, and stay the bottleneck) and abdicating (you toss it over the wall with no context and are surprised when it goes wrong). The craft is landing in between, and adjusting per person and per task.

Delegate outcomes, not just tasks

Hand over the goal and the "why," not a list of steps. "Reduce checkout latency to under 500ms because we're losing conversions" gives the person room to find a better solution than you'd have specified, and it's how they learn to think, not just execute. Specify the what and the constraints; let them own the how.

Match the level of oversight to the person and task

Calibrate on two axes: the person's competence at this kind of work and the task's risk/reversibility. High-skill person + reversible task → hand it off with a light touch. New-to-this person or one-way-door task → more context, checkpoints, and pairing early. Delegation is not one setting; give more support where the stakes or the stretch are higher, and pull back as they demonstrate mastery.

Set it up to succeed

When you hand something off, be explicit about:

• The outcome and how success is measured.
• The constraints: deadline, budget, non-negotiables, what not to touch.
• The decision rights: what they can decide alone vs. must consult on (see the decision-making skill).
• The checkpoints: when and how you'll sync, so oversight is scheduled, not surprise inspection.
• The context: background, stakeholders, and where to get unblocked.

Then get out of the way. Agree on outcomes and checkpoints, then let them work.

Let them do it their way (and let them struggle a little)

If you require it be done exactly your way, you haven't delegated (you've dictated. Accept a "good enough, done differently" result; correcting style you'd have done otherwise teaches people to stop thinking. Productive struggle is where growth happens) resist grabbing the keyboard the moment it's slower than you'd be. Step in for true blockers and high-stakes risk, not discomfort.

Delegate to grow, not just to offload

Give people work slightly beyond their current level (a stretch), with support sized to the stretch. Delegate the interesting and visible work too, not only the drudgery, hoarding the good work caps your team and signals distrust. Own the outcome publicly: you remain accountable, they get the credit for the win, and failures are shared learning, not blame.

Anti-patterns

• Micromanaging: delegating the task but not the authority; inspecting every step.
• Abdicating: no context, no checkpoints, then blaming the person for the result.
• Only delegating grunt work while hoarding the interesting, career-making projects.
• Requiring it be done exactly your way ("delegating" the how).
• Snatching the work back the moment it's slower or different than you'd do it.
• No agreed definition of done, so "finished" is a surprise to someone.
• Taking the credit and assigning the blame.