Most managers delegate tasks. Almost none do it well.
The manager who assigns a task and then checks in every three hours isn't delegating — they're creating a performance with two people. The manager who hands off work without context and expects results is setting up their employee to fail.
Effective delegation is a skill. It requires you to be precise about what you're handing off, clear about what success looks like, and disciplined enough to stay out of the way after the handoff. Most managers never learn this explicitly — they learn by failing at it until they develop patterns that kind of work.
This is the explicit version.
---
Why Delegation Fails (The Real Reasons)
Before building a delegation system, it helps to understand why most delegation attempts fail.
Unclear ownership. When an employee isn't certain whether they own a decision or just the execution, they'll ask for approval before every step — or make a decision they weren't authorized to make and cause a problem. Both outcomes put the task back on the manager.
No definition of done. "Handle the client situation" can mean ten different things. Without a shared definition of what completion looks like, you'll get what the employee thinks you wanted — which may or may not be what you needed.
Wrong authority level. Effective delegation requires matching the level of autonomy to the level of task complexity. Handing a new employee a high-stakes, high-complexity task and telling them to run with it is not delegation — it's exposure. Micromanaging a senior employee through a routine task wastes both of your time.
No check-in structure. Delegation without a check-in schedule creates anxiety on both sides. The manager wonders if it's being done right; the employee wonders if they're expected to ask questions or just produce results. Define the check-in before you walk away from the handoff.
---
The Delegation Framework
Step 1: Clarify the Task at Three Levels
Every task you delegate has three components. Make all three explicit before the handoff.
The output: What physical or digital deliverable are you expecting? Be specific. "A summary of the Q2 client issues" is vague. "A one-page write-up with the three most common complaint categories, frequency count for each, and a recommended priority order — due by end of Thursday" is a definition of done.
The constraints: What can't change? Budget limits, brand guidelines, timelines, approval requirements. These are the rails — the employee needs to know where the edges are before they start.
The authority level: How much can they decide without coming back to you? This is the piece most managers skip, and it's where the most delegation failures originate. The simplest framework is three levels:
- Level 1 (Recommend only): The employee gathers information and makes a recommendation. You decide.
- Level 2 (Act and report): The employee makes the decision and takes action. They tell you what they did and why.
- Level 3 (Full autonomy): The employee handles it. No report required unless they flag an exception.
Assign every delegated task to one of these levels before you hand it off.
Step 2: Match the Employee to the Task
Not every employee is ready for every task at every authority level. The error most managers make is assigning authority level based on seniority rather than task-specific competence.
An experienced employee who has never managed vendor relationships should start at Level 1 for vendor negotiations — regardless of their overall track record. A junior employee who has run a specific recurring process dozens of times can operate at Level 3 for that process.
The questions to ask before delegating: 1. Has this employee done this specific type of task before? 2. What's the consequence of a mistake, and how reversible is it? 3. Is this a task where I need visibility for downstream decisions, or can it operate independently?
High consequence + new employee = lower authority level, more check-ins. Low consequence + experienced employee = higher authority level, fewer check-ins.
Step 3: Brief the Handoff in Writing
The most common failure point in delegation isn't the work itself — it's the handoff conversation.
Verbal handoffs produce gaps. The manager remembers explaining something that the employee doesn't remember hearing. The employee fills the gap with their best guess, which may not match what the manager intended.
A written brief for any delegated task of significance should include: - What's being delegated (output definition) - The authority level (1, 2, or 3) - The constraints - The check-in schedule - What "done" looks like for review
This doesn't have to be long. For most tasks, five bullet points in Slack or your project management tool is sufficient. For high-stakes work, a short document is worth it.
The written brief creates a shared reference point. When the deliverable comes back and doesn't match expectations, the brief is the calibration tool — did the employee miss the brief, or was the brief unclear? Both are fixable. Guesswork is not.
Step 4: Set the Check-In Cadence and Honor It
Check-ins serve two functions: they give the employee a structured moment to surface problems, and they give you a mechanism to catch issues before they compound.
The check-in schedule should be set at the handoff and tied to task progress milestones — not calendar time. "Check in when you've done the first draft" is more useful than "check in every Tuesday."
For longer or more complex delegated work, a three-point check-in structure works: 1. Start check-in: The employee confirms they understand the task and has what they need. This surfaces resource or access gaps before they block progress. 2. Mid-point check-in: The employee shares where they are, what decisions they've made, and any problems they're tracking. 3. Pre-completion check-in: The employee confirms the deliverable is ready for review and surfaces any scope deviations.
If the employee misses a check-in without notice, that's a management conversation about professional norms — not a delegation failure.
---
What Stays With You
Delegation is not abdication. There are decisions that should stay with the manager regardless of the employee's competence level.
Decisions that affect other people's work. If the output of a delegated task will constrain or depend on other employees, the manager needs visibility before action is taken.
Commitments to external parties. Promises to clients, vendors, or partners typically require manager sign-off before they're made — even if the employee is doing the work.
Anything that changes the scope of the original assignment. If the task expands mid-stream, the employee should surface it rather than absorb the scope change silently.
Defining these "non-delegatable" categories explicitly at the team level prevents scope creep and boundary confusion.
---
The Delegate-to-Develop Distinction
There are two types of delegation. Most managers only practice one.
Workload delegation transfers work that exists so the manager can focus on higher-priority work. The goal is efficiency — get the right work done at the right level.
Developmental delegation transfers work that is intentionally at the edge of the employee's current capability. The goal is growth — build the employee's ability to operate at a higher level.
Developmental delegation requires more investment: more frequent check-ins, more explicit feedback, more tolerance for imperfection while the employee is learning. The return is a team that can do more over time without adding headcount.
Both types have a place. Most managers default entirely to workload delegation — and then wonder why their team isn't growing.
---
Further Reading
For the complete delegation system — including the full authority-level framework, delegation planning templates, and how to recover from a team culture where nobody owns anything — [The Delegation Standard](https://www.amazon.com/dp/B0H1JQXT47) covers the methodology in depth.
---
*Published by Tanta Holdings. For management consulting and operational systems work, visit [tantaholdings.com/consulting](https://tantaholdings.com/consulting).*