What is Delegation?
Delegation is the assignment of authority and responsibility to lower-level employees to make decisions and complete tasks. The components: (1) Authority — the right to act and decide. (2) Responsibility — the obligation to perform. (3) Accountability — answerability for results. Effective delegation specifies all three; vague delegation creates ambiguity and failure. The leader retains accountability even when authority and responsibility are delegated — "you can delegate authority but not accountability." Reasons leaders fail to delegate: trust issues, perfectionism, fear of being unnecessary, time pressure ("faster to do it myself"). The cost of under-delegation: leader bottleneck, team disengagement, no succession pipeline. The cost of over-delegation: misalignment, quality issues, leader insufficiently informed.
How Delegation actually works
The framework breaks down into the following moving parts. Knowing what each piece is — and what it is not — is what separates a B-grade answer from an A-grade answer in a written assignment.
- Specify authority, responsibility, AND accountability
- Match delegation to employee capability (situational)
- Delegate the work, not the result
- Coach but don't take back
- Leader retains accountability even after delegation
A worked example: Andrew Grove at Intel
Andrew Grove's "High Output Management" — the foundational text for many tech-company management practices — emphasizes delegation as a force multiplier. Grove's rule: a manager's output is the output of their team and influence area. Without delegation, output is capped at one person. With effective delegation, output scales with team size. Intel's mid-1990s growth from a microprocessor company to a $40B+ industry leader required delegating major decisions to division-level executives — too much for any single CEO. The discipline of delegation is one reason Intel could scale where many founder-led firms stalled.
Don't lose marks for these
- Specifying responsibility without authority (sets up failure)
- Taking back delegated tasks at first sign of trouble
- Failing to delegate because "faster to do it myself"
How to use this on the exam
Score-maximizing moves
- Distinguish authority, responsibility, accountability
- Cite leader retains accountability
- Recognize delegation as scaling tool
When to use Delegation (and when not to)
Use Delegation when your assignment asks you to analyze, structure, or recommend — and when you have at least two data points to populate every cell of the framework. Skip it when the question is asking for a numerical answer or a single recommendation, since Delegation is a structuring tool, not a calculator.