3 practical tools to build trust in teams

Trust in a team is built by repeated small behaviours that are easy to describe and hard to keep doing. Many leaders know this and have no method for it, so trust ends up being something they hope will develop.

The symptoms of low trust are quiet. People hedge in meetings and say the real thing in the corridor afterwards. Problems surface at the point where they have become expensive. Work gets checked twice because nobody is sure the first person did it properly.

This piece covers three tools you can put in place in a fortnight: a written team working agreement, a visible commitment log and a shared language for behavioural style. It also covers what changes in a distributed team and where this work usually fails.

Inner Leader has run team development with UK and global organisations since 2014. The client example below is a team of thirty-four people who had never worked together before.

What trust in a team means

Trust in a team is the willingness to be exposed to a colleague's behaviour without protecting yourself first. In practice it shows up as three specific things: people say what they think in the meeting, they hand work over without re-checking it and they admit a mistake early enough for it to be fixed cheaply.

Those three are observable, which means trust can be managed like anything else you can observe. A leader who wants to know where their team sits can count how often a decision gets reopened in a corridor, or how long a problem takes to reach them after the person responsible first knew about it. Those three behaviours are what our team development work is aimed at.

Trust and psychological safety overlap and are worth keeping separate. Trust is about whether I can rely on you. Psychological safety is about whether this group will punish me for speaking up. Our piece on psychological safety in high-performing teams covers the second in detail.

Tool 1, a written team working agreement

A working agreement is a single page the team writes together, setting out how they have agreed to behave with each other. Variants of it circulate under names like a team charter or a team canvas, and several free templates are available. The template matters far less than the conversation that fills it in.

What goes on the page

Keep it to the things that cause friction. What counts as urgent and how we say so. How quickly we reply to each other and what a reasonable expectation is out of hours. How we disagree in a meeting. What we do when somebody is going to miss a deadline. Who we tell, and how early.

Six to eight agreements is the working limit. A list of twenty is a list nobody reads, and a page that includes a value like integrity has stopped being useful because nobody can tell whether they have broken it.

How to run the session

Ninety minutes with the whole team in one room, facilitated by someone who will push past the first polite answer. Start each item with a real recent example of the friction, then agree the behaviour. The examples are what make it stick, because everybody remembers the incident.

Write it in the team's own words on the day. An agreement that comes back from HR a fortnight later in corporate language will be quietly ignored.

Keeping it alive

Put it on the wall or at the top of the team's shared space, and review it every quarter with two questions: which of these are we doing and which one do we need to change. A working agreement nobody has revisited in a year has usually stopped being used. Our piece on team building training covers how this fits into a wider programme.

Tool 2, a visible commitment log

Most trust in a team is lost through forgotten commitments. Somebody says they will look into it, means it and is overtaken by the week. Three of those and the team learns that a verbal commitment from that person is a maybe.

What to record

Every agreed action, with a named owner and a date, in one place everybody can see. One line each. The point of writing it down is that it removes the argument about what was agreed, which is where the resentment usually starts.

Reviewing it at the top of the meeting

Spend the first five minutes of every team meeting on the log. Done, not done, moved with a reason. Doing this in front of everyone is what makes it work, because a private reminder from the manager carries none of the same weight.

Handling a missed commitment

Ask what got in the way and agree a new date. Treat the missed action as information about workload or priorities. If the same person misses three in a row, that is a separate conversation about capacity, held privately, and it is a conversation the log has made unavoidable in a useful way.

Tool 3, a shared language for behavioural style

A large share of what teams call a trust problem is a style problem that has been misread. A fast, direct colleague who skips the context is experienced as dismissive. A careful colleague who asks for the detail before committing is experienced as obstructive. Both readings are wrong and both damage trust. The underlying differences are set out in our guide to the four DiSC personality types.

Giving the team a common vocabulary

We use Everything DiSC profiling for this. Each person gets a profile, the team spends a facilitated session on what the shape of the group explains and afterwards people have words for a difference they had been reading as a character flaw.

The test of whether it worked is whether anyone is still using the language three months later. When it works, a complaint about somebody being difficult turns into a specific statement about what that person needs before they can commit.

The check-in round

Open team meetings with sixty seconds each on how the week is going. It feels awkward for the first three or four weeks and then becomes the most useful part of the meeting, because it surfaces the thing somebody would not have raised as an agenda item.

How leaders respond when somebody speaks up

The whole team calibrates on what happens the first time somebody challenges the leader or admits a mistake. Listening without interrupting, thanking the person out loud and asking a question instead of defending are three behaviours that cost nothing and are watched closely by everybody in the room.

Building trust in distributed and hybrid teams

Everything above applies to a distributed or remote team and each tool has to work harder, because the incidental contact that used to build trust for free has gone.

What remote working removes

In an office, people build trust through accumulated small evidence: overhearing a colleague handle a difficult call well, noticing that somebody stayed late. Remote, all of that disappears and colleagues are judged almost entirely on responsiveness and on what they say in scheduled meetings. That is a thin basis for trust.

