You Say Trust. Your Meetings Say Something Else.

Every executive I talk to says they want a high-trust team.

I believe them. I don't think anyone is lying when they say it. But then I watch them run a hard meeting, the kind with real stakes and a decision that has to actually get made, and I see something completely different than what they told me they wanted.

That gap is the most honest thing in the entire organization. It just usually goes unexamined, because nobody's watching for it, and the people in the room are too busy managing the moment to notice what the moment is revealing.

Trust is easy to claim and hard to run

Ask a leadership team if they value trust and every hand goes up. It's one of those words that's basically impossible to disagree with in the abstract, right up there with communication and alignment. Nobody's ever said, out loud, in a strategy session, "actually, I'd prefer we trust each other less."

But trust isn't a value you hold. It's a behavior you demonstrate, specifically in the moments where demonstrating it costs you something. And the moments that cost the most are exactly the ones I'm talking about, the hard meetings, the ones with a deadline attached and a wrong answer that's expensive.

That's where I actually learn what a team believes about trust, not from what they tell me in a discovery call, but from what I watch happen the first time real pressure walks into the room.

What I actually see in a hard meeting

Here's the pattern, and I've watched it enough times now to know it isn't a coincidence.

The most senior person in the room speaks first, and often speaks longest. Not because they have the most useful information, but because hierarchy makes the first word feel safe for them and risky for everyone else. Once that opinion is on the table, something shifts. Fewer people push back. Questions get softer. What could have been a real disagreement turns into a series of careful nods and a couple of gently phrased alternatives that quietly die before they're fully said out loud.

Somebody in the room almost always sees the actual problem. I've asked them afterward, privately, and they'll tell me exactly what was wrong with the plan, sometimes in more detail and with more clarity than anyone offered in the meeting itself. When I ask why they didn't say it in the room, the answer is almost never "I didn't think of it." It's some version of "it wasn't my place," or "I didn't want to be the one who slowed things down," or "I figured someone more senior would say something if it really mattered."

That's not a high-trust team. That's a team that has learned, through repeated experience, exactly how much honesty the room can actually hold, and it's less than they claim.

The tell isn't what people say. It's what they protect.

If you want to know what a team actually trusts, don't listen to their stated values. Watch what they protect under pressure.

Some people protect the relationship, and go quiet rather than risk friction. Some protect their own standing, and hedge their opinion so it can't be used against them later. Some protect the timeline, and let a flawed plan move forward because stopping it would mean admitting the team is further behind than anyone wants to say out loud. Every one of those instincts is completely rational. None of them require bad intent. But none of them are trust in action either, and a team can say "we trust each other" in every offsite for a decade while every hard meeting quietly proves otherwise.

The uncomfortable part is that this gap is usually invisible to the leader running the meeting. They experience the meeting as smooth. Everyone agreed, decisions got made, the room felt calm. What they don't see is the version of the conversation that didn't happen, the disagreement that got swallowed, the concern that got softened into something forgettable. A quiet room isn't the same thing as an honest one, and mistaking one for the other is how good executive teams end up genuinely surprised when a decision they were "aligned on" falls apart three months later.

What closes the gap

This is the part that matters, because naming the gap without offering a way through it isn't useful. It's just diagnosis.

Closing the gap between stated trust and demonstrated trust doesn't happen through a values statement or a better mission deck. It happens by putting a team in a real situation, with real stakes, where the cost of honesty is actually tested, and where people get to watch what happens when someone tells the truth under pressure and nothing bad occurs to them for it.

That's the entire mechanism behind the work I do now. I don't run trust exercises. I create moments where trust either shows up or it doesn't, and the team gets to see the difference in real time. When you put an executive team in front of a horse, that animal has no idea who's the CEO and no interest in anyone's title. It responds only to what's true about the person in front of it right now. Leaders who talk over people in meetings often find the horse won't cooperate with that same energy. Leaders who defer and soften discover the horse won't move without more clarity than they're used to giving. It's not a metaphor I'm imposing on the experience. It's what actually happens, every time, and it's the fastest and most honest way I've found to show a team the real distance between what they say about trust and what they practice.

Once a leader sees that gap clearly, named specifically instead of gestured at vaguely, they can't unsee it back at the office. They start noticing the meeting where they spoke first and shut the room down without meaning to. They start asking the quiet person directly instead of waiting for volunteered honesty. That's what closes the gap. Not another values conversation, but a real one, followed by the discipline to keep having it.

Every executive I talk to wants a high-trust team. The ones who actually get one are the ones willing to find out, honestly and sometimes uncomfortably, what their team currently trusts more than they'd like to admit.

Ready to Build a High-Trust Leadership Team?

High-performing teams aren't defined by what they say about trust. They're defined by how they communicate, make decisions, and respond when the stakes are high.

If you're ready to uncover the patterns shaping your team's performance and build stronger trust where it matters most, we'd love to help.

