Building Trust at Work After Everything Falls Apart: 4 Real Scenarios Leaders Face

Power distance becomes most visible after something goes wrong.

A stressful team event that everyone’s still processing. A new manager who brings completely different values. Processes that change overnight without warning. Or leadership announcing a “culture shift” that makes people quietly roll their eyes.

These are the moments when trust either gets rebuilt intentionally — or it gets replaced with compliance, silence, and people just going through the motions.

Here’s how to actually rebuild trust in four scenarios I see leaders struggling with, with practical actions that reduce power distance instead of making it worse.

1. Rebuilding Trust After a Stressful Team Event

The scenario: A project crashed. A deadline got missed publicly. Conflict played out in front of everyone. Or a restructuring happened and people felt exposed and blamed.

What usually goes wrong: Leaders try to “move on” as quickly as possible without really acknowledging what happened. Silence becomes the default strategy. “Let’s just focus on the next quarter.”

Meanwhile, power distance grows because people learn a very clear lesson: speaking up about what went wrong isn’t safe here.

How you actually rebuild trust:

Name what happened without being defensive

Trust starts when you’re willing to say out loud:

“That was a difficult moment for this team, and I want to acknowledge the impact it had on all of us.”

Don’t offer explanations or justifications, but recognition that something hard happened and people felt it.

I worked with a leader whose team went through a brutal product launch where everything that could go wrong did. Three months later, people were still tense in meetings. When we finally created space to talk about it, the first thing people said was: “Thank you for naming it. We thought we were supposed to pretend it didn’t happen.”

Separate accountability from blame

Instead of asking “Who caused this?” which immediately makes people defensive, ask, “What conditions made this outcome possible?”

This reframe is important. You’re examining systems, not hunting for scapegoats. People can actually be honest about what went wrong when they’re not worried about being the person who gets blamed.

Create structured space for people to speak

Not a big emotional forum where everyone vents for two hours. That usually makes things worse. But structured listening that feels contained:

  • Small group reflections with clear questions
  • Anonymous input channels with visible follow-up (this part is critical — people need to see their input actually matters)
  • One-on-one check-ins where you ask the same question to everyone: “What did this change for you?”

The thing that actually signals trust: Share what you heard, what’s going to change because of it, and what won’t change — and be clear about why.

Trust gets built when people see their words actually shape decisions. When they speak up and nothing changes and nobody explains why, they stop speaking up.

2. A New Manager Trying to Reconnect After Values Misalignment

The scenario: A new manager joins a team with strong existing norms. Their leadership style, how they communicate, or their core values feel misaligned with what the team is used to. People start disengaging.

What usually goes wrong: The new manager tries to establish authority quickly:

  • “This is how I work.”
  • “In my last role, we did it this way.”
  • “Here’s what we’re changing.”

Power distance spikes immediately. Trust drops. The team starts doing the minimum required while quietly resisting everything.

I’ve seen this play out so many times. A high-performing team suddenly becomes average because the new leader didn’t take time to understand what made them high-performing in the first place.

How you actually rebuild trust:

Start by learning, not leading

The managers who build trust fastest are the ones who ask before they decide:

  • “What makes this team proud of its work?”
  • “What’s been hard under previous leadership?”
  • “What should I absolutely not change quickly?”

One manager I coached joined a team that had been burned by their previous leader. Instead of coming in with a plan, she spent her first month just listening. She held 30-minute conversations with each team member. She sat in on their workflows without changing anything. She asked what they wanted to protect.

By the time she started making changes, people trusted her because she’d demonstrated she cared about understanding them first.

Acknowledge the gap openly

There’s something powerful about saying:

“I know my style may feel different from what you’re used to, and I don’t want to assume it works here. I want us to figure out together what needs to stay and what might need to shift.”

This lowers defensiveness on both sides. You’re not pretending the difference doesn’t exist. You’re naming it and making it safe to talk about.

Co-create the non-negotiables

Don’t impose all your standards. Work together to clarify:

  • What values are genuinely fixed (and why they matter)
  • What practices are flexible and open to negotiation
  • What success actually looks like for this specific team

The thing that actually signals trust: Adopt one team practice you didn’t create — and tell them why you’re keeping it.

“I know you’ve been doing weekly demo days, and I wasn’t sure about them at first. But I’ve seen how they help you stay aligned and celebrate small wins. We’re keeping them.”

Trust grows when authority is willing to adapt.

3. A New Manager Changing Processes

The scenario: New systems roll out. New workflows get implemented. New metrics start tracking things people didn’t used to track. The goal is efficiency, but morale is dropping.

What usually goes wrong: Change gets framed as pure logic:

  • “This is more efficient.”
  • “This is industry best practice.”
  • “The data shows this works better.”

The team experiences all of this as control. As their judgment being questioned. As someone who doesn’t understand their work deciding how they should do it.

Leave a Comment