The Cost of Translation

For years I assumed creating multiple versions of the same idea was simply part of the job.

A leadership discussion required one explanation. Engineers needed a different level of detail. Designers cared about different constraints than operations partners. Finance teams often looked at the same initiative through an entirely different lens. The work itself wasn't changing, but the conversation surrounding it constantly was.

At some point I realized I was spending as much time translating ideas as developing them.

Most organizations don't have an official role called "translator," yet nearly every successful initiative depends on someone performing that function. Product managers, architects, consultants, design leaders, program managers, founders, and engineering leaders often find themselves in the position of helping different groups understand the same problem from different perspectives.

The work is surprisingly difficult because the challenge is rarely communication alone.

Most people imagine translation as simplifying information. In practice, it often involves preserving complexity while making it accessible to different audiences. A technical team may be focused on system dependencies. Leadership may be focused on investment decisions. Operations may be concerned about adoption and support. Each perspective is valid. Each group is looking at the same situation from a different altitude.

The translator's job is not to convince everyone to think the same way. It's to help people understand why reasonable people can arrive at different conclusions while looking at the same problem.

That distinction matters.

Many organizational challenges that appear to be disagreements are actually perspective gaps. Teams aren't necessarily arguing about the solution. They're often operating from different assumptions, incentives, responsibilities, and constraints. Until those differences become visible, conversations can feel far more difficult than they need to be.

What's interesting is that organizations rarely account for this work.

Roadmaps capture features. Project plans capture milestones. Budgets capture investments. Yet an enormous amount of progress depends on the invisible effort required to create shared understanding. Without it, decisions slow down, alignment becomes fragile, and teams begin solving different versions of what they believe is the same problem.

I've started to think of translation as a form of organizational infrastructure.

Most people don't think about infrastructure when it's working well. Roads, electrical systems, and networks tend to disappear into the background until something breaks. Translation often works the same way. When shared understanding exists, teams move quickly. When it doesn't, friction appears everywhere.

The challenge is that translation carries a cost.

Not financial cost. Cognitive cost.

The person doing the translating is often holding multiple models of the same problem simultaneously. They understand how leadership views the situation, how technical teams view it, how customers experience it, and how operational realities influence it. Moving between those perspectives becomes second nature over time, but it requires energy.

A lot of energy.

Because the work is largely invisible, the effort can be easy to overlook. Organizations benefit from it every day without necessarily recognizing how much coordination, interpretation, and context-building is happening beneath the surface.

The irony is that some of the most valuable contributors in an organization may spend relatively little time generating new ideas and an enormous amount of time helping ideas survive the journey between groups.

The more complex an organization becomes, the more important that function appears to be.

Perhaps that's why I've become increasingly convinced that many organizational challenges are not fundamentally technology problems, process problems, or even people problems.

They are translation problems.

Not because people lack intelligence or good intentions, but because understanding rarely emerges automatically. Someone usually has to help build the bridge.

Most of the time, that bridge is invisible.

Until it isn't.