How to Delegate

Bad delegation is worse than no delegation. It wastes the other person’s time, produces garbage output, and convinces you that delegation doesn’t work. Then you go back to doing everything yourself, and the ceiling stays right where it was.

Good delegation works. People produce quality work. You get time back. Output multiplies. The ceiling lifts.

The difference isn’t luck. It’s design.

The Four Elements

Every effective delegation has these four components. Miss any one and the whole thing degrades.

1. Clear Outcomes

The person needs to know what success looks like. Not vague direction. Specific, verifiable outcomes.

Bad: “Handle the customer emails.” Good: “Respond to all customer emails within four hours during business hours. Use our brand voice guide. Answer questions directly. Escalate anything involving refunds over fifty dollars or complaints about product defects to me. Log all responses in the tracking sheet.”

The test: Could someone who’s never worked with you read your delegation and know if they’ve done it right? If not, it’s not clear enough.

2. Appropriate Authority

People can’t produce results if they don’t have permission to make decisions. But unlimited authority without judgment is dangerous.

Define the decision space:

• What can they decide on their own?
• What requires checking with you first?
• What budget authority do they have?
• What changes can they make to the process?

The goal is maximum autonomy within clear boundaries. Tight boundaries at first, expanding as trust builds.

3. Resources Needed

Don’t tell someone to build a house and hand them a spoon. Identify what they need to succeed:

• Access to tools, systems, and accounts
• Information and context about the work
• Budget if money needs to be spent
• Time to do the work properly
• Contact info for people they might need to coordinate with

If you forget resources, they’ll either ask (best case), make do with inadequate tools (common case), or fail silently (worst case).

4. Feedback Loops

How will both of you know it’s working? How will problems surface before they become catastrophes?

Build in:

• Check-in points. When will you review progress? Daily at first, then weekly, then as-needed.
• Quality indicators. What metrics or signals show the work is on track?
• Escalation paths. When something’s wrong, how does it get flagged?
• Course correction. How do adjustments get made?

Feedback isn’t micromanagement. It’s infrastructure. Micromanagement is checking in constantly because you don’t trust the person. Feedback loops are structured systems that keep work on track regardless of trust level.

What Bad Delegation Looks Like

Every bad delegation violates one or more of the four elements:

• “Just handle it.” (No clear outcome, no authority defined, no resources, no feedback)
• “Do it exactly like I would.” (Impossible outcome, no authority, no room to work)
• “Ask me about everything.” (No authority at all — you’re still doing the work through them)
• “Let me know when it’s done.” (No feedback loops — problems fester until it’s too late)

If you’ve delegated badly before and gotten burned, check which elements were missing. The failure wasn’t delegation itself. It was incomplete delegation.

The Delegation Document

For anything significant, write it down. A delegation document forces clarity that verbal handoffs miss. It doesn’t need to be long. One page is usually enough. But it needs all four elements.

Think of it as a brief. You’re briefing someone on a mission. They need to know the objective, their authority, their resources, and how to report back.

Today’s Practice

Take one item from your delegation priority list (Lesson 13) and design the delegation properly.

1. Outcome: What does success look like? Be specific enough that anyone could verify it.
2. Authority: What decisions can they make? What needs your approval?
3. Resources: What do they need to succeed? List everything.
4. Feedback: How will you check in? What triggers escalation?
5. Write it up as if you’re handing it to someone starting tomorrow. If reading it cold, would they know what to do?

This exercise isn’t theoretical. If you’ve been doing the previous lessons, you have a real delegation to design. Design it properly. Then execute it.