🌟Transformational and Adaptive Leadership

Shaping a vision the team can see itself in

A vision is not a slogan on the wall; it is a story in which every team member can see their own role and meaning.

An effective leadership vision is not a description of what you as a leader want — it is a picture of what reality can look like when the team is working at its best. Most leaders, when asked about their vision, offer a numeric target, a work plan, or a written institutional mission — not a vision. A vision answers a different question: what will be different in the lives of the people we serve when we succeed? And who is each of us in that picture? A vision that generates real commitment does two things together: it makes the future concrete enough to be believable, and it opens a place inside it for every person on the team. The leader who stands before their team and says "we want to reach ten thousand beneficiaries" gives a number. The leader who says "we want every child in this neighbourhood to have someone who notices when they are absent from school" gives a picture — and between the two there is a large distance in motivation and meaning.

Building a vision with the team rather than for them makes a fundamental difference to what follows. When people take part in constructing the picture of the future, they become its owners rather than its recipients. This does not mean the leader sits empty-handed and asks "what is your vision?" and writes down whatever is said — that is a discussion, not a vision. It means the leader comes with a considered draft and presents it honestly: "this is what I see, and I want to understand what it means to you, and what seems missing from the picture." A team that was genuinely asked and found real space to modify and add will move afterwards in a way that is completely different from a team that received the vision ready-made and sealed. The difference does not show in the project launch meeting — it shows in month three when things become difficult.

Meeting resistance rather than ignoring it

Resistance is not an obstacle to change — it is information about it. The leader who ignores it misses the most important implementation data.

When a change is announced in an organisation or team, resistance usually begins before the first question is asked. Most leaders treat resistance as a problem of attitude or personality — "this person does not want to change" — but this view misses something fundamental: resistance is most often a message, not a flaw. The person who resists carries in their resistance one of many things: fear of loss, a feeling of not having been consulted, a different understanding of what will happen, or a prior experience with promised changes that did not come through. The leader who begins with the question "what are you afraid of losing?" rather than "why are you not cooperating?" suddenly finds themselves in a completely different conversation — one that contains information they can act on.

A change that does not acknowledge what people are losing will not be accepted however correct it may be. This is a central leadership principle sometimes called acknowledged loss — naming what people are leaving behind before asking them to move. Transitioning from a familiar way of working to a new one is not just learning a new skill — it is also leaving a way of working the person had mastered and in which they felt competent and confident. The leader who says "yes, it will be harder at first, and what you have built together will not disappear — we will carry it with us to the new place" opens a door. The leader who says "this is easier and better" and appears not to see the difficulty or the pain closes it — because people feel invisible inside the change process itself.

1. Open the conversation before announcing the decision: "we are considering changing this, and before we decide I want to understand its impact on you"
2. Listen to the concerns without defending — write down what is said and do not respond immediately, so the person feels heard
3. Separate concerns that call for modifying the decision from concerns that only need clarification
4. Modify what can be modified based on what you heard, and tell everyone what changed because of them — this proves the participation was real
5. Be clear about what will not change and why — ambiguity on this is far worse than a clear refusal
6. After implementation, come back and check: what were you afraid of? Did it happen? What did neither of us anticipate?

Adaptive leadership: problems that expertise alone cannot solve

Technical problems have technical solutions. Adaptive problems require people to change something in themselves — and that is a completely different function.

Adaptive leadership is a concept developed by Ronald Heifetz and colleagues, and its core is a simple and deep distinction: some problems are solved by technical expertise — we hand them to the specialist and the solution is implemented. But some problems cannot be solved this way because the solution requires people to change their attitudes, habits, or understanding of their roles. When a technical solution is applied to an adaptive problem, it is not solved — it is postponed or hidden until it returns in a more complex form. Example: a team experiencing declining volunteer participation. The technical solution is to improve communication methods and announce events better. But if the root cause is that volunteers do not feel their contribution is valued or visible, better announcements will not reach them, because the problem is adaptive: it requires changing the way the relationship between leadership and volunteer is built.

The adaptive leader's role is not to carry the problem on behalf of the team — this is what Heifetz calls "taking the work back," a trap that many well-intentioned leaders fall into. When you carry the adaptive problem instead of your team, you relieve them temporarily and keep them incapable in the long run. A team that has learned its leader will solve the hard problems gradually stops learning how to solve them, which makes the leader indispensable in a way that appears like an honour but is in essence institutional fragility — because the whole organisation becomes tied to one person's presence and continuity. The adaptive leader does not give answers to hard problems — they ask the hard questions and maintain the level of tension that pushes people toward change without breaking them.

Building a second line of leaders

An organisation where everything passes through one leader is not strong — it is fragile. Its strength is bounded by one person, and their absence stops it.

A leader who does not build other leaders builds for themselves an organisation that depends on them in a way that feels comfortable in the present moment — everything works, everyone values you, people come to you — but is in reality an institutional bottleneck. Every decision needs you, every crisis waits for you, every new idea passes through you. An organisation that depends on one person only grows as far as that person's capacity, and only expands where they can personally be present. When they are absent, decide to move on, or fall ill, the organisation discovers it has built a great deal around one person instead of building a great deal inside the people. Building a second line of leaders is the highest-impact long-term investment, and also the most postponed, because it yields no visible results next week.

1. Identify clearly who on your team has leadership capacity that has not yet had the opportunity to show — leadership is often visible in crises and side conversations
2. Delegate tasks, not instructions: instead of "do X in way Y", say "this is the outcome needed — you decide how to get there"
3. Allow mistakes in safe environments — a mistake in a small experiment is a free lesson; a mistake in the absence of delegation is a disaster
4. Make your leadership thinking visible: when you make a hard decision, share the thinking process, not just the final outcome
5. Talk about leadership directly: "I see capacity X in you and I want us to build on it together — do you want that?"
6. Delegate full responsibility, not half of it: "this project is yours" is fundamentally different from "help me with this project"

Real delegation means accepting that the person may do things differently from how you would — and that this is usually fine. A leader who delegates then intervenes in every detail has re-centralised the decision covertly, and sent a clear message: "I do not actually trust you." The difference between supervision and intervention is subtle but fundamental: supervision means you are available if needed and track the overall direction. Intervention means you are doing the work in the person's place while appearing to support them. The first builds a leader who trusts themselves. The second builds an employee who executes under the illusion of independence — who, when placed in a new situation, will wait for you.

Holding to values when breaking them would be faster

Values that are not tested under pressure are not truly known. Pressure does not create values — it reveals what was actually there.

In ordinary life, values are easy. Transparency is fine when there is nothing to hide. Respect is easy when nobody makes a mistake or irritates you. And fairness is comfortable when it costs nothing. But values only prove themselves in the moment when breaking them would be faster, cheaper, or less disruptive. These moments happen in daily work more often than is acknowledged: when rushing a decision is comfortable because the meeting has run long, when ignoring a problem is easier than formally raising it, when conceding a principle is possible under the reasoning of "this is one exceptional case." The leader who reinforces values does not do so in the founding speech or the poster on the wall — they do it in these small moments, in a place everyone can see.

When the team sees their leader concede a value once, they learn an implicit lesson: values are conditional on circumstances. When the leader concedes twice, they learn another: flexibility with values is a reward, not an exception. After enough such moments, the declared values become mere decoration — and the team operates according to the actual values they have seen the leader embody in practice, not the ones declared in words. For this very reason, leading by values is not reminding people of the values in team meetings — it is your own commitment to them in the moments when commitment costs something real. The team always notices the difference, even when they say nothing.