Diagnose failures in delegation scenarios and apply the rule that you can delegate a task and authority but never the accountability for the outcome.
When delegation fails — and why the manager is still responsible
Diagnosing broken delegation
Delegation fails in predictable ways. The most common failure modes are: giving no context (the person does not understand why the task matters or how it connects to the broader goal); giving no authority (the person is expected to deliver results but cannot make the decisions needed to get there); micromanaging afterward (the manager takes back control through constant check-ins or overriding every decision, which signals distrust and defeats the purpose of delegation); and accountability dumping (the manager tries to make the team member fully responsible for the outcome, including in front of senior leadership, when this was never a fair transfer).
A critical principle runs underneath all of these: you can delegate a task and you can delegate authority, but you cannot delegate accountability for the outcome. If a delegated project fails, the manager owns that failure — not because the team member did nothing wrong, but because the manager chose to delegate, chose the person, set the conditions, and is ultimately responsible for the team's results. This does not mean protecting poor performers from consequences; it means the manager cannot point at a report and say 'not my problem.'
Diagnosing what went wrong in a delegation situation requires asking four questions: Was the goal clear? Did the person have the authority they needed? Did I give enough context and check in appropriately (not too much, not too little)? And did I set up conditions for success — or just hand over a task and disappear? Rewriting a bad hand-over into a good one is the best way to build this diagnostic muscle before it is needed in a real situation.
Lesson notes
Diagnosing broken delegation
Delegation fails in predictable ways. The most common failure modes are: giving no context (the person does not understand why the task matters or how it connects to the broader goal); giving no authority (the person is expected to deliver results but cannot make the decisions needed to get there); micromanaging afterward (the manager takes back control through constant check-ins or overriding every decision, which signals distrust and defeats the purpose of delegation); and accountability dumping (the manager tries to make the team member fully responsible for the outcome, including in front of senior leadership, when this was never a fair transfer).
A critical principle runs underneath all of these: you can delegate a task and you can delegate authority, but you cannot delegate accountability for the outcome. If a delegated project fails, the manager owns that failure — not because the team member did nothing wrong, but because the manager chose to delegate, chose the person, set the conditions, and is ultimately responsible for the team's results. This does not mean protecting poor performers from consequences; it means the manager cannot point at a report and say 'not my problem.'
Diagnosing what went wrong in a delegation situation requires asking four questions: Was the goal clear? Did the person have the authority they needed? Did I give enough context and check in appropriately (not too much, not too little)? And did I set up conditions for success — or just hand over a task and disappear? Rewriting a bad hand-over into a good one is the best way to build this diagnostic muscle before it is needed in a real situation.