Trust is someone else’s decision, taken in their head, about a specific thing they would be risking. And nobody announces it. There’s no moment where a colleague tells you they’ve quietly downgraded you, and no moment where they tell you they’ve done the opposite either.
So how are you supposed to know where you stand?
The usual answer is to ask, and it’s a poor one. “Do you trust me?” puts the other person on the spot, and the honest answer is expensive for them, particularly if you’re more senior. It also asks for a summary of something that was never one number. And it assumes they’ve reached a conclusion they could report, when most of the time confidence has been adjusted rather than decided.
There’s a better answer, and it needs no conversation at all. Trust isn’t silent. It shows up in behaviour, continuously, in two forms you can learn to read. Neither can be managed by the other person, because in both cases they don’t know they’re telling you anything.
Signal one: how readily people say yes
Confidence and hesitation move in opposite directions. The more confidence someone has in you, the less they hesitate. The less confidence, the more they do.
That makes confidence observable, because hesitation is observable. The trick is knowing that the information sits in the readiness, not in the answer.
Watch for the pause before the agreement. The yes with a rider attached. “Let me just run it past someone first.” A sudden preference for having it in writing when there was never a need before. Easy agreement on one thing, and noticeable care about another.
None of those are refusals. If you’re only listening for no, you’ll hear nothing but yes and conclude everything is fine.
That last one matters most, and I’ll come back to it, because it’s where this stops being about how much someone trusts you and starts being about what they trust you with.
I should be clear about the status of this. It’s my own observation, formed over years of watching how people respond to being asked for things. It isn’t a research finding, and I’d rather you tested it against your own experience than took it on my say-so.
Signal two: what people bring you
This is the direction almost nobody thinks to look in, and it’s the more reliable of the two.
What somebody approaches you for tells you what they trust you with. When a colleague says “can you just…”, a judgement has already been made. They wouldn’t be bringing it to you otherwise. The ask is the evidence.
One ask tells you very little. The movement over months tells you a great deal. A simple task, then something harder a fortnight later. Bigger things, or more of them. And the shift that matters most, from can you do this, to how would you do this, to what do you think we should do. Execution, then judgement, then strategy. Each step is somebody deciding you’re good for more than they previously thought.
There’s a quieter version that’s easy to miss. “Can you help me with a problem?” is someone deciding you’re safe to be uncertain in front of. That’s often a bigger concession than being handed a task.
Then ask the harder half. What isn’t landing on your table? What do people handle without coming to you, or without you finding out until afterwards? That’s a reading too, and usually a more honest one.
The filter that makes this usable
One test applies before any of it counts. Did they have to come to you?
If someone brings you something because your position requires it, because a process says so, or because there’s nobody else who could deal with it, that’s compliance. The behaviour looks identical. There’s no information in it. What you’re reading is the authority attached to your role, not anyone’s confidence in you.
This is where senior people fool themselves. Plenty of things land on your table because of where you sit. Take those as evidence and you’ll conclude you’re trusted with a great deal more than you are.
But when somebody comes to you as an individual, having had the option not to, they’re showing you in their actions that this is something they’re willing to risk with you. That is trust, in the definition’s own terms.
So the test is one question. Did they have to come to me? If yes, discard it. If no, it counts.
Both signals at once, on the same person
My first work after leaving the prison service was facilitating training in the Middle East, a region I had never worked in.
On the facilitation, there was no hesitancy at all. They were satisfied I could do it and they let me run with it.
On how effective I’d be in a culture I didn’t know, they were much less sure, and we did a lot of in-depth work on cultural awareness before I started.
High on one thing and low on another, at the same time, about the same person. Nobody said any of it out loud. And both readings were correct.
That’s what people mean when they say trust is contextual, and it’s why “do they trust me?” is close to unanswerable. It was never one thing. Someone can trust you with a deadline and not with bad news.
Signals are evidence, not verdicts
People bring you things for reasons that have nothing to do with confidence. Convenience. Politics. You being the only one at your desk on a Friday afternoon. And the absence of a signal is not the absence of trust; sometimes there’s simply nothing to bring.
Read them the way you’d read any evidence. In the pattern, over time, alongside everything else you know about the person and the situation. A single ask proves nothing. A direction of travel over three months is worth taking seriously.
Using it deliberately
If you want to work with this rather than just notice it, there’s a sequence.
Start with what you want to be trusted with. Be specific — “more responsibility” isn’t a thing anyone can hand you.
Then name what you’d actually see if it were working. This is the step people skip, and it’s the one that does the work. An L&D client of mine wanted a seat at the table. Asked what she would see if she had it, she said people would ring her for advice rather than handing her the task. That single named behaviour turned a vague ambition into something observable, and gave her evidence to notice while the perception was still shifting.
Then look at what lands on your table now, and strip out anything they had no choice about.
The gap between what you’d see and what you’re seeing is the trust gap. It’s specific, it belongs to one relationship, and it points at a behaviour rather than a quality. Which leaves the only question that was ever going to matter: how do you demonstrate the thing, often enough that they start trusting you with it?
The better question
“Do they trust me?” was never going to be answered. There’s no single verdict, nobody was going to deliver it, and it would have told you little if they had.
The signals answer a better question. You don’t find out whether you’re trusted. You find out what you’re trusted with — and that is something you can do something about.