Making informal contact deliberate

The contact that happened by accident now has to be scheduled. A short recurring call with no agenda, pairs rotated every few weeks, is the cheapest intervention we know of. Teams resist it for about a month and then protect it.

Writing more of it down

Distributed teams need the working agreement and the commitment log more than co-located ones, because there is no corridor in which to clear up an ambiguity. Decisions written down with the reasoning attached also prevent the suspicion that things are being settled in a side conversation.

What we see when a team works on trust

BAT product development team, thirty-four people who had never worked together

BAT assembled a new product development R&D team of thirty-four people from seventeen countries in Southampton. Everyone was technically capable and nobody knew how anybody else worked. In some of the cultures represented, challenging a manager was normal. In others it was avoided. The result was politeness in place of the challenge the work required.

We ran two days with the whole group: DiSC profiling for a shared language, psychological safety work so people could speak without weighing up the hierarchy first and communication and personal brand sessions. Meetings became livelier within weeks and began running without the leader present. Over two years the team's product category grew by more than 250% with no increase in headcount. Their category lead, Chris Keller, said that where everyone had previously stayed in their own lane, helping each other became instinctive. The BAT case study has the detail.

What we see in the room

This is observation from our own delivery, with no measured figures behind it. Teams almost always describe their trust problem as a communication problem, and when you ask for an example it is usually a specific unresolved incident from eight months ago that two people are still carrying.

The other consistent pattern is that the leader is more trusted than they think and less predictable than they think. People generally believe the intent. What they cannot forecast is which version of their manager will be in the room on a bad Tuesday.

Where trust-building efforts fail

Three patterns account for most of the wasted effort.

The first is the away day with nothing attached. A group spends a good day together, agrees to be more open and returns to the same meetings, the same measures and the same manager. The goodwill is genuine and it has nothing to hold on to, so it lasts about six weeks.

The second is a leader asking for candour they then punish. Somebody takes the invitation at face value, raises something uncomfortable and is corrected in front of the group or quietly sidelined. Everyone else updates instantly, and the next invitation to speak freely gets a polite silence.

The third is trying to build trust while ignoring a live grievance. Where one person has been let down badly and it has never been addressed, exercises about communication styles will feel insulting. Deal with the specific incident first, then do the general work.

Questions people ask about building trust in teams

How do you build trust in a team?

Agree how you will behave with each other and write it down, record every commitment with an owner and a date and give the team a shared language for behavioural style so difference stops being read as bad intent. Then keep doing all three when the team is busy, which is the hard part.

What are the best tools for building trust in a team?

A one-page working agreement written by the team, a visible commitment log reviewed at the start of every meeting and a behavioural profiling tool that gives people a common vocabulary. These are cheap, they need no software and their value comes entirely from being used consistently.

Which tools help improve trust in leadership across distributed teams?

The same three, plus a scheduled replacement for the informal contact that remote working removes. A short recurring call with rotating pairs and no agenda does most of that job. Distributed teams also depend more heavily on written decisions with the reasoning attached.

What is a team trust canvas?

It is a one-page template a team completes together, usually covering purpose, roles, values, needs and the behaviours the group commits to. Several versions are freely available online. It is one way of producing a working agreement, and the conversation in the room is what creates the value.

How long does it take to build trust in a team?

The structures can be in place within a fortnight. The behaviour change takes around a quarter, because trust is built from repetition and people need to see a leader hold to something when it costs them. Rebuilding trust after a serious breach takes considerably longer.

What destroys trust in a team fastest?

A leader saying one thing in a meeting and something different one to one. Everything else is slower. Broken commitments erode trust gradually, but inconsistency between what a leader says publicly and privately removes it in a single conversation, because it tells people the public version was managed.

How do you rebuild trust after it has been broken?

Name the specific thing that happened without softening it, say what you got wrong and then be predictable for several months. Apologies without a change in behaviour make it worse, because they add a second broken promise to the first one.

Is trust the same as psychological safety?

They are related and distinct. Trust is about whether one person can rely on another. Psychological safety is about whether a group will penalise you for speaking up, admitting error or disagreeing. A team can have strong one-to-one trust and still be unsafe to challenge as a group.

How do you measure trust in a team?

Use observable proxies. How long a problem takes to reach the manager after somebody first knew about it. How often decisions are reopened after the meeting. How many people speak in a typical team meeting. An anonymous pulse survey repeated each quarter works as well, provided somebody acts on it.

Can trust be built in a one-day workshop?

A workshop can start it and cannot finish it. A well-run day surfaces what has gone unsaid and produces agreements the team believes in. What determines whether any of it survives is the manager's behaviour over the following three months.

What role does psychological safety research play here?

Google's Project Aristotle study of its own teams identified psychological safety as the strongest differentiator of effective teams, which is why it appears in almost every team development programme now. The practical consequence for a leader is that how they respond the first time somebody challenges them matters more than anything they say about wanting challenge.