For a long time, I believed communication was about finding the right words.

If someone didn't understand my idea, I assumed I hadn't explained it well enough.

So I'd explain it again.
More details.
More slides.
More examples.

It rarely worked.

For a while, I blamed it on English.

It's not my first language.

I don't think in English all the time.

Sometimes I know exactly what I want to say, but translating it into words takes longer than I'd like.

By the time I've found the right sentence, the conversation has already moved on.

I still think language plays a part.

But I've realized it's not the whole story.

Communication isn't the transfer of information.

It's the recreation of thought.

Imagine you've spent six months working on a product.

You've researched users.
Explored dozens of concepts.
Rejected ideas you loved.
Built prototypes.
Questioned every decision.

By the time you're presenting it, the final concept feels obvious.

But it isn't obvious.

It's obvious because you've lived inside the problem.

The person across the table hasn't.

They see the destination.
You experienced the journey.

That's why so many presentations fail.

We present conclusions while people are still looking for the reasoning that produced them.

I noticed this most clearly during a job interview.

I kept explaining what I had designed.

The interviewer kept asking why.

Then another question.
And another.

At first, I thought he wasn't convinced by the work.

Later, I realized he wasn't evaluating the project itself.

He was trying to reconstruct how I think.

Once he understood my reasoning, the project suddenly made sense without me changing the design at all.

Nothing about the work had changed.

Only his mental model had.

That interview taught me something I'll probably carry throughout my career.

People don't just buy ideas.

They buy the thinking behind them.

As designers, we often say we're solving problems.

But we forget something.

Before we can solve a problem, we have to convince someone that it's worth solving.

A client has to approve it.
A manager has to prioritize it.
An investor has to fund it.
An engineer has to believe it's worth building.
A customer has to understand why it should exist.

A brilliant idea that never gets built is just an interesting thought.

Communication is what turns ideas into reality.

Good communication isn't about sounding intelligent.

It's about reducing uncertainty.

Every question someone asks is evidence that part of their mental model is incomplete.

When someone interrupts your explanation, they usually aren't challenging you.

They're trying to fill a missing piece.

The best communicators don't simply answer questions.

They anticipate them.

They know where confusion is likely to appear because they've learned to see their own ideas through someone else's eyes.

I've also realized that communication isn't just speaking.

It's listening for where reality diverges from your expectations.

Whenever someone misunderstands you, it's tempting to think they weren't paying attention.

Sometimes that's true.

More often, you've discovered something valuable.

You've found the exact point where your mental models stopped matching.

That's not failure.

It's feedback.

It tells you exactly where your explanation needs another bridge.

For a long time, I thought my biggest challenge was English.

Now I think it's something else.

I often don't have complete thoughts waiting to be translated.

I have fragments.
Images.
Connections.
An intuition that something is true without fully understanding why.

Sometimes my mind jumps between ideas so quickly that I forget nobody else made those same jumps.

I don't think in sentences.

I think in patterns.

Writing forces me to slow down.

To connect the dots.
To examine assumptions.
To discover what I actually believe.

I've realized that I don't always write because I have something to say.

Sometimes I write to find out what I'm trying to say.

This is probably why writing feels easier than speaking.

In conversation, I have to think, translate, organize and respond all at once.

Writing removes the time pressure.

The page is patient.

It doesn't interrupt.
It doesn't move on because I paused for five seconds looking for the right word.

Writing has become less about documenting my thoughts and more about discovering them.

Design taught me something unexpected.

The same way we prototype products, we can prototype explanations.

You say something.
Watch the reaction.
Notice the confusion.
Adjust.
Try again.

Over time, the explanation becomes clearer—not because your vocabulary improved, but because your understanding of your audience did.

Communication, like design, is iterative.

I've stopped thinking of communication as public speaking.

Or storytelling.

Or presenting.

Communication is product design.

You're designing a path through an idea.

You have to understand where someone is starting.
What assumptions they're carrying.
Where they'll get lost.
What they'll need before they're willing to move forward.

The goal isn't to impress them.

The goal is to help them arrive.

I still catch myself trying to explain what I built before explaining why it needed to exist.

But I'm learning that people rarely trust conclusions they didn't arrive at themselves.

If you want someone to believe in an idea, don't begin with the answer.

Begin with the problem.

Help them notice what you noticed.

Let them ask the same questions you asked.

Walk them through the reasoning that changed your mind.

Because communication isn't about making people hear what you think.

It's about helping them think it for themselves.