Reach out today to learn how a Strides Leadership retreat can help your executive team strengthen communication, improve decision-making, and lead with greater confidence.

I Quit Selling "Team Building." Here's What I Sell Now.

For years, I got asked to run "team building days." And for years, I said yes.

I stopped answering to that phrase. Not because I got precious about language, but because I finally understood what the phrase was actually promising, and I couldn't keep selling it in good conscience.

Here's why.

What "team building" actually means to most people

Say "team building day" out loud to any executive and watch their face. You'll see it. A small, polite flinch. Because everyone has sat through one. Trust falls. Forced icebreakers. An escape room that felt more like a Tuesday afternoon than a leadership intervention. A facilitator with a clipboard asking the group to share something "no one knows about you." A nice lunch. A group photo. Everyone drives home a little more relaxed and absolutely nothing different about how they lead on Monday.

That's not an exaggeration. That's the actual, average experience, and executives know it, which is exactly why they show up skeptical before you've said a word.

The phrase "team building" carries a built-in assumption, and it's the wrong one. It assumes the problem is that people don't like each other enough. That if we can just get the team to bond, to have some shared fun, to loosen up a little, the working relationships will improve.

But that was almost never the actual problem on the teams I worked with. These were accomplished, likable, respectful people. They weren't cold to each other. They were guarded with each other, in specific and costly ways that no amount of shared laughter was going to touch.

The moment I stopped saying yes

The turning point wasn't dramatic. It was a debrief conversation with a CEO a few days after a retreat his team genuinely enjoyed. He thanked me, meant it, and then said something that stuck with me for a long time.

"That was a great day. But I don't think anything's actually different."

He wasn't being harsh. He was being honest, and he was right. His team had a nice time together. They did not leave with a clearer read on why decisions kept stalling in their Monday meetings, why two of his executives quietly avoided disagreeing with each other, or why the newest member of the team still hadn't found her voice in the room six months in. Those problems were still sitting exactly where we'd left them, just now with better memories attached.

That conversation forced me to be honest with myself. I had been selling an experience. What these leaders actually needed was a mirror.

The real problem was never bonding. It was honesty under pressure.

Once I stopped trying to make teams like each other more and started paying attention to how they actually behaved when something was on the line, a different picture came into focus.

The teams struggling weren't struggling with warmth. They were struggling with truth. Specifically, the kind of truth that's hard to say out loud in a room full of accomplished peers when you're the one who disagrees, or the one who's unsure, or the one who has to name that a plan everyone else likes has a real problem in it.

That's not a bonding gap. That's a trust gap, and trust gaps don't close over shared nachos and a scavenger hunt. They close when people watch each other be honest in a moment that actually mattered, and see that honesty didn't cost them anything.

So I stopped designing for fun and started designing for exposure. Not the uncomfortable kind, the useful kind. Situations honest enough that a team's real patterns show up in real time, in front of each other, where they can finally be named instead of quietly managed around for another six months.

What I build instead

This is where the horses come in, and I'll be direct about why. A horse has never once cared about anyone's title. It doesn't respond to confidence performed for an audience. It responds to what's actually true about a person in that moment, their tension, their hesitation, the gap between what they're saying and what their body is doing.

Put a leadership team in front of that, and something team building never could produce happens almost immediately. The patterns that quietly run the boardroom show up in the open. Who takes over. Who defers without saying so. Who gets impatient and starts pushing instead of leading. Who checks out the second things get uncertain. Nobody has to confess anything. It's just visible, plainly, to everyone in the group at the same time.

That's the difference. Team building tries to manufacture connection through shared activity. What I build now tries to manufacture clarity through shared reality. One produces a nice memory. The other produces a moment a team can actually reference back at work, the way you'd reference any hard truth that changed how you operate.

I've had executives tell me, months later, that they still catch themselves mid-meeting thinking about the exact moment a horse wouldn't move until they stopped trying to control it, and how that's exactly what they'd been doing to their VP of Sales for a year. That's not a takeaway from a fun day. That's a takeaway that changes behavior.

Why the word matters

I know it might sound like I'm arguing over language. I'm not. I'm arguing over what leaders are promised versus what they actually need.

"Team building" promises a better feeling. What most executive teams are actually missing is a better process for being honest with each other when it's hard and when it counts. Those are not the same product, and conflating them is how so many leadership teams end up sitting through their third offsite in five years, still unable to explain why decisions take too long or why the same conversation keeps happening without ever resolving.

I don't sell a nice day anymore. I sell the moment a leadership team sees itself clearly, some of it flattering and some of it not, and leaves knowing exactly what to do differently because of it.

That's not team building. It's something closer to the truth. And it's the only thing I've found that actually sticks.

Ready for More Than Team Building?

If your leadership team doesn't need another activity but needs clearer communication, stronger trust, and better decision-making under pressure, we'd love to start the conversation.

Reach out today to learn how a horse-guided leadership retreat can help your team see itself more clearly and lead more effectively.

