For Leaders & Managers Blog · November 2026 ~7 min read

Seven Signs You Are Leading a Low-Trust Team

You can usually see a low-trust team before you can measure one. The signs are behavioral, they repeat every week, and most of them get filed under something more flattering. Here are seven, and the question I would ask first.

By Jeff Morris, "The High Trust Guy" DreamSmart Behavioral Solutions
Editorial illustration of a team at work with small teal warning markers placed where work is quietly re-checked

What does a low-trust team look like?

A low-trust team is recognizable before it is measurable, and the earliest signs are behavioral rather than emotional. Seven of them show up in almost every team I have been called into: finished work gets quietly re-checked, decisions get re-argued after the meeting ends, bad news reaches you late and from the wrong person, every call routes through you, the paper trail gets longer, credit gets negotiated, and people hold a meeting before the meeting.

None of those are moods. Each one is an observable behavior you can count in a single ordinary week, which is what makes them useful to a leader who has a suspicion and no vocabulary for it. They are indicators, not predictions. A team can show three of them and recover inside a quarter, and a team can show one of them in a form so entrenched that it takes a year.

The reason to take them seriously is that intrateam trust and team performance track each other closely. De Jong, Dirks and Gillespie pooled 112 independent studies covering 7,763 teams and found an above-average relationship between the two, one that held up after controlling for prior performance and for trust in the leader (Journal of Applied Psychology, 2016). Trust is not the soft half of the job. It is the part that sets what the rest of the job costs.

The seven signs, one at a time

Each sign below comes with what it looks like in an ordinary week and the thing it usually gets mistaken for.

  • Finished work gets re-checked. An engineer rewrites a section a colleague already wrote. A manager re-runs numbers an analyst already ran. Usually mistaken for high standards, and it is often defended that way, but a team with high standards agrees on the standard once. A low-trust team pays for the same work twice.
  • Decisions get re-argued after the meeting. The room agrees on Tuesday. By Thursday two people have reopened it in a side thread and a third is waiting to see which way it lands. Usually mistaken for healthy debate. Real debate happens in front of the people who can change the decision.
  • Bad news arrives late, and from the wrong person. You hear about the slipped date from a peer in another function rather than from the person holding it, and you hear it a week after they knew. Usually mistaken for an isolated communication breakdown. It is almost never isolated.
  • Every decision routes through you. People who are perfectly capable of deciding bring it to you anyway, and the ones who could unblock each other directly wait for you to broker it. Usually mistaken for a headcount or seniority problem. Adding a person to a team that does not trust its own peers just adds another route through you.
  • The written trail grows. Longer CC lists, recap emails after conversations that used to just be conversations, screenshots kept. Usually mistaken for good documentation discipline. Documentation written to inform a team looks different from documentation written to protect its author, and people can tell the two apart instantly.
  • Credit gets negotiated. Who presents to the executive, whose name goes on the deck, who gets mentioned in the all-hands. When credit feels scarce, people start managing it. Usually mistaken for ambition, or for a personality clash between two individuals.
  • There is a meeting before the meeting. Pre-alignment calls, private soundings, a quiet check with two people before the real session. Usually mistaken for good preparation. Preparation makes a meeting shorter. Pre-alignment makes the real meeting ceremonial, because the decision already happened somewhere you were not.

The one question that tells you how serious it is

If you only get to ask one diagnostic question, ask this one. How long does it take bad news to reach me, and who does it come from?

Bad news that reaches you the same day, from the person closest to the problem, means the team is intact even if it is under strain. Bad news that reaches you a week late, from a peer, a skip-level or another department, means people are calculating the cost of telling you before they tell you. That calculation is the whole problem in miniature, and it is the first behavior I would work on.

The follow-up question is quieter and more revealing. What happened the last time somebody brought you bad news early? Most leaders have to think about it for a while, and the ones who remember the answer usually remember something they would not choose to repeat.

What low trust gets blamed on, and what usually causes it

Low trust is almost always diagnosed as a process problem first. The intake form is wrong, the tooling does not talk to itself, the team is two people short, the meeting cadence needs a redesign. Those are real complaints and they are worth fixing on their own merits. Fixing them does not move any of the seven signs.

What causes the pattern, in nearly every case I have seen, is a run of small broken commitments that nobody named at the time. Someone said they would have it Friday and it came the following Wednesday, twice. A manager promised to raise something upward and did not. A decision was announced as final and then reversed with no explanation. Individually, none of these is a firing offense. Together they teach a team to hedge, and hedging is what the seven signs are made of.

