Trust doesn't break. It erodes — and nobody tells you that part. By the time you notice, it's already gone.
My team didn't stop trusting me in a single moment. There was no blow-up, no resignation, no dramatic confrontation I could point to afterwards and say "that's when it started." If you'd watched us from the outside, you'd have said we were performing exactly as a high-functioning team should. Targets were being hit. Stakeholders were aligned. Meetings ran on time.
I had strong proximity to the executive leadership team, and decisions were moving fast. Everything looked like success.
It wasn't. Something had shifted, and I missed it — because I was reading the wrong signal.
This is the mistake I want to save you from: mistaking speed for alignment. Mistaking silence for consensus. Mistaking a quiet room for a safe one.
At first, the shift showed up in ways that were easy to misread as progress. Meetings became more efficient. Decisions landed faster. There was less friction, less debate, less challenge. Conversations felt cleaner, more simplified — the kind of thing you'd put in a performance review as evidence of a maturing team.
I told myself the story most leaders tell themselves in that moment: this is what alignment looks like.
It wasn't alignment. It was hesitation wearing alignment's clothes.
The moment it became undeniable wasn't dramatic — it was quiet, which is exactly what made it so confronting. I asked a question in a team session, the kind that should have triggered real discussion: disagreement, competing views, someone pushing back on the framing.
Instead, I got silence. Then a few safe answers. Then quick agreement. Then we moved on.
After the meeting, someone I trusted pulled me aside and said the sentence that reorganised everything I thought I knew about my own leadership: "People aren't pushing back because you're too close to the exec team."
That was the moment it clicked. Not because it was surprising — because it explained everything I'd been seeing and not understanding. I had believed my proximity to senior leadership was an asset for my team. I thought it created clarity, alignment, speed. What I hadn't considered was the other side of that equation: to them, it created risk.
If they disagreed with me, what did that signal upward? If they challenged a view in the room, would it read as misalignment with the executive team — not just with me? Would it touch how they were perceived, or even their progression?
No one said any of this out loud. They didn't need to. The behaviour told the story on its own, in a language every team speaks fluently and no leader is trained to read: caution.
That's how trust actually erodes — not through conflict, but through caution. Silence replaces honesty. Agreement replaces thinking. And if you're not paying close attention as a leader, caution can look exactly like high performance. That's what makes it dangerous — it doesn't look like a problem. It looks like a win.
This experience changed how I think about trust at a structural level. It's not just about creating psychological safety in the abstract, motivational-poster sense. It's about reducing perceived risk — the specific, calculated risk an individual runs when they disagree with you in front of other people who might report back, might remember, might factor it into a promotion conversation eighteen months later.
Psychological safety is the outcome. Perceived risk is the mechanism. If you only manage the outcome — running a warm, friendly team culture — while ignoring the mechanism, you'll keep getting silence dressed up as harmony. I know because that's exactly what I did.
The proximity paradox: how closeness to power quietly becomes a filter
Access to senior leadership is a resource to be used for the team, we're taught — faster decisions, clearer priorities, better air cover. All true, and also where most leadership advice gets it backwards. Every resource has a shadow cost, and proximity's shadow cost is that it turns you, without your consent, into a filter.
Your team stops seeing you as a peer they can argue with and starts seeing you as a conduit to people who can affect their careers. That reclassification happens silently, in their heads, and you will not be invited to the conversation where it happens. You'll only see the downstream effect: faster meetings, fewer objections, a suspicious lack of mess in a function that used to be messy in healthy ways.
The paradox is that the more visibly connected you are to power, the more deliberately you have to work to seem safe to disagree with. Most leaders do the opposite — they lean into the proximity, using it as a shortcut to compliance, because compliance is faster and feels like respect. It isn't respect. It's risk management, performed by your team, at your expense, without you ever knowing it's happening.
How I now read a room for hidden hesitation
- Speed as a warning sign, not a virtue: When a contentious decision gets made faster than usual, I don't congratulate the team on alignment. I ask what got skipped to make it fast.
- Count the dissent, not the agreement: I track how many genuine objections come up in a given month, not how many decisions land smoothly. A month with zero objections is a red flag, not a good month.
- Ask who's not in the room mentally: I watch for the person who used to argue and now just nods. That behavioural change is worth more diagnostic information than any survey.
- Separate the message from the messenger's fear: Before I ask for feedback on my own proximity to execs, I explicitly name the risk out loud first — so no one has to be the one who says it.
- Test agreement by asking for the counter-case: When a room agrees too quickly, I ask someone directly to argue the opposite position for two minutes. What comes back tells me whether the agreement was real or defensive.
None of this is complicated. It's uncomfortable, which is a different thing. Uncomplicated and uncomfortable is usually where the real leadership work lives — the technical stuff is rarely what separates teams that stay honest from teams that quietly stop.
So ask yourself, honestly: are the people around you aligned with you — or are they managing you? Those two states can look identical from the front of the room. They feel completely different from where your team is sitting.
What I actually changed, not just what I believed
Realising the problem is the easy part. Rebuilding candour once a team has learned that caution pays better than honesty is slower, and it doesn't respond to a single announcement or a single all-hands speech about "speaking up." I tried that first, because it's the cheapest fix available and every leader reaches for it first. It didn't work. Nobody changed their behaviour because I said the word "safe" in a meeting. Why would they — the risk I was asking them to ignore was real, not imagined, and a sentence doesn't cancel out a career calculation.
What actually moved the needle was smaller and slower than I wanted it to be. I started asking for the counter-argument by name, in the room, before a decision closed — not "any objections?" which is a question designed to be answered with silence, but "someone tell me why this is wrong" directed at a specific person. The first few times, what came back was thin. Polite hedging dressed up as pushback. That told me the risk calculation hadn't shifted yet, and I needed evidence, not reassurance, to shift it. So I built the evidence deliberately. When someone did push back — genuinely, not performatively — I made a point of changing the decision when they were right, visibly, and saying why in front of the group. Not "thanks for that input" followed by the same outcome anyway. An actual change, attributed to them, witnessed by the room. That's the only currency that resets a risk calculation: proof that the cost of disagreeing was lower than they'd priced it, repeated enough times that it stopped being a story and started being a pattern they could rely on.
It took months, not weeks. Trust that erodes slowly rebuilds slowly — there's no shortcut I found, and I looked for one, because I wanted this fixed faster than it was willing to be fixed. The team member who'd stopped arguing was the last one to come back, and when they finally did push back on something in a meeting again, I remember consciously not reacting the way I wanted to — not thanking them too warmly, not making it a moment, just engaging with the substance of what they'd said like it was a normal Tuesday. Because making it a moment would have told everyone watching that dissent was still notable, still remarkable, still something you'd get noticed for. The goal was for it to become boring again. Boring is what safe actually looks like in practice.
The distinction I now lead by
If there's one thing I'd want another leader to take from this, it's a distinction I didn't have language for at the time and now can't unsee: agreement is not the same as alignment, and speed is not the same as trust. Agreement is what you get when people have calculated that disagreement costs more than it's worth. Alignment is what you get when people have genuinely reasoned their way to the same conclusion you have — and would tell you if they hadn't.
The two are indistinguishable in a meeting. They are completely different in a crisis. A team that's merely agreeing with you will follow you off a cliff in silence, because objecting was never safe to begin with. A team that's actually aligned with you will tell you the cliff is coming, even if you don't want to hear it — because they've learned that telling you costs them nothing.
I don't think proximity to power is something leaders should avoid. That's not the lesson here, and I'd be lying if I said I've stepped back from executive relationships since this happened — I haven't, and I wouldn't advise it. The lesson is narrower and harder: proximity is a liability you have to actively manage, not a credential you get to enjoy passively. If you're closely connected to the people who shape your team's careers, the burden is on you to make disagreement demonstrably safe, repeatedly, in ways your team can actually see and test — not just to declare an open-door policy and assume the door reads as open from the other side.
The test I use now is simple, and I'd encourage any leader reading this to run it on their own team this week: pick the last significant decision your team agreed on quickly, and ask yourself honestly whether anyone in that room had a reason — career, reputation, access — to keep an objection to themselves. If you can't rule that out, you don't have alignment yet. You have a very well-managed version of silence, and it will hold right up until the moment it matters most.