The foundation is trust backed by clarity, communication and accountability
- Trust is the base layer: without it, people protect themselves instead of solving problems.
- Shared purpose and role clarity prevent duplication, gaps and quiet resentment.
- Good communication is open, respectful, two-way and inclusive, especially across shifts or departments.
- Psychological safety lets people raise risks, admit mistakes and challenge weak ideas early.
- Supervisors keep the foundation strong by setting expectations, coaching behaviour and dealing with conflict quickly.
Trust is the base layer of good teamwork
Trust changes how people interpret one another’s actions. When trust is low, every delay looks like laziness and every question sounds like criticism; when trust is high, teams give one another the benefit of the doubt and spend less energy on self-protection. In the CIPD’s evidence review on trust and psychological safety, trust is linked directly to teamwork, coordination, communication and collaboration, which is why I treat it as the starting point rather than a nice extra.
In practice, trust is not about liking everyone or agreeing on everything. It is about being able to rely on colleagues to do what they say, share information honestly and handle disagreements without turning them personal. That matters especially in public services, where a delay in a housing case, a safeguarding concern or a patient handover can quickly become a service failure.I also think it helps to separate trust from vague team spirit. A team can be friendly and still be unreliable. Real trust shows up in small behaviours: people follow through, explain changes early, and own mistakes without passing the problem on. Once that is in place, the next challenge is making sure everyone is pulling in the same direction.
That leads straight into purpose and roles, because even a trusting team will drift if the work itself is not clearly defined.
Shared purpose and clear roles stop drift
Shared purpose gives teamwork direction. Without it, people stay busy but pull in different directions, which is why I always ask three questions: what are we here to achieve, who owns which decisions, and where does one person’s work depend on another’s? In a council team, a service desk and a policy unit may both be helping residents, but they need different measures, different handoffs and different escalation routes.
Clear roles do not mean rigid silos. They mean that people understand where their accountability begins and ends. That matters because uncertainty creates hidden duplication on one side and dangerous gaps on the other. When nobody is sure who should chase an issue, the team often ends up doing more meetings and less work.
| What needs clarity | What it answers | Why it matters |
|---|---|---|
| Shared purpose | Why the team exists | Stops people optimising for their own tasks instead of the team outcome |
| Role boundaries | Who does what | Reduces duplication, missed work and blame when things go wrong |
| Decision rights | Who can decide, and when | Speeds up action and prevents constant escalation |
| Escalation routes | What happens when a problem grows | Keeps small issues from becoming avoidable service failures |
In cross-functional public-sector work, this is even more important. When a team spans operational staff, supervisors, policy colleagues and partner organisations, purpose has to be explicit or collaboration will feel messy from day one. I have seen teams become much more effective simply by agreeing what “good” looks like, what gets prioritised first and who is responsible for the final call.
Once direction is clear, communication becomes easier to manage instead of something people hope will sort itself out.
Communication practices that make collaboration workable
Good communication is not a personality trait; it is a team habit. NHS England’s patient safety guidance is very direct here: communication in teams should be open, respectful, honest, two-way and inclusive. That standard matters because teamwork often fails not through open conflict, but through unclear messages, assumptions and things left unsaid.
I find it useful to look at communication in terms of what people actually need from one another, not just how often they speak. A team can meet every day and still communicate badly if those meetings are vague, one-sided or overloaded with status updates that do not lead to decisions.
| Healthy communication | Poor communication | Team effect |
|---|---|---|
| Messages are clear and timely | People find out late, or by accident | Work is duplicated or delayed |
| Questions are welcomed | Questions are treated as resistance | Problems stay hidden |
| Handovers are structured | Assumptions fill the gaps | Errors and omissions increase |
| People check understanding | Everyone nods but nobody is aligned | Plans look agreed until execution starts |
For supervisors, the practical move is to make communication concrete. Use brief but regular team huddles, agree how urgent issues will be escalated, and close meetings with named actions rather than general intentions. In my experience, the teams that do this well sound less polished but perform better because they waste less time interpreting one another.
The next question is whether people feel safe enough to say what they really think, especially when the news is uncomfortable.
Psychological safety is what turns information into improvement
Psychological safety is the confidence to take appropriate risks at work because of the way colleagues and managers will respond. That usually means being able to ask a question, admit a mistake, challenge an assumption or raise a concern without fear of ridicule or punishment. It is one of the main reasons good teams learn faster than average ones.
This matters a great deal in public-sector environments, where silence can look like compliance while hiding real risk. If people do not feel safe speaking up, supervisors hear less about weak processes, pressured workloads, service gaps and emerging safeguarding issues. The team may appear calm, but it is often calm for the wrong reason.
What creates safety is not grand speeches. It is repeated behaviour. Leaders who respond calmly to bad news, thank people for raising issues, and admit their own mistakes make it easier for others to do the same. Teams then shift from defending themselves to improving the work.
I also think this is where many organisations underestimate the role of supervision. A supervisor is often the first person who can either normalise speaking up or shut it down. One dismissive reply can cost more trust than a dozen encouragements can rebuild.
That is why the weekly habits of supervision matter so much. They are where culture becomes visible.
What supervisors should do every week
Supervision is not just about checking output. It is about shaping the conditions in which people can work well together. The best supervisors I have seen do a small number of things consistently rather than trying to be impressive once a quarter.
| Weekly action | What it looks like | What it improves |
|---|---|---|
| Set the priorities | Say what matters most this week and what can wait | Reduces confusion and protects focus |
| Check workload honestly | Ask what is stuck, overloaded or unclear | Prevents quiet burnout and hidden backlogs |
| Give specific feedback | Name the behaviour, not just the person | Builds learning without defensiveness |
| Address tension early | Deal with friction before it hardens into sides | Protects trust and working relationships |
| Recognise useful behaviour | Notice follow-through, cooperation and calm problem-solving | Reinforces the habits that keep teams reliable |
There is a practical limit here, and it is worth saying plainly: if a supervisor has too many direct reports, the basics get squeezed out. That is when communication becomes reactive, feedback becomes rare and conflict is addressed only after it has become visible to everyone else. Good supervision is partly skill, but it is also a question of whether the manager has enough bandwidth to lead properly.
Once those weekly habits are in place, the remaining task is to avoid the quiet mistakes that erode teamwork faster than most people realise.
The mistakes that erode teamwork before anyone notices
Most weak teams do not fail because they lack talent. They fail because they keep repeating a few preventable habits. I see the same pattern often enough to treat it as a checklist of warning signs.
- Confusing harmony with trust - people stay pleasant, but they avoid hard conversations.
- Leaving roles vague - everyone is helping, but nobody knows who owns the outcome.
- Treating silence as agreement - the team nods in meetings and unravels later in delivery.
- Overloading meetings - the group talks a lot but makes few decisions.
- Ignoring small tensions - minor irritation becomes workplace politics.
- Rewarding speed over clarity - work moves quickly at first, then creates rework and confusion.
If I were supervising a team in the UK public sector, I would focus first on trust, then on purpose, then on communication, and then on psychological safety. Get those four elements right, and most teamwork problems become manageable management problems instead of permanent cultural damage. That is the practical answer to the question, and it is usually simpler than people expect.