That is also why a reorganization rarely helps here. Move the same people into a new structure and the commitment history moves with them.

What to do in the first two weeks

Three moves, in this order. They are small on purpose, because a leader with a low-trust team has very little credit to spend on a large announcement.

  • Audit your own closed loops. List every commitment you personally made in the last month and mark which ones you closed, which you closed late, and which you let quietly expire. Most leaders find two or three in that third column. Close them this week, and say out loud that you are closing them late.
  • Change the bad-news rule once, in public. Tell the team what you want (early, incomplete, from the person closest to it) and then wait for the first person to test it. What you do in that moment is the only part of this they will remember.
  • Name a decision owner for every open decision. One name, written down, next to each item. Re-litigation feeds on ambiguity about who actually had the call, and most of it stops once the answer is on the page.

Two weeks is not enough to rebuild trust. It is enough to stop the bleed and to give yourself something honest to measure against.

Getting an actual number

Observation gets you a direction. It does not get you a baseline, and it does not survive a disagreement with a peer who reads the same team differently. That is what scoring is for.

In the TrustFlow™ methodology, trust is scored as twelve specific behaviors, the 12 Cs of Trust, arranged in four quadrants: Foundations (Character, Courage, Commitment), Essentials (Connection, Communication, Caring), the Work (Clarify, Collaboration, Coaching) and Results (Consistency, Competence, Closeout). Each is rated 1 to 5 by the people who work together, and the team roll-up is the Team TrustFlow Index, or TTFI, reported from 1.00 to 5.00.

There are three bands. 1.00 to 2.49 is Constrained Trust, where people actively work around each other. 2.50 to 3.74 is Developing Trust, real but uneven and prone to breaking under deadline pressure. 3.75 to 5.00 is Sustained TrustFlow, where coordination is efficient and relational friction is low. The number itself matters less than the gap between the four quadrants, which is what tells you where to start.

In my experience, a team carrying four or more of the seven signs tends to land in Developing Trust with its weakest scores in Results, the quadrant that holds Closeout. That is a specific and fixable finding. "Morale is down" is not. The full scoring method is in How to Measure Trust, or you can run the team trust score and get the baseline directly.

FAQ

What are the signs of low trust in a team?

Seven show up most often: finished work gets re-checked by somebody else, decisions get re-argued after the meeting ends, bad news reaches the leader late and from someone other than the person holding it, every decision routes through the manager, the written trail grows as people document conversations they used to simply have, credit gets negotiated, and people hold a pre-meeting before the real meeting. Each one is observable in a single normal week.

How do you know if your team trusts you?

Time the bad news. If a slipped date, a mistake or a risk reaches you the same day and from the person closest to it, the team trusts you enough to tell you. If it reaches you a week later from a peer or a skip-level, people are weighing the cost of telling you before they do it. The second useful test is what happened the last time somebody brought you bad news early.

What causes low trust on a team?

Usually a run of small broken commitments that nobody named at the time: work promised Friday that arrived Wednesday, a concern someone agreed to raise upward and did not, a decision announced as final and then reversed without explanation. None of those is serious on its own. Repeated, they teach people to hedge. Process gaps, tooling and headcount get blamed far more often than they deserve.

Can a low-trust team be fixed?

Yes, and usually without changing the people. Trust is behavioral, which means it responds to changed behavior rather than to changed structure. The fastest lever is the leader's own closed loops, because a team calibrates on the most visible person before it calibrates on anyone else. The slowest cases are the ones where a specific unrepaired breach between two people is still sitting there, unaddressed and known to everyone.

How long does it take to rebuild team trust?

There is no fixed clock, because trust rebuilds on repetition rather than on elapsed time. In practice, a leader who closes every loop for six to eight weeks will usually see the first signal, which is somebody bringing bad news early without being prompted. Re-scoring the team every four to six weeks gives you the trend, and the trend is more useful than any single number.

What is the difference between low trust and low morale?

Morale is how people feel about the work. Trust is what they do with each other regardless of how they feel. A team can have good morale and low trust: people like each other, enjoy the work, and still quietly re-check each other's output. The reverse happens too. Morale responds to recognition and workload. Trust responds to kept commitments, and only to those.

Seven signs, one question, three moves. None of it needs a program, a budget or anybody's permission, which is the point of starting here. Begin with the closed-loop audit on yourself, because the team is already keeping that score whether or not you are.

You can see it.
Now find out how far it goes.

The Team TrustFlow Index scores all twelve behaviors, so the signs you noticed come back as a number with a direction.