Leadership
Use conflict before it uses you
Good leaders do not treat conflict as a personal failure. They treat it as information.
In small organisations, conflict is often avoided because people know each other too well. Nobody wants to damage the atmosphere, upset the founder, challenge the volunteer, or become “difficult.” So the team chooses artificial harmony. Everyone stays pleasant, and the bad decision survives.
Leadership means making disagreement usable. That requires separating the person from the issue, inviting dissent before decisions harden, and making it normal to test ideas. The question is not “how do we avoid conflict?” The better question is “how do we make conflict clean enough to improve the work?”
Communicate before the grapevine does
When formal communication is weak, informal communication takes over. The grapevine is fast, creative and usually underqualified.
Leaders often avoid communicating until they have perfect information. That sounds responsible, but in a small team it can create a vacuum. People sense uncertainty anyway. If they are not given a clear message, they will build one from fragments, tone changes and whatever someone half-heard in the kitchen.
Good project communication does not mean flooding people with updates and hoping they decode the important parts. It means being clear about what matters, what is known, what is not known yet, and what decisions are coming. Instead of “spray and pray,” use “underscore and explore”: emphasise the key message, then create space for questions, concerns and interpretation.
Stop being the whole operating system
Leadership in small organisations often starts with good intentions and ends with one exhausted person holding the entire project together by force of personality, memory and mild panic.
This is especially common in small businesses and charities. The founder, manager or project lead often knows the history, the people, the funders, the customers, the passwords, the printer issue from 2021 and the exact tone that will not annoy the board. Naturally, everything flows through them. Also naturally, this becomes a problem.
The heroic leader is a seductive myth. It says the leader should have the vision, make the decisions, motivate the team, fix the conflict, protect the standards and somehow remain emotionally available while answering emails at midnight. That is not leadership. That is becoming infrastructure.
Good project leadership is about making sure the project does not collapse when one person stops carrying it.
You do not need to be complete
The idea of the “complete leader” is both flattering and dangerous. Nobody is equally good at strategy, relationships, planning, communication, decision-making, conflict, technical detail and emotional support. Pretending otherwise creates bottlenecks.
A better model is the incomplete leader: someone who understands their own strengths and weaknesses and builds leadership around the team, not just themselves. This is not an excuse to disappear or delegate chaos. It means knowing when to lead directly, when to ask better questions, when to bring in expertise, and when to let someone else own a piece of the work properly.
For small organisations, this matters because founder-dependency is one of the quietest risks. The project may look efficient because one person knows everything. In reality, it is fragile. If that person becomes unavailable, tired, distracted or simply human, the whole system starts wobbling.
The four jobs of project leadership
A useful way to think about leadership is through four capabilities: sensemaking, relating, visioning and inventing.
Sensemaking means understanding what is really going on. What problem are we solving? What constraints are real? What are we assuming? What has changed? A leader who skips sensemaking often leads confidently in the wrong direction, which is still wrong, just with better posture.
Relating means building the trust and relationships needed for people to speak honestly. This is not about being universally liked. It is about being credible enough that people will tell you the truth before the project is on fire.
Visioning means giving people a clear picture of where the project is going and why it matters. “We need to improve operations” is fog. “We need a booking process that reduces missed appointments, saves staff time and makes life easier for clients by September” gives people something to organise around.
Inventing means creating new ways to get there. Small organisations rarely have perfect resources, so leadership often involves practical creativity: simplifying the plan, finding partners, changing the workflow, or building a workaround that is not glamorous but actually works.
Set the emotional weather
Leaders set the emotional weather of a project. If the leader panics, hides information, punishes mistakes or treats every challenge as disloyalty, the team learns quickly. People stop raising problems. They perform agreement. They wait.
Psychological safety means people can ask questions, admit mistakes, challenge assumptions and raise concerns without being embarrassed or punished. It does not mean the team becomes soft or endlessly therapeutic. It means the team becomes honest enough to function.
This is where emotional intelligence matters. A technically brilliant leader who cannot manage their reactions will still create silence around them. The first time someone raises a concern and gets dismissed, the meeting continues, but the real conversation leaves the room.
Strategy is not planning
Strategy, planning, implementation and governance are related, but they are not the same thing.
Strategy chooses the direction. Planning works out the route, resources, timeline and responsibilities. Implementation does the work. Governance checks whether the work still makes sense, still has authority, and still deserves support.
Confusing these creates trouble. A detailed plan is not a strategy. A busy organisation is not necessarily a strategic one. A project delivered on time can still be the wrong project. That is the uncomfortable part people often avoid: good execution does not rescue a bad choice. It just delivers the mistake more efficiently.
Choose what not to do
A useful strategy creates focus. It says yes to some things and no to others. This is where many small organisations struggle, especially charities and mission-led businesses. When the cause matters, every opportunity can feel morally important. Every grant looks tempting. Every partnership seems worth exploring. Every service gap feels like something you should fix.
But saying yes to everything is not generosity. It is strategic self-harm.
A charity that chases every available funding stream may end up running projects that do not fit its mission, confuse staff, exhaust volunteers and make the organisation harder to explain. A small business that copies every competitor may lose the thing that made it distinctive. A team that keeps adding initiatives without stopping anything is not becoming more ambitious. It is building a museum of unfinished intentions.
Strategy requires trade-offs. What will you not do? Which customer or beneficiary will you prioritise? Which projects will you pause? Which “nice idea” does not deserve resources right now?
The strategy is often hidden in the no.
Tools to use
Use to identify where you are strong and where the project needs support from others.
Leadership Capabilities Audit
Use to check whether meetings involve real questions, concerns and shared learning, or just top-down updates with better chairs.
High-Quality Conversation Checklist
Use to decide how to communicate changes, uncertainty and decisions before the grapevine writes its own story.
Communication Strategy Selector
“Management is doing things right; leadership is doing the right things.”
— Peter Drucker
Recommended reading & sources
Ancona, D. – “In Praise of the Incomplete Leader”
A useful read for leaders who feel they have to do everything themselves. It explains why good leadership often means knowing your gaps and building support around them.
Edmondson, A. – The Fearless Organization
Helpful for understanding how leaders create teams where people can speak up, raise concerns and learn from mistakes.
Clampitt, P.G. – Communicating for Managerial Effectiveness
Good for improving leadership communication, especially when people need clarity rather than another vague update.
Lencioni, P. – The Five Dysfunctions of a Team
A practical leadership book on trust, conflict, commitment, accountability and results. Useful for spotting where a team is quietly getting stuck.
Goleman, D. – “What Makes a Leader?”
A clear introduction to emotional intelligence and why technical competence alone is not enough to lead people well.
Amabile, T.M. & Kramer, S.J. – The Progress Principle
Useful for leaders who want to keep people motivated through clear goals, visible progress and small wins.