Delegation

“The output of a manager is the output of the organizational units under his or her supervision.” — Andrew S. Grove, High Output Management

Delegation is how you increase that output. But most delegation fails quietly. Tasks are handed off without real authority. Deadlines are set without context. Check‑ins are either suffocating or absent. The manager keeps catching “monkeys” that jump back on their shoulders, and the work that should have grown a teammate instead grows the manager’s inbox and to do list. Clear delegation fixes this by transferring outcomes, decision rights, and support – not just a to‑do.

The goal is not theory; it is a rhythm you can keep this quarter. You will see how to frame a delegation conversation, which traps to avoid, and a set of repeatable scripts and artifacts that make autonomy safe and performance reliable.

Principle: Delegation transfers outcomes, authority, and support

The core principle is simple: when you delegate, you transfer ownership of an outcome, not just a list of activities. You also transfer the authority to make the decisions required to reach that outcome, and you commit to support that makes success likely. Clear delegation defines the end state, the decision boundaries, the resources available, and the review rhythm.

Outcomes over activities. Activity can look busy while producing little value. Outcomes describe what success changes in the world: behavior, reliability, margin, or time to value. When you delegate an outcome, you give the owner room to choose the path, which taps their expertise and increases motivation (Deci & Ryan).

Decision rights. Authority is the ability to choose among options without waiting. Many handoffs fail because authority remains implicit or too narrow. A useful tool is a 5‑level decision ladder: (1) Tell me and I decide; (2) Propose and we decide together; (3) Decide, then inform me; (4) Decide within bounds; (5) You set bounds and decide. You can use different levels for different risks. The key is to make the level explicit and to adjust it as task‑relevant maturity rises (Grove).

Support. Delegation is not abdication. You remain responsible for the system. Support means access to context, people, budget, and feedback loops. Support also means protection – removing blockers and shielding the owner from scope creep and drive‑by requests that dilute focus.

Clarity before speed. It is tempting to throw work over the fence when you are busy. Resist that. Take ten minutes to write a one‑page brief. The time you spend clarifying the end state, authority, and rhythm will come back many times over in fewer escalations and faster progress.

Public clarity creates shared memory. When the brief is written and visible, newcomers understand decisions without a meeting, and dependencies are resolved with less friction. Written briefs also reduce politics because expectations are clear to everyone who matters.

Pitfall: The seven traps that break delegation

Tasking without context: You hand someone a task list but never explain why it matters or how it will be judged. They execute the list and miss the point.
1. Fix: lead with context—stakeholder needs, strategy, constraints, and success criteria.
Fuzzy decision rights: The owner must ask permission for every choice. Speed dies. Morale follows.
1. Fix: choose a level on the decision ladder and write it down.
Too many constraints, too little runway: You specify tools, steps, and more. There is no room for expertise.
1. Fix: constrain safety, legal, and brand; leave the “how” to the owner.
Dump‑and‑run (abdication): You hand off work with no support or check‑ins. The owner spins quietly and returns late with bad news.
1. Fix: agree on a review rhythm and early signals.
Micromanagement theater: You over‑specify and re‑do work, signaling you do not trust the owner. Initiative dies.
1. Fix: inspect outcomes and leading indicators, not keystrokes.
Role/skill mismatch: The task requires skills the owner does not yet have, but the plan assumes mastery.
1. Fix: fit the delegation to task‑relevant maturity; pair with practice and coaching.
The monkey returns: Problems bounce back to the manager (Oncken & Wass). The owner brings you issues but leaves without next steps.
1. Fix: when a “monkey” arrives, send it back with an owner, options, and a decision deadline.

Practice: A repeatable system for clear delegation

Turn the principle into a system you can keep. Use the CLEAR brief, level the decision rights, set a review rhythm, and use scripts to keep ownership in the right place.

CLEAR Brief – Context, Level of decision, End state/Evidence, Authority & support, Rhythm.

Opening with context reduces rework because people can make trade‑offs aligned to purpose. The level clarifies who decides and when to involve you. Definition of Done makes quality explicit. Authority and support prevent resource starvation. Rhythm keeps learning and course‑correcting cheap.

Level of Decision – Pick one per delegation. 1) Tell me and I decide. 2) Propose and we decide together. 3) Decide, then inform me. 4) Decide within bounds. 5) You set bounds and decide. Start where risk is manageable, then move up the ladder as task‑relevant maturity grows.

End State – “I want to delegate the outcome of X. Here is the context and why it matters now. Success looks like Y by date Z. You are at level 3 on the decision ladder -decide, then inform me – except for W, which is level 2. You have access to A and B, and a budget cap of $. We will review Wednesdays at 2pm for 20 minutes. What do you need from me to start?”

Authority & Support – Provide information about the level of authority the person will have. What access and authority over resources are they empowered to use? What level of support are you providing to the individual?

Rhythm – How often do you want to follow-up on the task and to what level of knowledge do you want to be briefed? Use a short template: status vs measures, what changed, decisions made, top risks, help needed, next milestone. Keep it to 15–20 minutes. Praise progress with specifics. When off‑track, coach with curiosity first, then adjust scope, time, or support.

Written one‑pager – Outcome and measures; decision level and exceptions; constraints and non‑goals; authority and resources; rhythm; risks, dependencies, first three milestones; Definition of Done checklist.

Impact and sustainability

With clear delegation, calendars match strategy, decisions speed up, and first‑attempt quality improves. Surprises shrink because reality shows up earlier in the rhythm. Sustain it by keeping briefs short, ladders explicit, and reviews on the calendar – even when you are busy. Consistency is the culture.

Summary

Delegation is not a handoff of tasks. It is a transfer of outcomes, authority, and support. Avoid predictable traps with written context, explicit decision rights, and a tight review rhythm. Use CLEAR and a decision ladder to make autonomy safe. Keep ownership with the owner through questions and coaching. After a quarter, expect higher output, faster decisions, and more time for the work only you can do.