The Moment Talented Teams Stop Moving

I've watched a lot of teams make decisions under pressure. Boardrooms, offsites, the quiet tension of a call that everyone knew mattered more than the agenda let on. And after enough of these rooms, a pattern started to repeat itself so consistently that I stopped writing it off as coincidence.

The teams with the most talent in the room are not always the teams that move.

That should surprise us more than it does. These are smart people. Accomplished, credentialed, used to solving hard problems for a living. They've read the books, sat through the trainings, built careers on making good calls. And yet the moment the stakes actually rise, something in the room seizes up. Conversations get careful. Opinions get vague. Everyone starts speaking in probabilities instead of positions. The meeting that was supposed to produce a decision produces another meeting instead.

If intelligence were the answer, this wouldn't happen. So it isn't intelligence. It's something else, and it's worth naming.

The freeze isn't a thinking problem

Here's what I've come to believe after watching this play out again and again, including in some very unexpected settings. The freeze doesn't happen because people can't figure out the right answer. It happens because they've stopped trusting that the room can hold their answer well.

Think about what actually happens inside a high-stakes conversation. Someone has a strong opinion, but they hedge it, because they're not sure how it will land with the person two seats down. Someone else sees a problem forming, but stays quiet, because raising it feels like criticizing a colleague's work in front of the whole team. A third person genuinely doesn't know the answer, but performs confidence anyway, because admitting uncertainty at this level feels like a liability instead of an honest data point.

None of this is cowardice. It's self-protection, and self-protection is a completely rational response to a room where honesty hasn't been proven safe yet.

The tragedy is that this happens most on the executive teams that can least afford it. The higher people rise, the more they have to lose by being wrong out loud, and the more practiced they become at looking composed instead of being direct. Composure starts to substitute for clarity. And a room full of composed, careful, unreadable people cannot make a fast decision together, no matter how sharp any one of them is individually.

What actually separates the teams that move

The teams that move under pressure aren't the ones with the smartest individuals. They're the ones who already know, before the pressure ever shows up, exactly how the group behaves when things get hard.

They know who goes quiet when they disagree, and they've learned to ask that person directly instead of waiting for volunteered honesty. They know which two people will default to conflict avoidance and let a bad plan slide rather than name what's wrong with it. They know their own habit, whether it's talking too much to fill silence, or going silent to avoid looking unsure, or needing to be the one who's right.

That kind of self-knowledge and team-knowledge doesn't get built in a quarterly offsite icebreaker. It gets built by putting a team in a situation honest enough that those patterns show up in real time, where they can actually be seen and named, rather than in the middle of a live decision where the cost of seeing them clearly is suddenly very high.

This is, frankly, one of the most useful things I've learned from an unlikely teacher.

What horses taught me about the freeze

I spend a lot of my time around horses, and if you've never worked closely with one, here's something that will sound strange until you've felt it. A horse does not respond to your title, your track record, or how convincing you sound. It responds to what's actually true about your state in that moment, your tension, your hesitation, your incongruence between what you're saying and what your body is doing.

I have watched extremely accomplished, decisive executives walk up to a horse and completely stall. Not because the task was hard. Leading an animal a few steps forward is not hard. They stalled because for the first time in a long time, they were in a situation where their usual tools, their title, their certainty, their ability to talk their way to a conclusion, simply didn't work. The horse wasn't buying it. And in that gap, you could watch the exact same freeze that happens in a high-stakes boardroom moment, except now it was visible, physical, and impossible to explain away.

That's the value in it. Not the horse itself, but the mirror. Most leadership breakdowns are invisible until the cost has already been paid. This makes them visible while the cost is still low, in a setting where a stalled decision just means the horse takes a few extra minutes, not a missed quarter or a fractured executive team.

Once a leader sees their own freeze clearly, named and specific rather than vague and defensive, they can't unsee it. And more importantly, they start recognizing it in the room the next time it happens at work.

The real work isn't about being smarter

Nobody on a high-performing executive team needs to get smarter. They need to trust the room enough to say the true thing before it's the safe thing, and they need enough self-awareness to catch themselves in the moment they start protecting their image instead of protecting the decision.

That's not a skill you build by discussing it in the abstract. It's a skill you build by practicing it somewhere real, somewhere the stakes are low enough to be honest and high enough to matter, until it becomes reflex instead of effort.

The teams that move when it counts aren't the ones who never freeze. They're the ones who've already learned what their freeze looks like, and who trust each other enough to call it out before it costs them anything.

That's the work. And it starts long before the moment you actually need it.

Ready to See How Your Team Responds Under Pressure?

The patterns that slow down decision-making rarely appear in a conference room until the stakes are high. Our horse-guided leadership experiences create a space where those patterns become visible, allowing your team to build trust, communicate more directly, and make better decisions together.

Schedule a discovery call to learn how Strides Leadership can design a leadership experience for your executive team.