Leadership
Delegation and accountability: clarify who decides
Delegate with a clear outcome, decision authority and review points, so accountability helps the work instead of creating another approval queue.
You delegate a project, then approve every detail. The colleague has responsibility for delivery, but each decision still returns to you. When the date slips, it is unclear whether the delay belongs to the task owner or the approval queue.
Useful delegation transfers a defined outcome with enough authority and support to pursue it. Accountability makes the agreement reviewable: what was expected, what each party could control and what happened.
The aim is not to remove your involvement. It is to make your involvement purposeful. This guide gives you a delegation brief and a way to distinguish a question, an exception and a decision that the person already owns.
Begin with an outcome someone can recognise
“Take care of the campaign” leaves too much to interpretation. Define what should be ready, who will use it and what makes it acceptable.
For example, a campaign brief might need an agreed audience, approved claims, required assets and a usable handover to production. That description tells the owner what the work must make possible.
Explain the purpose, not only the deliverable. A person can make a better choice about format when they understand the decision it serves. Leave reasonable freedom where the result does not depend on your preferred method.
Hackman and Oldham’s work-design research is a useful reference for examining the task itself. The practical brief below is an original planning tool, not a research assessment or a promise about performance.
Transfer decisions, not just activity
List the choices that the owner needs to make. Distinguish three routes: decide within an agreed boundary, propose for a required approval, or pause and escalate when a defined condition appears.
The boundaries should be specific. “Check with me if it matters” does not help the person recognise an exception. “A change to the approved audience requires the commercial owner’s decision” does.
Explain what can proceed without you. If the person must consult you on every routine choice, call the arrangement assisted execution rather than pretending it is full delegation.
Also name the controls you do not own. Delegation from a manager does not cancel a security review, a data permission requirement or another function’s approval. The person needs a route to those owners.
Match responsibility with resources and capacity
An owner cannot reliably deliver a task without access, information and available time. Identify these conditions before asking them to commit.
Discuss competing work. If the delegated project has priority, state what can wait and who has approved that trade-off. Do not make the person negotiate every conflict privately after the handover.
Identify dependencies outside their control. A supplier input, a data extract or a specialist review needs an owner and an expected timing. The task owner can coordinate the dependency, but cannot be made accountable for authority they do not possess.
Use leading without authority when the work crosses functions. A realistic commitment includes what each partner has accepted, not merely what the project lead hopes they will provide.
Make support a condition of the agreement
A person may need an example, a first-draft review or access to specialist advice. Discuss that need without equating it with unwillingness to take responsibility.
Zhang and Bartol’s research on empowering leadership examined empowerment within a particular organisational context. It is not proof that increasing autonomy automatically produces creativity or better delivery in every team.
The practical point is to specify what support helps this task. Agree when it is available and what the review will consider. Keep the owner responsible for preparing the work and identifying questions.
The situational leadership guide explains how to adjust assistance to an unfamiliar part of the task. Review the support arrangement as capability or risk changes.
Choose review points that correspond to decisions
A review is useful when it can change the work before a costly commitment. Ask what decision each checkpoint should inform.
For a brief, a review of claims before production may be valuable. Reviewing the colour of every draft slide may not be, unless it belongs to an actual requirement.
Agree what the owner brings: the current result, open questions, evidence and recommendation. This keeps the checkpoint focused on judgement instead of a complete narration of activity.
Avoid adding reviews casually after the task begins. If a new risk warrants one, explain it. Otherwise the person may discover that the promised authority was temporary and depends on your comfort.
A hypothetical delegation of a campaign brief
Imagine a marketing manager assigning a campaign brief to a colleague. This is a hypothetical example. The previous arrangement required approval of every wording change, although the manager mainly cared about audience and claims.
They define the outcome: a brief production can use without reconstructing the strategy. The colleague can choose structure and draft language within approved claims. Changing the audience requires a commercial decision. Introducing a new claim requires evidence and the relevant approval.
They schedule a review before production commits resources. The colleague brings unresolved decisions and a recommendation. The manager does not rewrite acceptable wording simply because another phrase sounds better to them.
At the review after handover, they examine whether production understood the brief, which decisions returned unnecessarily and whether the owner had enough support.
The example has no asserted outcome. It illustrates how to delegate decisions that fit the task while retaining the approvals that genuinely belong elsewhere.
Write a delegation brief
Use this with the person who will own the work. A short conversation about each field is more valuable than a completed form nobody understands.
Swipe or use the arrow keys to see every column.
| Field | Agreement to record |
|---|---|
| Outcome | What will be ready and which need it serves |
| Acceptance criteria | How the result will be judged |
| Decisions transferred | Choices the owner can make independently |
| Decisions retained | Approvals required from you or another role |
| Resources | Access, information, time and permitted budget where relevant |
| Dependencies | Inputs with named owners and accepted commitments |
| Support | Examples, specialist access and review assistance |
| Escalation | Conditions requiring a pause or a decision elsewhere |
| Review | Decision points and evidence the owner brings |
Ask the person to explain their first action and decision boundary. If their account differs from yours, resolve the gap now. A shared document can still hide two different interpretations.
Keep a question from becoming a return of the task
When the colleague asks what to do, identify the question. Do they lack information, need a decision outside their authority or want to compare options inside it?
If the choice is theirs, ask for the options and recommendation. Provide missing context and let them decide. This supports judgement without manufacturing a test of independence.
If the choice is yours, make it and record its effect. Do not send the person back to find an answer they cannot authorise.
If the task itself has changed, revise the brief. New scope should not be described as a failure to deliver the old agreement. The leadership guide connects this practice to the wider operating arrangement.
Review accountability with a fair account of control
At the end, compare the agreement with what happened. Was the outcome clear? Which choices did the person make? Which inputs arrived? Were risks communicated through the agreed route?
Accountability should include your commitments too. If you promised a review and did not provide it, record the consequence. The owner’s delivery date may have depended on that support.
Distinguish a changed condition, a skill gap and a missed expectation. These can require replanning, training or a direct performance conversation. Use difficult feedback to describe the episode and agree the next action.
Avoid a broad judgement about character from one delivery. Also avoid using context to make every failure unreviewable. A precise account helps you decide what needs to change.
Recognise the limits of delegation
Some decisions require authority or qualifications that the colleague does not have. Some tasks require close supervision because the consequences of an error are substantial. Those conditions should be named, not disguised.
Delegation also cannot solve a resource shortage by moving the problem down the hierarchy. An owner may coordinate limited capacity, but cannot create it through commitment.
If you cannot agree a viable task, narrow it, change the resources or change the date through the appropriate owner. Do not let a vague assignment become an individual test of endurance.
The organisational psychology guide examines task and system conditions alongside individual capability. It helps keep responsibility proportionate to the environment.
Close the assignment and update the boundary
At completion, say which responsibilities end and which remain. A colleague who delivered a campaign brief does not automatically own every later change or support request. Name the next owner and pass on the unresolved questions that affect their work.
Also identify decisions that could be transferred in the next comparable assignment. If a recurring approval added no useful information, clarify whether explicit criteria can replace it. If an exception required specialist judgement, retain that route. This closing step turns a single delegation into reusable knowledge without assuming that authority carries over to every new task.
Start with one approval you can transfer
Choose a recurring decision you currently approve. Ask whether it genuinely needs your authority or whether the criteria could allow the task owner to decide.
Write the boundary, give the necessary context and agree the exception route. Review the next complete work cycle, including new risks or rework. Fewer messages alone do not establish that the delegation worked.
The consumer psychology guide applies the same discipline to observed behaviour: an outcome and its explanation are different kinds of evidence.
If delegation in a digital programme keeps returning to your desk, tell me which approval creates the queue. We can define an outcome, a workable boundary and a review point.
Apply this to your project
Tell me the decision you are facing, the constraints and what you have already tried.
Keep exploring
Situational leadership: choose the right support
Use situational leadership carefully: assess the specific task, agree useful support and review it without turning people into fixed categories.
Decision-making under uncertainty: expose assumptions
Make a work decision with incomplete evidence. Separate facts from assumptions, compare options and define a review trigger with a practical record.
Difficult feedback: prepare a useful conversation
Prepare difficult feedback with observable behaviour, fair questions and a clear next agreement. Use a practical worksheet without labelling the person.