The management practice of assigning tasks, decision-making authority, and ownership of outcomes to subordinates while retaining overall accountability for results.
Key Takeaways
Delegation is giving someone else both the work and the authority to get it done. That second part is what separates real delegation from simply dumping tasks on people. When a manager delegates a project, they're saying: "This is yours. Make the calls. Own the result. I'm here if you need me, but I'm not going to hover." It sounds straightforward, but most managers struggle with it. A 2023 Harvard Business Review study found that 53% of managers admit they don't delegate enough, primarily because they don't trust their teams to deliver at the quality level they expect. This creates a bottleneck. The manager becomes a single point of failure, working 60-hour weeks while their team sits idle waiting for approvals and decisions. Meanwhile, the team doesn't develop because they never get the chance to handle anything meaningful. Delegation isn't about reducing a manager's workload, though that's a welcome side effect. It's about developing people. Every delegated task is a learning opportunity for the employee and a signal that their manager trusts their judgment.
Delegation isn't binary. There's a spectrum from full manager control to full employee autonomy, and effective managers adjust the level based on the task and the person.
| Level | Description | When to Use It | Example |
|---|---|---|---|
| 1. Tell | Manager decides and informs | Crisis situations, non-negotiable compliance tasks | "Process payroll by Friday using the standard procedure." |
| 2. Sell | Manager decides but explains reasoning | When buy-in matters but the decision is made | "We're switching to biweekly pay cycles because of X. Here's why it's the right call." |
| 3. Consult | Manager asks for input, then decides | When the employee has relevant expertise | "How do you think we should handle the onboarding backlog? I'll make the final call." |
| 4. Agree | Manager and employee decide together | Moderate complexity, shared ownership needed | "Let's figure out the Q2 training calendar together." |
| 5. Advise | Employee decides, manager offers input | Experienced employees with proven judgment | "It's your call on the vendor selection. Here's what I'd consider." |
| 6. Inquire | Employee decides and informs manager | High-trust, routine decisions | "Handle the new hire orientation plan. Just let me know what you decided." |
| 7. Delegate | Employee decides and acts autonomously | Expert-level employees on familiar tasks | "You own the monthly engagement report end to end." |
Poor delegation causes more problems than no delegation at all. Following a structured approach prevents the common failures.
Not everything should be delegated. Tasks that are good candidates for delegation include recurring operational work, tasks that develop the employee's skills, decisions that the employee is closer to than the manager, and projects with clear success criteria. Tasks that shouldn't be delegated include confidential HR matters (terminations, salary decisions for the delegatee's peers), tasks that are core to the manager's role (like conducting performance reviews for their own team), and crisis decisions that require the manager's authority level.
Match the task to someone who either has the skill already or is ready to develop it. Consider current workload (don't overload your strongest performers), interest level (delegation works best when the employee wants the responsibility), and skill proximity (they should be about 70% ready, with the remaining 30% being the growth opportunity). Delegating a complex task to someone with no foundation in the area isn't development, it's setting them up to fail.
Tell them what success looks like, not how to achieve it. Specify the deadline, quality standards, budget constraints, and stakeholders. Then step back and let them determine the approach. If you dictate every step, you're not delegating. You're using the employee as an extra pair of hands while keeping all the thinking for yourself.
If you've asked someone to manage a vendor relationship, they need the authority to make decisions with that vendor without checking with you on every email. Delegating a task without the corresponding authority creates frustration on both sides. The employee feels micromanaged, and the vendor wonders who's actually in charge.
Don't disappear after delegating, and don't hover. Set specific milestones where you'll review progress. For a two-week project, that might be a brief check-in at the end of week one. For a six-month initiative, it might be a monthly review. Check-ins should focus on removing obstacles, not second-guessing decisions that have already been made.
Most delegation failures aren't about the employee. They're about the manager's approach.
This is the most common failure. The manager assigns a project but requires approval for every decision along the way. The employee becomes a messenger rather than an owner. They can't respond to stakeholders in real time, progress stalls, and both parties end up frustrated. If you can't grant the authority, you shouldn't delegate the task.
Some managers delegate on Monday, check in on Tuesday, take over on Wednesday, and wonder why their team lacks initiative by Thursday. When a manager takes a task back at the first sign of difficulty, the employee learns that struggling means the manager will rescue them. This kills development. Resist the urge to step in unless the situation truly requires it. Let people work through challenges.
If the only things you delegate are filing, data entry, and meeting scheduling, you aren't developing anyone. You're just offloading administrative work. Real delegation includes meaningful decisions, client-facing responsibilities, budget management, and strategic thinking. Employees who only receive low-value delegation don't grow, and they eventually leave for roles where they can.
Telling someone to "handle the Q3 budget" without explaining organizational priorities, past decisions, political sensitivities, and stakeholder expectations is a recipe for misalignment. Context doesn't mean dictating the approach. It means sharing the information the employee needs to make good decisions independently.
Delegation isn't just a management technique. It has measurable business outcomes.
Research from London Business School found that managers who delegate effectively recover an average of 8 hours per week. That's time redirected from tasks someone else could handle toward strategy, relationship building, and the high-impact work that only the manager can do. Managers who don't delegate become operational bottlenecks. Their teams can't move faster than the manager can review and approve.
Delegation is on-the-job development in its purest form. Employees who receive meaningful delegated work report higher engagement, develop new skills faster, and are better prepared for promotion. Gallup's 2023 data shows that employees who feel they're growing are 3.5 times more likely to be engaged at work. Delegation is the most direct way to create that growth feeling.
If a manager can't take vacation without the team falling apart, there's a delegation problem. Systematic delegation creates bench strength. When employees have been making decisions and managing projects for months, they're ready to step into bigger roles. Organizations with strong delegation cultures have deeper succession pipelines and faster internal promotion rates.
Several structured approaches help organizations formalize delegation practices beyond individual manager judgment.
The RACI (Responsible, Accountable, Consulted, Informed) matrix clarifies who does the work, who owns the outcome, who provides input, and who needs to be kept in the loop. It's the most widely used delegation tool in project management and HR operations. RACI prevents the confusion that happens when delegation is informal: two people thinking they're both responsible, or nobody realizing they were supposed to make a decision.
Developed by Hersey and Blanchard, this model matches the delegation level to the employee's readiness. New employees with low competence but high commitment get more direction. Experienced employees with high competence and high commitment get full delegation. The model prevents the common mistake of delegating at the same level to everyone regardless of their capability.
Borrowed from Management 3.0, delegation poker is a team exercise where managers and employees discuss specific decision types and agree on the appropriate delegation level for each. It removes ambiguity by creating explicit agreements about who decides what, documented and visible to the entire team.
Data supporting the business case for developing delegation as a core management competency.