Not trusting the team sounds like an observation. It is usually a verdict nobody has tested.
"I don't trust my team with this" arrives in the room the way a weather report arrives, read off the outside world rather than offered as a claim. The executive saying it does not present it as a judgment. It comes across as a finding: the team is not there yet, the work cannot be handed over, and control has to stay in one place or a mistake follows. Said this way, the sentence closes the conversation instead of opening it, because it is spoken as something already proven rather than something worth checking. Most people in the room accept it on those terms too, because the anxiety behind it is genuine, and genuine anxiety tends to borrow credibility for whatever reason it gives.
Ask how many times the team has actually gotten this wrong in the last year, and the sentence usually runs out of evidence. The executive reaches for one example, and it is old, involves someone no longer on the team, or never repeated since; sometimes the example is not even from this team, but carried over from a job before it. The distrust rests on an impression rather than a record, and an impression that has already settled does not go back and check itself — it does not go looking for new evidence, because the verdict was reached a long time ago.
A different picture from the manager who will not let go This is not the same picture as the manager who still does the work. There, the task never leaves the desk, because letting it go feels like a personal loss. Here, the task is usually assigned: a name goes on it, a date gets set, and for a while it can even look genuinely handed over. But the verdict was reached before the name was written: this will not go well. The task is external. The judgment is not, and it does not move with the task, because it was never really about the task in the first place.
The standard is not read off the team. It is read off the manager's own past.
Ask what the distrust is actually measured against, and it is almost never the team member as they are today. It is measured against the executive's own best version of themselves: years into the same work, past its early mistakes, close to never getting it wrong. That version sits so clearly in the executive's memory that it feels like an honest benchmark, when no team member, and no executive, ever resembled it in their first year.
A comparison that is unfair in three places - The team member is doing this for the first time; the executive is remembering their own last attempt, not their first one. - The team member's mistake is visible, because it is new; the executive's old mistakes have already been forgotten, corrected, absorbed into the record. - The team member is judged without the support the executive quietly had — a manager, a mentor, someone quietly covering for them more than once, which the executive has since forgotten was ever there.
Distrust here is not information about the team. It is a distortion in the executive's own memory. A standard that measures today's beginner against yesterday's expert will always return the same verdict, and the verdict does not move even as the team genuinely improves.
Change the standard and the verdict changes with it The same team member usually compares well against the executive's own first year, back when the tools, the feedback, and the examples on hand were thinner than what the team has now. Change the standard and the verdict changes with it, which is the clearest sign that the distrust was never really about the team. Saying this comparison out loud once is often enough for an executive to notice their own standard for the first time.
The difference shows up in what happens after the mistake, not in how large it was.
There is one way to tell whether distrust is really about competence or about control: watch what happens when something goes wrong. A competence concern teaches after the mistake: what went wrong gets discussed, something changes for next time, and the work stays where it is. A control concern takes the work back quietly, and it does not leave again; the return is rarely announced, it just shows up the next time that piece of work needs doing and someone else's name is no longer on it.
The first is a competence judgment, and competence judgments change over time. The second is a search for reassurance, and no amount of performance satisfies it, because what is being sought was never a better team. It was a calmer executive. In the second case the team can perform as well as it likes and the executive's anxiety will not move, because the anxiety was never really tracking the team's performance.
The test itself is simple Watch who repairs the next mistake. If the team repairs it and the executive only discusses the outcome, the concern is genuinely about competence, and it closes on its own. If the executive repairs it and the team stops being handed that kind of work again, the concern is about control, and it feeds itself, growing a little with each repetition because the team has quietly stopped offering.
A competence concern teaches after the mistake. A control concern takes the work back after it.
The cost of not trusting the team lands on the manager's own capacity, not the team's.
An executive who withholds trust believes they are reducing risk. What they are actually reducing is the team's room to take one on, and what they are increasing is their own workload. Every task pulled back becomes a permanent line on the executive's own desk, and the lines add up until there is no time left for the work only the executive can do. A year later this executive is doing work two levels below their own, and can rarely explain how it happened.
The cost accumulates on both sides at once: the executive sinks further into operational work while the team offers less and less. Proposing something and having it taken away costs more than never proposing it at all, and after a few rounds the team learns that waiting is safer than offering.
A loop that appears to prove itself right The loop looks like it confirms the original distrust, because the team genuinely starts initiating less. That is not evidence the team was never capable. It is what the loop itself produces: the same team behaves differently once work that is handed over is allowed to stay handed over, and it usually only takes one full try to see the difference.
From the room
The first move with an executive who arrives saying "I can't trust my team" is not to argue with the sentence. It is to ask for the evidence underneath it: when, on what, and what actually happened. Most often the example is old, or it is one incident that has been carried into every decision since, sometimes involving someone who has since left the team entirely.
The room's job is not reassurance. It is rewriting the standard. Comparing today's team to yesterday's beginner instead of yesterday's expert, and watching where the correction goes the next time something breaks, usually makes the source of the distrust visible within a few sessions.
Telling the difference between distrust that is about competence and distrust that is about control usually starts with one question in the first conversation: how the last handed-over task ended, and who picked it up once it broke.