| name | delegation-levels |
| description | When you need to calibrate control vs autonomy - the 7-level framework for matching delegation depth to team readiness |
| tags | ["management","leadership","delegation","autonomy","development"] |
Delegation Levels (7 Levels)
Overview
A progressive framework for adjusting how much autonomy you grant when delegating tasks, from "I decide" to "You decide without reporting". Maps control levels to employee capability, criticality of decision, and developmental goals.
Core Principles
- Match Level to Readiness: High performers + low-risk tasks = high delegation
- Explicit Contracting: State the level upfront ("I need you to research options, I'll decide")
- Progressive Development: Move people up levels over time as capability grows
- Context-Dependent: Same person may operate at different levels for different tasks
- Transparency: Making the delegation level explicit prevents misalignment
The 7 Levels
Level 1: Tell - "I decide, you execute"
What it means: Manager makes decision, provides specific instructions
Communication: "Here's what to do, here's how to do it"
When to use:
- New employee learning the ropes
- Crisis situations requiring immediate action
- Legally/ethically sensitive decisions
- Employee explicitly requests detailed guidance
Example: "Update the pricing page to show $99/month instead of $79. Use the exact copy I've written here."
Level 2: Sell - "I decide, but I'll explain why"
What it means: Manager decides, but takes time to build buy-in through reasoning
Communication: "Here's the decision and the rationale behind it"
When to use:
- Unpopular but necessary decisions
- Employee has context to understand but not authority to decide
- Building decision-making capability for future
- Change management scenarios
Example: "We're switching to competitor X's API. Here's why: lower cost, better SLA, migration path is straightforward. Let me walk you through the analysis."
Level 3: Consult - "Give me input, I'll decide"
What it means: Manager seeks employee perspectives before making final call
Communication: "I want your recommendation, but I'll make the final decision"
When to use:
- Employee has relevant expertise or frontline perspective
- Decision has moderate risk/impact
- Developing employee's strategic thinking
- Building trust while maintaining oversight
Example: "Research the top 3 payment providers and present pros/cons. I'll choose which one we implement."
Level 4: Agree - "We decide together"
What it means: Collaborative decision-making with equal weight
Communication: "Let's work through this together until we both agree"
When to use:
- Decision affects both manager and employee significantly
- Complex problem requiring combined expertise
- High-stakes decisions needing shared ownership
- Team culture decisions
Example: "Let's whiteboard the architecture options together. We need to both be confident in whatever we choose."
Level 5: Advise - "You decide, but run it by me first"
What it means: Employee makes decision, manager provides feedback before execution
Communication: "Make your recommendation, I'll give you my thoughts, then you finalize"
When to use:
- High-capability employee on moderately important decisions
- Manager wants visibility without micromanaging
- Developing judgment in employee
- Decisions with reversible consequences
Example: "Draft the customer communication about the outage. Show me before you send, but it's your call on tone and content."
Level 6: Inform - "You decide, just tell me"
What it means: Employee has full authority, manager wants awareness after decision
Communication: "You make the call, just keep me in the loop"
When to use:
- Trusted employee in their area of expertise
- Low-to-moderate risk decisions
- Manager needs situational awareness but not control
- Empowering high performers
Example: "You own the sprint planning process. Just send me the final sprint goals so I can sync with other teams."
Level 7: Delegate Fully - "You decide, reporting optional"
What it means: Complete autonomy, employee may not even inform manager
Communication: "This is entirely yours. Update me if you think it's relevant."
When to use:
- Senior/expert employees in their domain
- Low-risk, high-frequency decisions
- Explicit ownership transfer
- Routine operational choices
Example: "Handle all customer support escalations using your judgment. I trust you to loop me in only if there's a pattern or major issue."
Execution Steps
1. Assess the Decision Context
- Task Criticality: What's the impact if this goes wrong? (High/Medium/Low)
- Employee Capability: How experienced are they with this type of decision?
- Reversibility: Can we easily undo this decision if needed?
- Time Pressure: Do we have time for collaboration or need speed?
- Development Goal: Should this stretch them or play to strengths?
2. Choose the Appropriate Level
Map your assessment to the framework:
- High criticality + Low capability = Level 1-2
- Medium criticality + Medium capability = Level 3-4
- Low criticality + High capability = Level 5-7
Development modifier: You can delegate one level higher than "safe" to stretch people
3. Make the Level Explicit
State it clearly upfront:
- "I need you to research this and give me 3 options - I'll make the final call" (Level 3)
- "This is yours to run with. Let me know what you decide" (Level 6)
4. Provide Context and Constraints
- Share relevant background information
- Define boundaries: budget limits, timeline, stakeholders to consult
- Clarify success criteria
- Identify risks to watch for
5. Monitor and Adjust
- If they exceed expectations: move up a level next time
- If they struggle: provide support, but don't immediately drop levels (undermines trust)
- Revisit levels quarterly as capabilities grow
- Different tasks may warrant different levels for the same person
6. Reflect and Calibrate
Periodically ask:
- "Am I delegating at the right level for each person?"
- "Where am I micromanaging (too low)?"
- "Where am I abdicating (too high)?"
- "What pattern do I see - do I default to one level?"
Anti-Patterns
The Hovering Delegator: Says "Level 7" but constantly checks in (really Level 5-6)
The False Collaborator: Says "Level 4" but steamrolls employee input (really Level 2)
The Premature Promoter: Jumps from Level 2 to Level 7 without building capability
The Permanent Micromanager: Keeps high performers at Level 1-2 indefinitely
The Abdicator: Uses Level 7 for everything to avoid managing (not empowerment, neglect)
The Retroactive Reverser: Grants Level 6, then overrides decision after execution (destroys trust)
Quality Indicators
High Signal:
- Employees know which level they're operating at before starting work
- Level matches task importance and employee capability
- Over time, most employees progress to higher levels
- Clear pattern of increasing autonomy as tenure/skill grows
- Disagreements about "what level was this?" are rare
Low Signal:
- Frequent misunderstandings about decision authority
- Manager frequently overrides decisions they "delegated"
- Employees say "I thought I could decide that" or "I didn't know you wanted input"
- All employees treated at same level regardless of capability
- No visible progression in delegation over time
Situational Adjustments
New Employee (First 90 Days):
- Start mostly at Level 1-2
- Explicitly teach the framework
- Progressively move to 3-4 for their core expertise areas
- By day 90, high performers should be at Level 5-6 for routine tasks
Crisis/High-Pressure Situations:
- Temporarily drop to Level 1-2 for critical path items
- Explain the shift: "Normally this is yours, but given the outage..."
- Return to normal levels once crisis passes
- Discuss lessons learned: "Could we have maintained Level 5 if we had X?"
Performance Issues:
- Don't immediately drop levels (signals distrust)
- Instead, add checkpoints: "Let's do Level 5 but with daily syncs"
- Address root cause: skill gap vs. motivation vs. unclear expectations
- Return to appropriate level once issue is resolved
High Performer Retention:
- Audit their levels - are they at 6-7 for most work?
- If not, you're likely micromanaging and risking turnover
- Top talent expects to operate at Level 6-7 for their core work
- Create new Level 3-4 challenges (new domains) to keep growth
Real-World Examples
Software Engineering Manager:
- Code review standards: Level 7 (senior devs decide when code is ready)
- Architecture decisions: Level 4 (collaborative design)
- Production deployments: Level 5 (engineer decides when, manager reviews plan)
- Incident response: Level 2 during crisis, Level 6 for postmortems
Product Manager:
- Feature prioritization: Level 3 (team proposes, PM decides)
- Wireframe iterations: Level 6 (designer decides, PM informed)
- Pricing changes: Level 1 (exec decision, PM executes)
- A/B test design: Level 5 (PM designs, reviews with analytics team)
Related Frameworks
- Situational Leadership (Hersey-Blanchard): Similar readiness-based model
- RACI Matrix: Defines Responsible/Accountable/Consulted/Informed (orthogonal to delegation levels)
- Manager's Path (Camille Fournier): Four-quadrant delegation model (simple/complex × frequent/infrequent)
- Extreme Ownership: Balances decentralized command with centralized intent
Scoring (44/50)
- Practitioner Weight (9/10): Widely used, but often implicit rather than formalized
- Clarity (9/10): Seven levels provide clear gradations
- Proven ROI (9/10): Strong correlation with employee autonomy and retention
- Novelty (7/10): Codifies common management practice into explicit framework
- Applicability (10/10): Universal across industries, roles, and contexts
Sources
- Tannenbaum-Schmidt Continuum (1958): Original leadership behavior spectrum
- Situational Leadership (Hersey-Blanchard): Readiness-based delegation model
- Manager Tools Podcast: Practical delegation guidance
- The Manager's Path (Camille Fournier): Four-category delegation framework
- Turn the Ship Around (David Marquet): Intent-based leadership and control transfer
