Principle
Give decision rights, not just tasks
Responsibility without authority creates queues and learned dependence.
When it fits
- When someone is accountable for delivery but must ask permission for every small choice.
When to avoid it
- Autonomy must be bounded by competence, risk, compliance and recoverability. High-consequence decisions may need explicit approval gates.
Why it matters
For delegated work, name which decisions the person may make independently, which require consultation and which require approval. Align authority with the expected outcome.
An example
The workstream lead may sequence fixes and approve low-risk mapping changes but needs architecture approval for interface contracts.
Check your result
Routine decisions no longer wait for the delegator unless a defined boundary is crossed.
Keep this limit in mind
- Autonomy must be bounded by competence, risk, compliance and recoverability. High-consequence decisions may need explicit approval gates.
Connected ideas
Useful withMatch autonomy to capability and risk
Evidence and sources
Supports
A meta-analysis based on 105 samples found empowering leadership positively related to performance, citizenship behavior and creativity at individual and team levels, while also identifying mediators and boundary conditions.
The result does not support maximal delegation in high-risk work or when authority, competence and feedback are missing.