Workflow Automation
The most common delegation failure is not picking the wrong person. It is handing off a task without handing off the context, authority, and feedback loop that make the task completable. The result is a delegation that creeps back — the person you delegated to keeps checking in, you keep getting pulled back in, and eventually the task is yours again.
Delegate the outcome, not the method
When you delegate, describe what done looks like — not how to do it. Describing the method creates dependency: the person needs your method to succeed. Describing the outcome creates autonomy: the person can find their own method as long as the outcome is met. This requires you to know what the outcome actually is, which is harder than it sounds.
Transfer the authority explicitly
For a delegation to hold, the person receiving it needs to know they have the authority to make decisions within its scope. Vague delegations — "handle the vendor relationship" — create uncertainty about what decisions require escalation. Clear delegations — "you have authority to approve invoices under $5,000 without my sign-off" — create confidence to act.
Set a feedback mechanism, not a check-in schedule
Regular check-ins on delegated tasks create the same dependency you were trying to eliminate. Instead, define a feedback trigger: "Let me know if the project goes over budget, hits a blocker you cannot resolve, or misses a deadline." This way you hear about problems, not about progress.
Document what you delegated
A verbal delegation has a shelf life. The person you delegated to moves on, forgets the scope, or interprets it differently over time. Write down what was delegated, to whom, at what authority level, and when it was last reviewed. One paragraph. Date-stamped. This single practice eliminates most re-delegation conversations.