Trust Isn’t Default: How Product Managers Build Influence With Teams

The Pushback I Didn’t Expect

When I joined that startup, I thought I’d walk in with instant influence. I had the title, I had experience, and I was brought in to lead change, not just in what we built, but in how we built it.

This was the company’s very first task force. The squad that was supposed to deliver a win big enough to replicate across the rapidly growing org. No pressure, right?

Two weeks in, I suggested a change in how the team worked. I don’t even remember the exact thing, but I’ll never forget the reaction. They shut me down. Hard. A blunt “That’s not your role.” And then silence—the kind that echoes louder than words.

It wasn’t personal. It was their world, their rhythms. I had walked in with assumptions. They had been shipping longer than I had even been in the building.

Why Trust Is Slow to Earn

Here’s the truth: I wasn’t the one pushing for change. Management was. I was just the face of it. And when you’re the face of change, the resistance will hit you first.

I knew that moment well. Back in the Air Force, when I was an F-16 flight instructor, I’d get that exact look from pilots who had been flying longer than I had been alive. The look that said: “Really, sweety? You think you’re going to teach me?”

So I wasn’t offended. But I was surprised. I didn’t expect it in such a young startup, with such a promising team.

That day I learned something: Change is never easy. Not for new people, not for veterans. And definitely not when the “why” is unclear.

How Trust Really Gets Built

Here’s the thing about trust: You can’t demand it. You can’t shortcut it. Force won’t work. It takes patience, subtlety, and humility.

So I backed off. I listened. I watched. I looked for their real pain, the friction, the frustration, the cracks in the system. And a few weeks later, in a retrospective, the team themselves suggested the very change I had pushed earlier. This time, it wasn’t me forcing it. It was them deciding. And because it was theirs, it stuck.

Even though I was still new in the org and technically in my 30-60-90 days, trust began to form in small ways. Not because we were already delivering big results, but because I started working with them differently. I pulled design and engineering into the conversations, I treated the team as partners, and I built personal relationships. That consistency started to create reliability, even before the big wins came.

That’s how trust started to build. Not with a big speech. Not with a “PM knows best” attitude. But by stepping back, listening, and letting them come with me on the journey.

We ended up building some of the best products I have ever worked on. That team, the one that shut me down so strongly at first, became one of the most amazing teams of my career.

10 Lessons on Building Trust as a Product Manager

1. Stay humble, there’s always more to learn.

2. Appreciate your team and make sure they know it.

3. Don’t look down on anyone, you’ll get the same look back.

4. Lead with vulnerability. Admit mistakes. Be open to being questioned.

5. Take the team with you. Teach them the “why,” not just the “what.”

6. Lead by example. Do the things you expect from them.

7. Empower and delegate. Show trust even before you feel it fully.

8. Build relationships beyond Jira boards, especially when it’s not easy.

9. Celebrate small wins, loudly. Give shoutouts.

10. Be patient. Look for that first small win, it creates momentum.

Practical Tools to Strengthen Trust

If you want to put these lessons into practice, a few tools can help you think of things:

• Stakeholder Mapping - map out everyone who touches your product, not just your immediate team. It helps you see where trust gaps might appear and who to build relationships with early.

• Influence Mapping - beyond titles, notice who really shapes decisions in your org. Influence often lives outside the org chart. Knowing this helps you invest in the right relationships.

• First 90 Days Plan - use your 30-60-90 days wisely. Spend the first phase listening, the second shaping, the third acting. Don’t rush to the rescue too early.

• Team Health Checks - regularly ask simple retro questions like: “What’s one thing slowing us down?” or “What’s one thing we’re proud of?” They surface pain points and wins, while showing you’re listening.

• The Trust Equation - a simple reminder: Trust = (Credibility + Reliability + Intimacy) ÷ Self-interest. It’s not enough to be competent. You also need to be consistent, human, and focused on the team, not just yourself.

  
  

Trust isn’t default. It’s your quiet superpower as a product manager. Build it carefully, and it will carry you further than any process.

When the door shut… I found my window