The Designer as a Translator

One of the strangest things about being a designer is that people rarely come to you with the problem they actually have.

They come with symptoms.

“We need a new homepage.”

“The product feels confusing.”

“The brand needs to feel more premium.”

“Our users aren't converting.”

“We need something that pops.”

That last one is always interesting.

Sometimes the request is exactly what it sounds like. Most of the time, it isn't.

Behind a request for a new screen, there might be a broken product strategy.

Behind a request for a new identity, there might be a company that no longer knows who it is.

Behind “make it simpler” there might be five stakeholders who haven't agreed on what matters most.

So a big part of the work isn't designing what people ask for.

It's understanding what they're actually trying to solve.

Everyone Is Speaking a Different Language

A product leader might be thinking about adoption. Marketing is thinking about perception. Sales needs something easier to explain. Engineering is thinking about what can actually be built without setting the building on fire. Leadership is thinking about growth. Users, meanwhile, are just trying to get something done.

Everyone is looking at the same thing.

But they're seeing a different problem.

And they're all describing it in their own language.

This is where the designer becomes something between a translator and a therapist.

Not the kind of therapist who tells you that everything will be okay.

The kind who sits there quietly until you accidentally explain the real problem yourself.

Finding Their Thing

Good stakeholder management isn't about keeping everyone happy.

That would be impossible. And probably a terrible use of everyone's time.

It's about helping each person find their thing.

The thing they're worried about.

The thing they're trying to protect.

The thing they haven't been able to articulate clearly yet.

Different concerns.

Different languages.

Often, the same underlying problem.

The work is to get underneath the argument without making people feel like they're being cross-examined.

Design as the Common Language

This is one of the reasons I love design. Design can hold several realities at the same time.

A good concept can give strategy a shape.

A visual system can make an abstract idea visible.

An experience can turn a business goal into something a person can actually use.

A prototype can end a conversation that a two-hour meeting couldn't.

Because sometimes people don't disagree about the idea.

They disagree because they're imagining different versions of it.

Design gives those versions a body. And once something becomes visible, people can finally react to the same thing.

That's when the real conversation begins.

Translation Is Not Decoration

I think designers sometimes get positioned as the people who make things look good after everyone else has finished thinking.

That's a misunderstanding of the role.

Translation is not decoration.

To translate well, you have to understand both languages.

You have to understand the business problem and the human problem.

The conceptual intention and the technical reality.

What the brand wants to promise and what the product can actually deliver.

Then you have to find a form that can hold all of it without collapsing.

That's why design can operate conceptually, visually, and experientially at the same time.

We don't just make things understandable.

We make understanding usable.

Going Below the Request

The best design conversations I've had usually begin when we stop asking:

What do you want?

And start asking:

What is happening here?

What's not working?

For whom?

Why now?

What are we afraid of losing?

What would success actually look like?

These questions can feel slower at the beginning.

But they usually save a lot of time later.

Because the first solution is often a reaction.

The real solution requires a little more digging.

And yes, occasionally some emotional archaeology.

Somewhere Between Therapist and Translator

I don't think the designer's job is to have all the answers.

That's another strange expectation.

Our job is often to create enough clarity for the right answer to emerge.

To listen carefully. To notice contradictions. To translate competing needs. To make the invisible visible. And then, eventually, to turn all of that into something.

A concept.

A system.

A screen.

A product.

An experience.

Something people can finally use, understand, and respond to.

Maybe that's the real craft.

Not making a beautiful thing out of a vague brief.

But sitting in the middle of a room full of different people, different fears, different goals, and different versions of reality

and helping them realize that, somewhere underneath all the noise,

they might have been trying to solve the same thing all along.