Teams
Fight cleanly
Good teams do not avoid conflict. They learn how to have it without turning it into a personality contest.
Healthy conflict focuses on the issue, not the person. It uses facts, examples and alternatives. Instead of saying, “that will not work,” ask, “what would need to be true for that to work?” Instead of letting the loudest person win, create space for quieter people to contribute. Instead of forcing consensus too early, compare two or three real options.
Bad conflict gets vague, personal or political. But no conflict is not the answer either. Avoided conflict does not disappear. It becomes delay, resentment, passive resistance, or another meeting about the same problem next week.
A team that cannot disagree cannot really decide.
Make it safe to speak up
Psychological safety means people can ask questions, admit mistakes, challenge assumptions and raise concerns without being punished or embarrassed. It does not mean the team becomes soft. It means the team becomes honest enough to learn.
This matters because silence is expensive. A volunteer who does not understand their role may simply disappear. A junior employee who notices a risk may keep quiet because they do not want to seem negative. A whole team may privately disagree with a decision and publicly nod along because everyone wants to be “supportive.”
That is not alignment. That is theatre.
Leaders build psychological safety through reactions, not speeches. If someone raises a concern and gets dismissed, the team learns the rule immediately. If mistakes are treated as evidence rather than personal failure, people are more likely to surface problems early, when they are still fixable.
Turning good people into a working unit
Putting good people in the same room does not automatically create a team. It creates a room with good people in it. Sometimes that is enough. For simple work, a loose group can get by: one person writes the email, someone else makes the poster, another person sorts the budget, and everyone hopes the pieces eventually meet in the middle.
Projects are usually less forgiving. They expose every vague role, every polite silence, every “I thought someone else was doing that.” This is especially true in small businesses and charities, where teams are often built from whoever is available, trusted, enthusiastic, or standing nearest to the problem. That is understandable. It is also how one reliable person accidentally becomes the entire operating system.
A real team is not defined by friendliness. It is defined by shared purpose, complementary skills, clear responsibilities and mutual accountability. People are not just doing separate tasks beside each other. They are carrying the same outcome together.
Are you a group or a team?
A working group depends mainly on individual outputs. This can work when tasks are simple and separate. A real team is needed when the work is interdependent: when one delay affects someone else’s task, when decisions need several perspectives, or when the final result depends on people combining judgement rather than simply completing a list.
The test is simple: if the work can fail because people are not aligned, you need a team. Not a WhatsApp group. Not a list of names. A team.
For a charity, this might mean launching a fundraising campaign, applying for a grant, organising an event, or coordinating volunteers. For a small business, it might mean opening a new location, improving a service, building a website, or changing how customers are handled. In all of these cases, the problem is rarely just “workload.” It is usually coordination, ownership and decision-making.
Design the team before the work starts
Good teams are designed. They do not appear because everyone has good intentions and a shared Google Drive.
Before delivery begins, the team needs three things.
First, a clear purpose. “Improve our website” is not a project goal. It is a fog machine. “Launch a clearer mobile-friendly website by June that explains our services and increases online enquiries” is something people can actually organise around.
Second, the right mix of skills. Small organisations often choose people because they are available, loyal or generally competent. That helps, but it is not enough. A project team needs technical skills, problem-solving skills and interpersonal skills. Someone has to make the thing. Someone has to organise the thing. Someone has to notice when the thing is quietly falling apart.
Third, the team needs support. This means time, information, budget, tools, authority and access to the people who can actually make decisions. Without that, the team may look chaotic when really it was under-equipped from the start.
Expect some storming
Early tension does not mean the team is failing. It may mean the team is becoming real.
Most teams go through some version of forming, storming, norming and performing. At first, people are polite. Then the real questions appear. Who is actually leading? Who decides when people disagree? What standard are we working to? Who is allowed to challenge whom? Who always ends up doing the invisible work?
This stage is uncomfortable, but useful. It brings hidden assumptions into the open. The mistake is pretending it is not happening. Small teams often protect the atmosphere at all costs, especially when people are friends, volunteers or long-term colleagues. The result is artificial harmony: everyone is pleasant, nobody says the difficult thing, and the project quietly pays the bill.
The goal is not to eliminate tension. The goal is to make tension useful.
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 help the team agree its purpose, roles, decision rules, communication norms and conflict process before pressure hits.
Use to show what skills exist in the team, who is overloaded, and where support or training is needed.
Use to keep discussions focused: what are we deciding, who owns the next action, what concerns have not been said yet?
Meeting and Conflict Toolkit
“Great things in business are never done by one person, they’re done by a team of people.”
— Steve Jobs
Recommended reading & sources
Katzenbach, J.R. & Smith, D.K. – “The Discipline of Teams”
A clear starting point for understanding what makes a real team different from a group of people working beside each other.
Haas, M. & Mortensen, M. – “The Secrets of Great Teamwork”
A practical guide to the conditions teams need before they can perform well: direction, structure, support and shared mindset.
Edmondson, A. – “Psychological Safety and Learning Behavior in Work Teams”
Useful for understanding why people need to feel safe enough to speak up, ask questions and admit mistakes.
Eisenhardt, K.M., Kahwajy, J.L. & Bourgeois, L.J. – “How Management Teams Can Have a Good Fight”
Helpful for learning how teams can disagree productively without turning conflict into a personality contest.
Amabile, T.M. & Kramer, S.J. – “The Power of Small Wins”
A useful read on why visible progress, small achievements and meaningful work help keep teams motivated.
Lencioni, P. – The Five Dysfunctions of a Team
An accessible business book on trust, conflict, commitment, accountability and results. Best used as a practical team check-up.