Building Trust: The Small Stuff Counts

Everyone wants to be trusted. Fewer people want to do the little things that earn it.

The truth is you don't build trust by asking for it or by thinking you deserve it because of a title. You build it in moments so small you're tempted to think they don't count: keeping a promise, admitting a mistake, or listening when someone tells you something you don't want to hear.

Your team watches those moments. They also watch what you do after you let them down. An explanation matters. What you do next gives them a reason to trust you again.

I used to think being reliable meant always saying yes. It didn't. Every yes becomes a commitment, and when you can't follow through, even the best intentions won't keep trust intact.

So, what's one thing you do that makes people hesitate to trust you?

Hold that thought. Here's where trust actually gets built, one small moment at a time.

Graphic generated with OpenAI, with creative direction by David Hofstetter.

Listen before you change things

When you step into a new leadership role, there's a pull to prove you belong. Fast. So you start fixing things in week one.

Your team doesn't see a confident new leader. They see someone with an agenda, who didn't ask, and who doesn't know what they're about to break.

Here's what's really going on. Your team knows things you don't: what works, what's broken, and who's quietly holding the whole thing together with tape and good intentions.

If you came up from that team, it gets trickier. You know things too. But your version of the story came from one seat. They saw it from several, and their version may not match yours.

And here's the hard part. Some of what you know needs fixing may not line up with what your new bosses want, or what they can support right now. You can see the problem from both sides, and you can't always fix it. Welcome to the middle.

So before you change anything, learn the team. Their strengths. Their frustrations. How work actually gets done, not how the org chart says it does.

Start with one question: "What are we doing well, and what's one thing you wish we would improve?"

Then stop talking. The silence will feel like an eternity. Let it.

When you hear something you disagree with, resist the urge to defend. Try this instead: "Help me see this from your perspective."

Write down what you hear. Some of it you'll be able to fix. Some of it you won't, at least not yet. Your team will be watching how you handle both.

Make commitments people can count on

Let's start with the hard one. Sometimes the most trustworthy thing you can say is no, even to something you know needs to happen.

A vague "I'll look into it" feels easier in the moment. It isn't. It's a quiet yes you can't deliver, and we already know where that road goes. Think back to when you were a kid and asked your parents for something, and they said, ‘We’ll see.’ You knew exactly what that meant. 

What builds trust instead is being straight with people. Tell them what you heard, what you can't do right now, and why, as far as you're able to share. Then tell them what you can do.

Something like:  "You're right that this needs fixing. I can't make it happen this quarter, and here's why. What I can do is bring it to my boss and tell you what I hear back by the end of the month."

Two things to watch here.

Don't throw your boss under the bus. "Corporate won't let me" might get you a cheap laugh, but it also tells your team you'll talk about them the same way when they're not in the room.

And don't promise to fight a battle you won't fight. If you say you'll raise it, raise it. Then report back, even when the answer is still no.

This is where my old "always say yes" habit finally made sense to me. Being reliable isn't about saying yes more. It's about saying yes to fewer things, doing them, and being honest about the rest.

Small beats big. A small promise you keep does more than a big one you don't. Nobody remembers your ambitious plan. They remember that you followed up on Tuesday like you said you would.

If you want a quick win, go back to the list from your listening conversations. Pick one frustration the team named and fix it. That proves you heard them, which is worth more than the fix itself.

And when something slips (it will), say so early, before anyone has to chase you: "I said Friday. It's going to be Tuesday, and here's why." Late and honest beats on-time silence that turns into a surprise.

Coaching question: What's one small promise you can make and keep this week?

Make your decisions (and your reactions) predictable

People can live with decisions they don't love. What they struggle with are decisions that seem to come out of nowhere.

So explain the why. Not a dissertation, just enough context that the decision makes sense from where they sit.

And say what you don't know. Pretending to have every answer costs you more than admitting a gap. Try: "Here's what I know, here's what I don't yet, and here's when I'll know more."

Apply the same standards to everyone. If the rules bend for your favorites, the whole team notices. Including your favorites.

Now the part most leaders miss. Your team is always running a quiet test: What happens when I bring them bad news?

React badly once, and you've taught them to stop telling you things. Then you're the last to know, which is a lousy place to lead from.

When the bad news lands, take a breath and try: "Thanks for telling me. What else do I need to know?"

Coaching question: When someone brings you bad news, what does your face do before your mouth catches up?

Show your team you'll stand behind them

Your team needs to know you're in their corner, especially when they're not in the room.

Give credit, and make it specific. "Great job, team" is nice. "Maria caught the error that would have cost us the client" builds trust.

Clear the road. Part of your job is removing whatever slows them down, even when it's annoying, political, or both.

Go to bat for them. Remember that issue you promised to raise with your boss? This is where you do it. Ask for the time, resources, or support they need, even when you might hear no. Then close the loop with your team either way.

When things go wrong, own your part first: "That one's on me. Here's what I'll do differently."

Standing behind people doesn't mean letting everything slide. Hold people accountable, fairly and directly, not behind their backs: "Here's what I expected, here's what happened. Walk me through it."

Coaching question: Would your team believe you'd defend them in a room they're not in?

When you break trust, make the repair visible

You will break trust at some point. Everyone does. The leaders people stick with aren't the ones who never mess up. They're the ones who clean it up well.

Here's what a real repair looks like:

1. Name the commitment you missed. Be specific. "Sorry if anything fell through the cracks" doesn't count.

2. Acknowledge the impact, and listen. Let the person tell you what it cost them, even if it's uncomfortable to hear.

3. Say what you'll do to fix it, and by when.

4. Follow through, consistently. Trust comes back slower than it left. That's not a punishment. That's just how it works.

If you want it in one breath: "I missed this. Here's the impact, the fix, and when I'll confirm it's resolved."

Coaching question: Is there a repair you've been putting off because the conversation feels awkward?


Your move this week

So back to the question I asked at the start: What's one thing you do that makes people hesitate to trust you?

Maybe it's the promises you forget. Maybe it's the "I'll look into it" that never gets looked into. Maybe it's what your face does when someone brings you bad news. Maybe it's the yes you already know you can't keep.

Pick one. Not five. One small behavior you'll change this week.

Trust doesn't show up in the big speech. It shows up in the small stuff, over and over, until your team stops wondering whether they can count on you.

Next
Next

Training Is Learning It. Coaching Is Living It.