Delegation That Actually Works — Beyond 'You've Got This'

A manager told me his report 'kept dropping the ball'. We looked at it: 11 tasks delegated in 2 weeks, no documented outcomes, no decision rights, no check-in cadence. He wasn't dropping balls — they had never really been thrown. The throw is the skill.

Why it matters

Delegation is the single highest-leverage skill a manager has — and the most consistently botched. Done right, it multiplies your output and grows your team. Done wrong, it creates the manager's busiest week ever and a team that's quietly losing confidence. The most common failure isn't capability; it's an incomplete handoff.

Two stable patterns: managers who never delegate enough (and become the bottleneck) and managers who delegate too much too soon (and look hands-off but leave the team un-supported). Both fail the same test — they didn't specify which level of authority they were handing over, in writing, with a check-in cadence.

5 levels of authority

7-point handoff

1. What's the outcome? (Not the task.)
2. What's the deadline?
3. What level of authority (L1-L5)?
4. What's the budget — money, time, scope?
5. What are the non-negotiables?
6. Who else needs to be informed?
7. When and how do we check in?

Bad vs good delegation

Example

When Andy Grove wrote 'High Output Management', he documented Intel managers explicitly negotiating level of authority on each delegated task. The friction up front saved exponentially more correction later. The 5-minute conversation prevents the 5-hour cleanup. The same dynamic shows up in every modern engineering org that runs RFCs — a written proposal is a forcing function for the handoff conversation that should have happened anyway.

Apply on Monday

• Pick your last 3 delegated tasks. Score whether they got the 7-point handoff.
• For each report, document their default level of authority by area.
• Replace 'can you handle this?' with the 7-point template, in writing.
• Move one task up a level this quarter — and stop micromanaging it.
• When something goes wrong, ask: was this a handoff problem or a capability problem?

Common mistakes

• Delegating tasks, not outcomes.
• Same level of authority for every task and every person.
• Verbal handoffs that no one can audit later.
• Pulling work back the moment it's uncomfortable.
• Skipping the check-in cadence because 'I trust them' — then being surprised at the result.
• Not naming non-negotiables, then enforcing them retroactively.

Reflection prompts

1. What did I delegate this week with vague authority?
2. Which report should be operating at a higher level than I'm allowing?
3. Where am I doing work that should be 2 levels below me?
4. Which 'capability problem' on my team is actually a handoff problem?

Takeaways

• Delegation = authority transfer, not task transfer.
• Write the handoff. Verbal decays in a week.
• Most 'capability gaps' are handoff gaps.
• Move one task up a level per quarter, per report.