Why Delegation Emails Backfire
You need to hand off a task. You write an email that says 'Can you take care of this?' and hit send. What you meant: 'I trust you with this important work.' What they read: 'I don't want to do this so now it's your problem.'
Bad delegation emails fail in one of two ways. Either they're so vague that the person doesn't know what success looks like, or they're so detailed that the person feels micromanaged before they've even started. The sweet spot is giving enough context for autonomy while being clear about what done looks like.
The templates below hit that balance. They communicate trust, provide clarity, and give the person room to own the work — not just execute it.
The 'Context + Outcome' Template
Subject: [Task name] — would like your ownership on this
Hi [Name], I'd like you to take the lead on [specific task]. Here's the context: [2-3 sentences about why this matters and what's happened so far]. The outcome we need: [specific deliverable or result, with deadline]. You have full ownership of how you approach this. If you need [specific resources/access/authority], let me know and I'll get those set up. Any questions before you dive in? [Your name]
Why this works: 'Take the lead' is different from 'handle this.' It signals ownership, not dumping. The context explains WHY, the outcome explains WHAT, and 'full ownership of how' explains the level of autonomy. The person knows exactly what success looks like without being told how to get there.
The 'Stretch Assignment' Template
Subject: Growth opportunity — [task description]
Hi [Name], I have a project that I think would be a great stretch for you: [task description]. I'm asking you specifically because [genuine reason related to their skills or development]. Here's what I know so far: [context]. The goal is [specific outcome] by [deadline]. I'm available for questions and check-ins, but I want this to be your project. How does this sound? [Your name]
Use this when you're delegating something that's slightly above someone's current level. The 'I'm asking you specifically because' line transforms the task from an assignment into recognition. People work harder on projects they feel chosen for.
The 'Redistribution' Template
When you're delegating because your plate is full and you need to be transparent about it:
Hi [Name], I'm redistributing some of my current priorities to make sure everything gets the attention it deserves. I'd like to move [specific task] to you because [genuine reason — their expertise, bandwidth, development]. Here's where things stand: [current status]. Key deadline: [date]. I'll do a proper handoff [time/meeting] so you have everything you need. Thanks for taking this on. [Your name]
This template works because it's honest without being helpless. 'Redistributing priorities' is different from 'I can't handle my workload.' And offering a proper handoff shows respect for the work and the person receiving it.
Delegation Anti-Patterns
Never delegate via forwarded email with just 'Can you handle this?' written above it. It signals that you spent zero seconds thinking about who should do this or why.
Never delegate with invisible deadlines. If you know the deadline, share it. If there isn't one, say that explicitly. Nothing erodes trust faster than a Monday morning 'actually this was due Friday.'
Never delegate and disappear. The email should include when and how you'll be available for questions. Delegation without support isn't delegation — it's abandonment.
Top comments (0)