Working Together Doesn’t Make You a Team
Updated: Oct 27

I’ve spent much of my professional life working in teams. Some have been exceptional. Others have been groups of highly capable, committed people who, despite their individual talents, never quite managed to become a team.
I’ve experienced this in medicine, in corporate leadership and in the voluntary sector. Different environments, different personalities and different objectives, but remarkably similar challenges.
One of the things I’ve come to appreciate is that putting people together and giving them a common objective doesn’t automatically create a team.
We recruit capable individuals, establish responsibilities, agree objectives and expect them to collaborate. We arrange regular meetings, perhaps organise an occasional team-building day, and hope that a sense of collective identity will emerge. Sometimes it does. Often it doesn’t.
People can work alongside one another for years without developing a meaningful sense of connection. They can attend the same meetings, report to the same manager and contribute towards the same organisational goals while feeling surprisingly isolated.
And this matters because the quality of relationships within a team affects much more than whether people enjoy coming to work. It influences how they communicate, make decisions, handle disagreements, respond to pressure and ultimately perform.
The difference between a group and a team
I think one of the most important distinctions in leadership is between a group of people who work together and a team that genuinely supports one another.
A group can function perfectly adequately through clearly defined roles, individual competence and established processes. A team requires something more.
It requires people to understand one another, recognise their interdependence and accept a degree of responsibility for each other’s success. In a genuinely cohesive team, individuals don’t simply ask, “Am I doing my job well?”
They also ask, “How can I help the people around me succeed?”
That shift in thinking is subtle, but its consequences can be profound.
I’ve worked with individuals who were outstanding at their jobs but struggled to contribute effectively to a wider team. Equally, I’ve worked with people whose greatest contribution wasn’t necessarily their technical expertise, but their ability to bring others together, offer encouragement and create an environment in which colleagues could flourish.
Over time, I’ve become increasingly convinced that the effectiveness of a team is not simply the sum of its individual capabilities. It is also a product of the relationships between those individuals.
Start by understanding, not fixing
When leaders recognise that their team lacks cohesion, the instinctive response is often to organise some form of team-building activity.
Perhaps an away day, a personality assessment or a workshop on communication.
These activities can be enjoyable and occasionally valuable, but I would argue that they frequently begin in the wrong place.
Before attempting to improve a team, we need to understand why it isn’t functioning as well as it could. And the reasons are not always obvious. Sometimes the problem is relational. People simply don’t know one another particularly well, or past disagreements have never been properly resolved.
Sometimes it’s structural. Individuals work in separate functions, rarely collaborate and have little appreciation of the challenges their colleagues face.
Sometimes it’s cultural. People are reluctant to admit mistakes, challenge decisions or acknowledge that they’re struggling.
And sometimes it’s leadership itself. Unclear expectations, inconsistent decisions or an unwillingness to address difficult behaviour can undermine even the most committed group.
These are fundamentally different problems, and they require different responses.
This is why, when approaching team development through coaching, I would always begin by listening. Not simply to the team leader, but to the individuals within the team.
I’d want to understand how people experience working together, what they value about their colleagues and what makes collaboration difficult.
One question I find particularly revealing is:
“When you’re having a difficult day at work, who do you turn to?”
If the answer is consistently “nobody”, or if people feel uncomfortable asking colleagues for help, that tells us something important about the culture of the team.
Another useful question is:
“What do you wish your colleagues understood about your role?”
It’s remarkable how frequently people work closely together without appreciating the pressures, frustrations or responsibilities experienced by those around them.
Before people can support one another effectively, they need to understand one another.
Trust is built in ordinary moments
Psychological safety has become a familiar term in leadership discussions, sometimes to the point of losing its practical meaning.
At its simplest, it describes an environment in which people feel able to speak openly, ask questions, acknowledge mistakes and express concerns without fearing humiliation or punishment. It’s not about avoiding difficult conversations or ensuring that everyone agrees. Quite the opposite.
A psychologically safe team should be better equipped to disagree constructively because individuals trust that disagreement won’t damage their relationships or standing within the group.
Reflecting on my own leadership experience, I recognise that trust is rarely established through grand gestures. It develops through repeated, often unremarkable interactions.
A colleague admitting they don’t know something and receiving help rather than criticism. A manager acknowledging they’ve made a mistake. Someone noticing that a colleague is overwhelmed and offering practical support.
A difficult conversation handled respectfully rather than avoided.
Each interaction contributes to an individual’s understanding of whether the team is a safe and supportive place to work. Of course, the reverse is equally true.
Trust can be undermined by seemingly small behaviours: dismissing someone’s concerns, making decisions without explanation, criticising colleagues in their absence or failing to follow through on commitments.
As leaders, we sometimes underestimate how closely people observe our behaviour, particularly when circumstances become difficult. It’s relatively easy to demonstrate supportive leadership when everything is going well. The real test comes when someone makes a mistake, challenges our judgement or tells us something we don’t particularly want to hear.
Being nice isn’t the same as being supportive
This is something I’ve thought about increasingly over the years, particularly in organisations where people are strongly motivated by shared values. There can be an understandable desire to preserve harmony.
People want to be kind, encouraging and respectful. These are admirable qualities.
But sometimes the desire to maintain positive relationships can discourage the very conversations needed to make those relationships stronger.
Difficulties go unaddressed. Frustrations accumulate. People discuss concerns privately rather than speaking directly to those involved. Outwardly, the team may appear harmonious. Underneath, trust is gradually being eroded.
I’ve come to believe that genuine support sometimes requires the courage to have an uncomfortable conversation.
It means being willing to challenge someone respectfully when their behaviour is affecting others. It means giving honest feedback rather than simply offering reassurance. And it means accepting that disagreement is not necessarily evidence of a poor relationship.
In fact, the ability to disagree openly while maintaining mutual respect may be one of the clearest signs of a healthy team. This is particularly relevant in churches, charities and other values-driven organisations, where the language of community, service and shared purpose can sometimes make professional accountability more complicated.
Shared values should strengthen our ability to have honest conversations, not become a reason to avoid them.
People need to feel understood before they can feel connected
One of the exercises I particularly value in team coaching is deceptively simple.
I invite people to reflect on three questions:
What do I find most rewarding about my work?
What do I find most difficult?
What do I wish my colleagues understood about me?
The purpose isn’t to encourage unnecessary personal disclosure. Nobody should feel obliged to share something they’re uncomfortable discussing. Instead, it creates an opportunity for colleagues to see one another beyond their job titles and responsibilities. Someone who appears distant may actually be struggling with an overwhelming workload. Someone perceived as overly critical may be deeply concerned about maintaining standards. Someone who rarely contributes during meetings may need more time to process information before expressing an opinion.
Understanding these differences doesn’t excuse poor behaviour, but it can help us interpret one another more accurately. And that matters.
As many workplace tensions arise not from deliberate hostility, but from assumptions about other people’s motivations. We interpret behaviour through our own experiences, often without recognising that our interpretation may be wrong. Coaching can help individuals examine those assumptions and consider alternative explanations. Sometimes a relatively small change in understanding can transform a working relationship.
Mutual support needs to become a habit
One of my concerns with traditional team-building programmes is that they can create a temporary sense of connection without fundamentally changing how people work together.
Everyone enjoys the away day, leaves feeling positive and returns to precisely the same working patterns. Within a few weeks, very little has changed. If we’re serious about building stronger teams, we need to translate good intentions into consistent behaviours. And those behaviours don’t necessarily require elaborate interventions.
For example, imagine beginning a weekly team meeting with three questions:
What’s gone well this week?
What’s been difficult?
What support would be helpful next week?
Fifteen minutes spent discussing these questions could be more valuable than another hour reviewing operational updates. Not because operational performance is unimportant, but because effective performance depends on people being able to work together. Another approach I particularly like is peer coaching.
Rather than immediately offering solutions when a colleague describes a problem, team members learn to listen and ask thoughtful questions.
“What do you think is making this particularly difficult?”
“What have you already tried?”
“What options have you considered?”
“What would be most helpful from me?”
These are simple questions, but they change the nature of the conversation.
Instead of creating dependence on someone else’s advice, they help individuals think more clearly and develop their own solutions.
They also communicate something important: I’m interested in understanding your experience, not simply telling you what to do. Over time, these interactions can help establish a culture in which mutual support becomes normal rather than exceptional.
Individual responsibility matters
There’s another dimension to team development that I think is sometimes overlooked.
We tend to talk about team culture as though it’s something created by the leader and experienced by everyone else.
Leadership undoubtedly has a disproportionate influence, but every member of a team contributes to its culture. Each of us brings habits, assumptions, insecurities and preferred ways of working into our relationships.
Some people respond to pressure by becoming controlling. Others withdraw.
Some become impatient or overly direct. Others avoid difficult conversations altogether.
I’ve certainly had occasions during my own career when, looking back, I can recognise that my response to pressure wasn’t particularly helpful to those around me.
It’s easy to justify our behaviour by pointing to the circumstances we were facing.
It’s harder, but considerably more productive, to ask how our behaviour affected others.
This is where individual coaching can complement group development.
A team session might help people agree that they want to communicate more openly.
Individual coaching can help someone recognise why they personally find openness difficult.
A team might commit to handling disagreements constructively. Individual coaching can help a participant understand why they become defensive when challenged.
Team development creates collective commitments. Individual coaching helps people understand what might prevent them from fulfilling those commitments.
Both have a role.
The leader has to go first
Perhaps the most important lesson I’ve learned is that leaders cannot simply instruct a team to become more trusting, collaborative or supportive. They have to demonstrate what those behaviours look like.
If we want people to acknowledge mistakes, we need to acknowledge our own.
If we want honest feedback, we need to demonstrate that we can receive it without becoming defensive.
If we want colleagues to support one another, we need to notice when people are struggling and respond appropriately.
And if we want people to feel valued, we need to ensure that our behaviour consistently communicates that value.
This doesn’t mean leaders need to share every personal concern or abandon professional boundaries. It means recognising that culture is shaped far more by what people experience than by what leaders say they believe.
A team can have an impressive set of values displayed on the wall, but if those values aren’t reflected in everyday interactions, they become little more than decoration.
I’ve seen the consequences when leaders underestimate this distinction.
People quickly recognise the difference between an organisation’s stated culture and its lived reality. And when the two diverge, cynicism can develop remarkably quickly.
How do we know when a group has become a team?
I don’t think the answer lies primarily in how well people get along socially.
Some excellent teams contain individuals with very different personalities, interests and approaches to work. They may never become close friends. Nor should they have to. The real indicators are behavioural.
Do people ask for help before they become overwhelmed?
Can they disagree without damaging relationships?
Do they recognise and celebrate one another’s achievements?
Are they willing to challenge behaviour that undermines the group?
Do they understand how their individual contributions support the wider purpose?
And perhaps most importantly, do they feel that their colleagues genuinely care whether they succeed?
These are the questions I would ask when assessing whether team development has made a meaningful difference. Not whether everyone enjoyed the workshop. Not whether they completed a personality questionnaire. And certainly not whether they managed to construct the tallest tower out of spaghetti and marshmallows. The measure of success is whether the experience of working together has changed.
A final reflection
Looking back across my career, the teams I remember most fondly aren’t necessarily those that achieved the greatest commercial success or delivered the most impressive results.
They’re the teams in which I felt that people genuinely looked out for one another.
Where difficult days were shared rather than endured alone. Where disagreements could be expressed without fear. Where individual achievements were celebrated collectively. And where people recognised that their responsibilities extended beyond their own job descriptions.
Those environments didn’t emerge simply because everyone was pleasant or because we shared a common objective. They developed through trust, mutual understanding, consistent leadership and a willingness to invest in relationships.
I also recognise that, as a leader, I haven’t always got this right.
There have been times when I’ve been too focused on delivering results, resolving problems or moving things forward to give sufficient attention to the relationships that made those outcomes possible.
With experience, I’ve come to appreciate that investing in those relationships isn’t a distraction from leadership. It is an essential part of it.
A group of people becomes a team when they stop thinking only about what they need from one another and start thinking about what they owe one another.
And perhaps that’s the question every leader should occasionally ask:
Have I created a group of people who work for the same organisation, or a team of people who genuinely work for one another?






Comments