Unleashing Leaders Logo

The Translator’s Advantage in Leading Big Change

3/16/2026

There’s a kind of leadership skill that doesn’t show up on a résumé.

It looks like patience, but it’s sharper than that.
It sounds like clarity, but it’s built from friction.
And most of the time, it starts long before someone ever gets a title.

This story begins with a kid standing beside two adults in everyday places, at a grocery store checkout, at a bank counter, at a gas station, helping both sides understand each other.

Not because the adults weren’t capable.
Because the world wasn’t designed for the way they communicated.

So, the kid translated.

And somewhere between “What did they say?” and “Here’s what they mean,” a lifelong leadership ethic formed:

Mutual understanding matters. Respect matters. Communication isn’t a soft skill; it’s the difference between outcomes and breakdowns.

When the stakes are high, misunderstanding gets expensive

Fast-forward to adult life, and the same translator mindset shows up in a very different arena: large-scale operations where a single misstep can ripple across massive systems.

In work like this, the goal isn’t just keeping the machine running. It’s transforming it, while it’s running, without breaking what people rely on.

That’s the tightrope so many leaders walk, whether they’re leading a team of five or a workforce of hundreds:

  • keeping the day-to-day stable
  • while implementing new initiatives
  • across multiple functions
  • with competing priorities
  • and different “languages” inside the same organization

Because every function speaks differently.

Operations. Technology. Legal. Finance. Communications. Program teams.

Each group has its own terminology, its own traditions, its own assumptions, and its own blind spots. And when those groups collide, the problem is rarely a lack of intelligence.

It’s a lack of translation.

Integrative thinking: more than solving the problem in front of you

One leadership principle that emerged in this conversation was integrative thinking, the discipline of keeping the big-picture goal in view while working through real-world constraints.

Not just asking, “Can we implement this?”
But asking, “Will this actually work for the people who need it to work?”

A perfect example came from rolling out a new service benefit by welcoming a group of providers who weren’t used to navigating complex enrollment and payment systems.

The technical build could be flawless.

But the real risk wasn’t the technology.

The real risk was assuming that if the system existed, people would automatically know how to use it.

Because for many new providers, enrolling, billing, and getting paid wasn’t just “one more step.” It was an entirely new world. Without outreach, training, clear support, and thoughtful engagement with the communities around them, the benefit wouldn’t land the way it was intended to.

That’s integrative thinking in action:

Seeing the full end-to-end experience, provider to member to system, and building change management around real human behavior, not just process maps.

“Non-custodial” and the power of language

Sometimes translation isn’t about complicated systems.

Sometimes it’s about one phrase.

In another transformation effort, a simple but loaded label was called out: a term used to describe a parent in a support process.

On paper, it was “technical.”
In real life, it carried judgment.

And judgment changes behavior.

When leaders choose more neutral, respectful language, language that better reflects real situations, they don’t just improve communication. They improve outcomes because people feel seen as human, not as categories.

This wasn’t wordsmithing for optics. The motivation was deeper:

Respect for the people being served.

And when respect becomes a leadership standard, it tends to spread. It changes the tone of meetings. It changes the way decisions are made. It changes the way conflict is handled.

The hidden leadership superpower: solving for the right problem

Another thread ran through the entire discussion: most teams don’t struggle because they can’t solve problems.

They struggle because they solve the wrong one first.

A defect. A breakdown. A complaint. A missed metric.

It’s easy to jump to action, especially in cultures that reward speed.

But the better move is slower at the start and faster in the finish:

  • Get the right people in the room (including people with divergent viewpoints).
  • Ask enough questions to find what’s underneath the symptom.
  • Bring in the technical knowledge and the lived experience of the people impacted at the end of the process.
  • Keep pushing: “Is this the real issue, or just what’s loudest?”

This approach isn’t occasional. It’s daily.

And it’s paired with something many leaders say they want but rarely practice:

Issue-spotting before something becomes a crisis.
Watching for early warning signs. Paying attention to details that seem small—until they aren’t.

Healthy conflict stays healthy when you stop making it personal

At scale, disagreements aren’t rare, but constant.

But there’s a difference between conflict that improves decisions and conflict that fractures teams.

One moment in the conversation described a high-stakes transition decision where there was real debate about readiness and risk. People disagreed earnestly. The tension was real.

What kept it productive?

A shared rule:

Stay focused on issues and problem-solving, not people and personality.

Not opinion. Not ego. Not “who’s right.”

Instead:

  • What does the data say?
  • What are the risks?
  • What are the consequences?
  • What path reduces risk while protecting the people who rely on the service?

That kind of conflict doesn’t just lead to better decisions. It builds trust, because people learn the room is safe for truth, not just agreement.

Influence without credit: planting seeds that grow into buy-in

Here’s a leadership lesson that feels simple until you try it:

Sometimes your best idea shouldn’t stay “your idea.”

Early in a career, it’s tempting to push hard for recognition, because credibility matters.

But a mentor offered a different approach: build support by planting seeds. Share the concept. Invite others to shape it. Let the idea come back around as something the team believes in, sometimes even as something they think they created.

And instead of feeling like a loss, that becomes a win:

Because the outcome matters more than credit.

And when people feel ownership, implementation accelerates.

Collaboration is the real transformation challenge

Toward the end of the conversation, the focus shifted to a reality many organizations are facing: major waves of workforce change and the risk of losing institutional knowledge.

That raises a bigger question than “How do we document what we know?”

It raises the question:

What is our collaboration model going forward?

Because collaboration has barriers:

  • teams resist ideas that didn’t originate “here”
  • knowledge gets hoarded because it feels like power
  • information is hidden in people, not shared in systems
  • complex knowledge doesn’t transfer easily across silos

So the work becomes intentional:

Break silos. Build shared domains of knowledge. Partner earlier and more consistently across functions. Create ways of learning that outlast any single leader.

Which leads to one of the strongest closing ideas from the conversation:

An unleashed leader isn’t just confident enough to lead.

They’re confident enough to build many leaders.
To share the mantle.
To unify people around vision, alignment, and purpose—so leadership multiplies., 

And that’s how you go far.

If this resonates, be sure to listen to the full episode on The Unleashing Leaders Podcast.

Ready to unleash your leadership?
Discover how our large-scale Strategic Planning and Operational Management Services can transform your organization, dive into practical growth with Unleashing Leaders University and get inspired by real stories on The Unleashing Leaders Podcast.