When a new manager walks in, the team is watching. Not always consciously, but they are. They want to know: does this person know what they’re doing? Will they have our backs? Can we count on what they say?
Nobody answers those questions with a title. Trust is earned through a lot of small moments that mostly go unremarked. And it’s built on more fronts than most people expect.
You need to know something they respect
New managers often worry about not being the most technical person in the room. Especially if they come from an IC role and now manage people with deeper expertise in areas they’ve never touched.
Here’s what I’ve noticed: your team doesn’t need you to be the best at their job. They need you to bring something to the table that they can look up to.
For some people on my team, that was customer service knowledge: how to de-escalate a difficult client interaction, how to explain something complex to someone who has no technical background. For others, it was data analysis. For others, understanding how the business actually worked.
The specific knowledge matters less than the fact that you have some. If your team can’t identify what you bring beyond the manager title, they’ll quietly wonder how you got there. That question, even unspoken, makes trust harder to build.
The Golden story: different strengths, same team
When I was a coordinator at my previous company, I had two peers I often compared myself to: another coordinator and our manager. Both were what we called Goldens. Like the dog breed. Everyone loved them, they got along with everyone effortlessly, they seemed to move through every interaction without any friction.
I was not a Golden.
The interpersonal part of leadership, the natural warmth and instant rapport, came harder for me. I worked at it. And even when I did, I didn’t get the same results they got.
But I had something they didn’t: I was much more comfortable with data analysis. Digging into numbers, building reports, finding patterns.
I started using that comparison openly with my team. Not as a complaint, but as a point. The N3 on your team might have a technical investigation depth you’ll never match. You might have an empathy and communication ability they’ve been trying to develop for years. Neither is more important. Both matter.
When you’re honest about where you’re strong and where you’re not, people start to see you as a real person rather than a job title. And that matters for trust.
If you’re thinking about what it actually takes to step into that role, I wrote more about that in Advice for First-Time Managers.
Defend in public, coach in private
Your team needs to know you’re on their side. Not blindly, but reliably.
What that looks like in practice: if someone on my team makes a mistake and gets called out publicly, or gets treated harshly by someone else, I step in. Even if internally I think they made a real error. I’ll address the situation, push back on the tone or the public nature of it, and make clear that this person doesn’t deserve to be treated that way regardless of what happened.
Then, later, in private: we talk about the mistake. What happened, what they could do differently, how to avoid it next time.
The sequence matters. If I let someone get torn apart in front of others and only come in after with feedback, I’ve already signaled that I won’t protect them when it counts.
The same applies to difficult customer situations. Sometimes a customer explodes at a support agent. Sometimes there’s a real service failure behind that frustration. Sometimes there isn’t. Either way, my job is to step in, take over the interaction, and protect my agent from absorbing that intensity. And then, after, sit with them and look at what could have been done differently.
Defending your team doesn’t mean protecting them from accountability. It means making sure they know you’ve got them while they’re learning.
The small promises nobody talks about
There’s a category of trust that breaks very quietly, and it’s almost always promises.
Not big promises. The small ones. “I’ll talk to the other team about this.” “I’ll get you on that project.” “I’ll follow up on that process change.” Things said in a 1:1 or a team meeting, half in passing.
If you say it and don’t do it, people notice. They might not say anything. But they file it away. Over time, those unfulfilled small promises stack up into a single conclusion: this person says things they don’t mean.
I don’t think most managers are being dishonest when this happens. They’re just overcommitted and forgetful. But intent doesn’t really matter to someone who’s been waiting three months for the follow-up you said would happen soon.
The fix is boring: only promise what you’ll actually do. Track what you say you’ll do. That’s it.
Vulnerability doesn’t have a formula
Someone asked me recently where the line is between vulnerability that builds trust and vulnerability that makes people nervous.
Honest answer: I don’t know.
I’ve shared doubts in team meetings and felt the energy shift in a good way. I’ve admitted I didn’t have the answer to something and had people step up to fill that gap, which made the team stronger. I’ve compared myself openly to the Goldens I mentioned, named my own limitations, and had people respond by sharing theirs.
But I can’t give you a rule for when to do it. I do it by feel. What I can say is that I’ve never regretted being honest about not knowing something. I’ve occasionally regretted performing confidence I didn’t have.
The good news is that the bar is lower than you think. Your team isn’t looking for a perfect manager. They’re looking for a real one.
Friendship helps. It’s not required.
If you can build a genuine personal connection with people on your team, that tends to reinforce trust. Shared context, a real relationship that makes difficult conversations easier because there’s a foundation underneath them.
But it’s not always possible. And in some cases, it might not even be desirable. The closer the personal relationship, the harder certain management decisions become.
What I’ve found is that trust doesn’t require friendship. It requires consistency, reliability, and the things I’ve described above. You can have a professional, warm, respectful working relationship with someone without ever grabbing coffee outside the office. And that’s enough.
Trust is cumulative
It doesn’t arrive in a moment. It builds through a lot of small moments that mostly go unremarked.
The thing I remind myself is that distrust is also cumulative. Every broken promise, every moment where I didn’t step up, every time I performed confidence I didn’t have, those stack up too.
I’m still figuring a lot of this out. But thinking seriously about how trust actually works, rather than assuming it comes with the title, is already most of the way there.