Delegation means giving another person responsibility for a defined result, along with the authority to decide how to reach it, and it works when the leader names the outcome, the limits and the check-in points and then stays out of the method. A leader who cannot delegate becomes the community’s single point of failure, because everything stops when that one person is ill, hurt or exhausted.
Part of Leadership Psychology in Crisis
Delegation is the transfer of a defined responsibility and decision authority to another person, resting on trust built through experience.
Why A Leader Must Let Go
A leader carries more problems than anyone else, and a group can be rebuilt only if more than one person can solve them. Delegation does three things at once: it spreads the load (see Decision Fatigue & Prevention), it uses the skills the group already has, and it trains the people who will lead later (see Succession & Shared Leadership).
Delegation also has a cost the first time. The task is done more slowly, perhaps worse, and perhaps differently from how you would have done it. A leader who judges delegation by the first attempt will conclude it does not work and take everything back. The test is the third or fourth time.
Trust Is The Fuel, And It Is Built In Steps
Nobody hands over the grain store to a stranger. Trust grows by a small task done well, a larger task done well, and so on. For the person receiving the task, trust also runs the other way: they need to know the leader will not undermine their decisions in front of others.
The usual ladder, as practical custom rather than a research finding, runs like this:
- Look into it and report. The person gathers facts; the leader decides.
- Recommend. The person proposes a decision; the leader accepts or changes it.
- Decide, then tell. The person decides within limits and informs the leader at once.
- Decide and report later. The person acts within their area and reports on a schedule.
Start someone on the step that suits what you know of them, and move up as the results justify.
Method: A First Delegation
Step 1: Choose a task that matters but forgives a mistake. A rotation schedule, a store inventory, a repair. Not the water supply on day one.
Step 2: State the outcome, the deadline and the limits. “Have the north fence mended by Friday. You may use up to the spare timber. Do not take anyone off the harvest.” See Accountability Without Micromanagement.
Step 3: Agree when you will check in. Not constantly. At a fixed time, such as the end of the second day.
Step 4: Back them in public. If someone disputes their decision, send the question back to them first. If the decision was wrong, correct it privately and with the person involved.
Step 5: Review afterward, together. What worked, what you would change. Credit publicly, advise privately.
What To Keep And What To Give
Some decisions should stay with the leader or council, such as scarce critical resources or contact with other communities. Others are best given away. The article What to Delegate vs Hold sorts them, and Building Capable Deputies covers building a second tier.
Common Mistakes
- Delegating the task but keeping the decision. The person becomes an errand runner and learns nothing.
- Delegating without saying what is off limits. They will find the limit by crossing it.
- Taking a task back at the first problem. It teaches the group that delegation is conditional on never failing.
- Delegating only the dull work. People can tell, and it does not build trust.
What’s Next
- Learn next: What to Delegate vs Hold — which decisions to give away
- Combine with: Community Roles — naming who is responsible for what