🧭Leading Teams and Assigning Roles

Leadership and Management — The Difference That Matters

Leadership looks toward people, management toward tasks. Conflate them and you lose both.

The difference between leadership and management is not in the title or the authority, but in the direction the practitioner looks. A manager looks toward tasks: were they done, on time, to the required standard? A leader looks toward people: are they capable of what is being asked? Are they energised or exhausted? Do they have what they need to deliver what they have been given? A team that is only managed delivers what is asked and stops. A team that is led innovates when circumstances change and carries each other when time is short. In a volunteer context this distinction is sharper than in any other, because what holds volunteers together is not a contract but a voluntary commitment — and that commitment is built or destroyed by how leadership is practised day by day.

Assigning Roles — Who Does What and Why

The most common mistake of new leaders is giving tasks to people they like rather than people who are good at them.

When roles are distributed by relationship rather than capacity and availability, two paired problems repeat themselves: the first is that whoever is assigned finds themselves in a position they are not good at or cannot sustain, and either fails or burns out. The second is that whoever is actually good at the task sees it go to someone else and feels their contribution is invisible. Both problems end a team from within — the first through exhaustion and failure, the second through frustration and gradual withdrawal. Fair role assignment starts with a clear understanding of what each task requires, then an honest question about capacity and availability — not with who you trust most or who has been here longest.

• Define what the task actually requires before thinking about who will do it: technical skill, physical presence, social communication?
• Ask each person about their capacity and availability — do not assume either from past history
• Allow reserve capacity: do not fill anyone's schedule completely, leave room for the unexpected
• Document the assignment in writing: a short message summarising the task, deadline, and available resources
• Acknowledge early when you have assigned badly and adjust before the failure arrives
• After every activity ask: were the roles well matched to the people who held them?

Briefing and Debriefing — Before and After

Minutes before an activity save hours of correction after it, and minutes after it teach what no classroom training can.

A briefing is the moment when a plan moves from a sheet in the leader's hands to a shared picture in every team member's mind. When an activity starts without a briefing, each person works from their own imagined version of the plan, and those versions will not match when anything goes wrong or conditions change. A good briefing takes no more than ten minutes and answers five questions: what exactly are we doing today, who is responsible for what by name, what is the timeline and its turning points, what might change and what do we do then, and who do we call if we need a decision above our authority?

1. Start with the goal in one sentence: what do we want to have accomplished by the end of this activity?
2. Assign roles out loud in front of everyone so each person knows what role everyone else holds, not just their own
3. Review the timeline and its turning points: when we start, when we stop, when we assess
4. Name what might change and the fallback: "if X happens we do Y" — do not leave the unexpected without a plan
5. Open the floor for one question — whoever stays silent now may act on individual initiative during the activity
6. Close with collective confirmation: "we are all agreed on this" — confirmation reduces individual interpretation later

The debriefing after an activity is the difference between a team that repeats its mistakes and a team that learns. A good debriefing does not look for who made the mistake — it looks for what can be improved. It always begins with what worked, because a team that only hears what it did wrong gradually stops taking initiative and begins working to the safe minimum. It then moves to what could have been better, in descriptive rather than accusatory language: "we noticed coordination slipped in the middle" rather than "you delayed X". It closes with one concrete decision for the next activity — one only, with a name and a date attached.

• What worked better than we expected? — always start here
• Where was coordination or clarity lost, and what caused it to slip?
• Were the assigned roles well matched to the people holding them, or did we need last-minute adjustments?
• What would we do differently if we repeated the activity tomorrow?
• One decision we implement next time — specific, with a time and a name

Follow-up Without Surveillance

Follow-up that discourages more than it supports is not follow-up — it is anxiety walking with authority.

There is a thin line between supportive follow-up and discouraging surveillance, and the difference is not in how often you communicate but in the implicit message each carries. When you call a volunteer and ask "how are things going, do you need anything?" — the message is: I am here with you. When you call every day and ask "where are you up to, why no update?" — the message is: I don't trust you. A team that feels monitored performs to the minimum required and avoids initiative for fear of mistakes. A team that feels supported reports problems before they grow, because it trusts that reporting will not be punished.

Underperformance — How to Address It Without Breaking Anyone

Underperformance is a real problem, silence about it is worse, and addressing it wrongly is worse than either.

When a volunteer underperforms, you have three choices. The first is to ignore it and absorb the work yourself or distribute it — which teaches the whole team that underperformance has no consequences. The second is to escalate immediately to a superior — which teaches the team that you cannot resolve simple problems and only refer them. The third is to have a direct, documented conversation — which is the only choice that respects the person and accomplishes the goal simultaneously. A direct conversation is not a confrontation or a trial; it is an opportunity to understand what you did not see, agree on what changes, and give the person what they need to fix things. Most underperformance is not defiance — it is misunderstanding, exhaustion, or a task that was not the right match at the right time. Only the conversation distinguishes between the cases.

1. Keep to facts not impressions: "the report was not delivered on time" not "you are disorganised"
2. Choose a private quiet moment — never comment on performance in front of others
3. Start with a question not an accusation: "I noticed X — how did you see it?"
4. Listen to the full answer before offering your view — there may be something you don't know
5. Agree together on what will change and by when
6. Document the agreement in a short message immediately after the conversation
7. If the shortfall recurs after two clear conversations, escalate — with documentation in hand

Reading the Team — Early Burnout and Protecting Energy

Signs of burnout appear weeks before someone withdraws. The leader who reads them early saves a person and saves a task.

Team burnout does not arrive suddenly — it accumulates slowly and becomes obvious all at once. The leader who waits until fatigue is visible to the whole team has already missed the right moment to act. Early signals do not announce themselves clearly: slight delays in communication, less initiative from people who always used to take it, shorter replies than usual, minor absences from meetings or activities. These are not neglect — they are messages the body and mind send before the person can put them into words. A good leader notices the change because they know the normal state of each person in their team — and they cannot know it if they never drew people close in the first place.

• Know the "normal state" of each person on your team: how they communicate, their rhythm, how they look when they are doing well
• Change from the normal state is the signal — do not compare a person to others, compare them to themselves
• When you notice a change, start with an open question: "how are you doing with everything?" not "why are you late?"
• Offer load reduction as a real option, not a courtesy: "if you need to defer this week I can arrange it"
• Do not expose fatigue in front of the team — talk to the person privately first
• Schedule rest after major activities — recovery is not empty time, it is part of the work