
Trust does not arrive with time. It does not grow from team-building events or years of shared lunches. Trust is a decision - and after that decision, a practice. This is the part most leaders skip.
Date Created | Date Modified
2025-09-07
|
Author
Mats Soomre
Share this article
Trust in a team is a decision, and after the decision a practice. It is when you can act on a colleague’s recommendation without needing every detail explained, because you know what he is good at and what he is not. It does not grow from time, lunches or team-building days. It grows when someone decides to go first. Its absence is quiet: the first sign is that people stop saying things as they are. Five questions tell you where your team stands, and one figure explains why so few teams get there on their own.
Trust does not arrive with time. It does not grow from team-building events, shared lunches, or years of sitting in the same office. Trust develops when someone decides to go first. This is the part most leaders skip.
What is trust in a team?
Trust is when you can follow a colleague’s recommendation without needing every detail explained. Not blindly - but with enough confidence in her competence and intentions that you act on her input without second-guessing it.
Underneath that sits something simpler: the feeling that people will not harm the team or each other, and that they genuinely care how everyone in it is doing. The test is short. People do what they say, and say what they do.
That is a high standard. Most teams operate well below it. And most leaders do not notice, because the absence of trust is quiet.
Why two hours is enough
I run trust as the first topic of every team programme, and I give it two hours. If two hours cannot build trust between people who share a goal, something important is missing - and the missing thing is almost never time.
Research on temporary teams says the same. Debra Meyerson and her colleagues described it in 1996 as swift trust: a group that has to start working now assumes trust first and verifies it afterwards, adjusting as the evidence comes in. Project teams, crews and task forces run on it every day. Waiting for trust to accumulate is a luxury most teams never had.
In practice it is a short exchange. Can I trust you? Can I rely on you? Will you do what you promised, help when I need it, and say things as they are, with respect? Yes. Then I will do the same. Decided. Now, what are you good at?
That last question is where the two hours usually go, and it is the subject of the last section.
How does trust disappear?
Trust does not disappear loudly. It fades in silence.
The first sign is always the same: people stop saying things as they are. Problems go unmentioned. Suggestions stop coming. Meetings become polite and empty. The leader reads this as alignment. It is the opposite.
A team where everyone is too polite and too agreeable is not a team with good relationships. It is a team where trust has already left the building. Openness depends on trust, and trust depends on openness - which is why the fall, once it starts, is hard to see from inside.
The quiet person is not always the problem. Sometimes silence is thinking. Read The Two People You Call Difficult Are the Two You Can’t Decide Without. When silence replaces honesty, demotivation follows close behind. Read Before You Motivate, Remove What Demotivates.
Are trust and psychological safety the same thing?
They are connected but distinct. Trust is between individuals - I trust you specifically, based on experience and decision. Psychological safety is a property of the group. Amy Edmondson, who has studied it for thirty years, defines it as the shared belief that this team will not punish a person for speaking up with a question, a concern, a mistake or an idea.
You can trust your direct colleague completely and still feel unsafe in the wider team. You can feel safe in a group discussion and still not trust one particular person in the room.
Both are needed. A team with trust but no psychological safety has strong pairs and weak collective courage. A team with psychological safety but no interpersonal trust has open discussions that never turn into reliable follow-through.
Five questions that test trust
Answer these honestly about your own team. Not the team you describe at conferences - the one you sat with on Tuesday.
Will my weaknesses be used against me?
Do my colleagues genuinely care about me, and about the whole team?
Can we speak our minds without negative consequences?
Do people do what they say, and say what they did?
Can I be who I truly am here, without pretending?
Five yeses is rare. Four is a team worth working with. Three or fewer, and the silence described above has probably already started - you have not counted it yet.
What does trust require from the leader?
The leader sets the tone. Not through words - through response.
When a team member tells the leader something is wrong, and the response is “Thank you for noticing - let’s see what we can do,” trust and openness begin to grow. When the response is “that’s not your concern,” initiative disappears. And with it, the willingness to collaborate.
A leader who says “I value honesty” and then reacts badly to the first honest thing someone says has destroyed more trust in one moment than she can rebuild in a year.
The practical test: how openly and boldly do people talk to you about their own mistakes and weaknesses? If they hide these, the trust is not where you think it is. The everyday minimum - showing up, doing the work properly, and nothing beyond it - is what a team looks like when that test has been failed.
The leader who cannot read her own impact will misjudge how much trust the team has. Read Self-Awareness: You Think You Know Yourself. Your Team Sees Something Different.
Is trust only the leader’s job?
No. This is where most advice stops - as if trust is something the leader creates and the team receives. Trust is a team function. Every member builds it or erodes it.
A thought and a proposal is not a decision. It is an invitation to discuss. Teams where people understand this distinction argue productively. Teams where every idea is treated as a challenge to authority, or as a final position, stop offering ideas at all.
There is a tension every team member feels and few name. Tim Urban draws it as two overlapping circles: my team and my principles. Going against my principles to support the team is one failure. Going against the team to stay true to my principles is the other. The overlap - supporting the team while staying true to what I think - is the only place where trust is built, and it is a narrower space than it looks. Speaking up is how you stay in it.
The team must agree on how it handles disagreement, how it discusses uncomfortable topics, and what happens when someone makes a mistake. These are not natural conversations. They need structure, and often someone from outside the team to create the conditions for them.
Google’s Project Aristotle found psychological safety to be the single most important factor in team performance. Read Google Spent Years Researching What Makes Teams Work. Belbin Knew the Answer Decades Earlier.
How do you break the silence?
In many teams a silent pattern runs underneath everything: nobody talks openly because there is no trust, and trust does not develop because nobody talks openly.
Breaking the circle requires someone to go first. Usually the leader. Sometimes a team member with enough courage and standing to say what others will not. Occasionally an outside coach who builds the structure for a conversation the team has been avoiding.
The break always feels risky. The first honest conversation after a long silence is uncomfortable. But - and I have watched this in hundreds of teams - nothing bad usually happens. The disagreement does not destroy the team. Trust rises to a level it never reached during all those months of polite silence.
Why does knowing each other’s strengths build trust faster?
Here is the part of trust that the leadership books leave out. Trust is not only about intentions. It is about predictability. I trust you when I know when, where and how you tend to behave - what you are good at, what you are not, and what to expect from you when the pressure arrives. Once I know that, I stop being surprised by you, and I stop reading your behaviour as a message about me.
That is why I use Belbin Team Roles in the trust conversation. It describes behaviour, not personality: how a person contributes to a team, based on his own view and on the view of four to six colleagues who work with him. When those two views are on the table, expectations can be aligned. Not “why are you like this?” but “this is what you bring, this is what I bring, this is where we will need to adjust.”
There is a catch, and it is measurable. Across more than 78,000 Belbin profiles from over 30 countries, only 17.7% show a coherent match between how people see themselves and how their colleagues see them. Most of us are carrying a self-image our team does not recognise. You cannot align expectations on a picture of yourself that nobody else can see. That is where a great deal of “trust” breaks - not on bad intent, but on two different pictures of the same person.
When a new person joins, the whole process starts again - not from zero, but the newcomer has no history with the group and does not know the unwritten rules. A profile visible alongside the rest of the team moves the first weeks from guesswork to specifics. For the nine-role framework behind this, read Belbin Team Roles: The Practitioner’s Guide to What Teams Actually Need. For the gap between self-view and observer view, read Self-Awareness: You Think You Know Yourself. Your Team Sees Something Different.
One question
If trust in your team disappeared tomorrow - not through a dramatic event, but through the slow, quiet process of people choosing silence over honesty - how long would it take you to notice?
In most teams, longer than you think. That is why trust is not a feeling to wait for. It is a decision to make, a practice to maintain, and a conversation to have before the silence settles in.
Every team that built trust did so because someone went first - said something honest, admitted something uncomfortable, disagreed without apology. The question is whether you will be that someone. See your own profile →, then have the conversation you have been avoiding. Trust rises faster than you expect - because nothing bad usually happens, and your team will remember who decided to go first.
Frequently asked questions (FAQ)
What is trust in a team?
Trust in a team is when you can act on a colleague’s recommendation without needing every detail explained - with enough confidence in his competence and intentions that you do not second-guess him. Underneath it sits the feeling that people will not harm the team or each other and genuinely care how everyone is doing. The short test: people do what they say, and say what they do.
How do you build trust in a team?
Decide it, then practise it. Trust does not grow from time or team-building days; it grows when someone goes first - says something honest, admits a mistake, disagrees without apology. Then make expectations visible: agree how the team handles disagreement and mistakes, and learn what each person is good at and not good at, so behaviour stops being a surprise. Two hours is usually enough to start.
What is the difference between trust and psychological safety?
Trust is between individuals: I trust you specifically, based on experience and decision. Psychological safety is a property of the group - Amy Edmondson’s term for the shared belief that the team will not punish a person for a question, a concern, a mistake or an idea. A team can have strong pairs and weak collective courage, or open discussions with no reliable follow-through. It needs both.
What are the signs that a team has lost trust?
The signs are quiet. People stop saying things as they are. Problems go unmentioned, suggestions stop coming, meetings become polite and empty, and people do the everyday minimum - proper work, nothing extra. Leaders often read this as alignment. It is the opposite. Watch how openly people admit mistakes and talk about their own weaknesses; if they hide these, trust is not where you think it is.
Is trust the leader’s responsibility?
The leader sets the tone through response, not words - what happens the first time someone brings bad news decides more than any values statement. But trust is a team function. Every member builds it or erodes it, and a team where people treat every proposal as a final position, or every disagreement as an attack, will lose trust regardless of the leader.
How does Belbin help build trust in a team?
Trust is partly predictability: knowing when, where and how a colleague tends to behave, what he is good at and what he is not. Belbin Team Roles describes exactly that behaviour, from a person’s own view and from four to six colleagues who work with him, so expectations can be aligned instead of guessed. Only 17.7% of Belbin profiles show a coherent match between self-view and colleagues’ view, which is why so many teams misread each other.
Photo by Mats Soomre · #MomentsBySoomre · moments.soomre.com
