I have spent a lot of my life assuming that being understood was my responsibility.

If someone didn't understand what I was saying, I assumed I hadn't explained it well enough.

So I would try again.

Change the words. Draw the diagram. Find the data. Build the model. Trace the dependencies. Translate the technical problem into a business problem, the business problem into money, the money into risk, the risk into something somebody with authority might finally care about.

I got very good at this.

It is, in fact, a large part of what I have been paid to do. Because translation is a real kind of labor.

Organizations are full of it. We translate product value into a price someone is willing to pay. We translate a signed contract into revenue, implementation work, invoices, and eventually cash. We translate labor into customer service, sales conversations, software, shipments, or a set of closed books at the end of the month. We translate what a customer needs into product requirements, and what a product can actually do back into promises a salesperson can responsibly make.

Most of this translation becomes invisible when it works. We notice it when it doesn't—when the contract says one thing and the product does another, when Finance and Sales mean different things by the same number, when a customer's problem has to pass through three teams before it reaches someone who can act on it.

Translation isn't ancillary to the work. A surprising amount of the work is translation.

I think I have been drawn to my field partly because translation is familiar to me. Long before I was being paid to translate between systems, functions, and people, I was trying to make things legible—to explain what I could see, what I meant, what was happening underneath something that looked simpler from the outside.

I have written some version of this impulse for years. I need you to listen to me. Because I can no longer bear to go unheard. And elsewhere: I feel responsible for making the invisible visible. If it can be seen, it can be acknowledged and understood.

There is something both generous and controlling in that.

Generous, because understanding requires translation. What is obvious from one position may be completely invisible from another, and making it legible can create the possibility of recognition, care, or action.

Controlling, because hidden inside I can make this visible can be I can make you see it. Those are not the same thing.

That's not how people work.

And it's definitely not how organizations work.

Sometimes I haven't explained something well enough.

Sometimes someone sees exactly what I see and doesn't agree with me.

Sometimes they agree and don't care enough to act.

Sometimes they care and don't have the authority.

Sometimes they have the authority but acting would cost them something they aren't willing to give up.

Sometimes the system is producing exactly the outcome its incentives reward, even while everyone inside it says they want something different.

Being legible has a cost

Those are not all communication problems.

I think some of my professional disillusionment has been the repeated discovery that legibility does not guarantee action.

For a long time, I imagined a sequence:

See the thing.

Understand the thing.

Explain the thing.

Agree on the thing.

Change the thing.

A lot of my career has been discovering all the places where that sequence breaks.

Information does not automatically produce agreement. Agreement does not produce authority. Authority does not produce willingness. Willingness does not produce capacity. And none of those guarantee action.

This seems obvious when I write it down.

It did not feel obvious while I was standing in rooms thinking, maybe one more diagram.

There is also something psychologically convenient about misunderstanding.

Misunderstanding leaves me another move.

I can explain again.

I can give more context. Find a better metaphor. Make the implicit thing explicit. Ask another question.

Understanding followed by a different choice requires me to confront something much harder.

They saw it.

They understood.

And they chose differently.

There is no better slide for that.

Understanding does not require sameness

I notice this outside of work too.

There have been times when I've told myself that someone didn't understand me because the alternative was more painful. Maybe I hadn't found the right words. Maybe I needed to explain what I meant by autonomy, or care, or commitment. Maybe I needed to provide enough context that my internal logic would become obvious.

There is hope inside misunderstanding.

If the problem is translation, translation can be improved.

But eventually there is a question I have had to become more willing to ask:

What if they understand me and this is still their answer?

That question changes the available choices.

Because then my work isn't necessarily to become more understandable.

It may be to believe what I have been told.

And decide what I want to do with it.

I don't want to stop translating. Translation is one of the things I'm unusually good at. I love finding the sentence that suddenly makes the architecture visible. I like connecting things that have been treated as separate. I like taking something I can almost physically see in my head and figuring out how to build enough language around it that someone else can walk around inside it too.

The problem isn't translation.

The problem is translation without a stopping condition.

How many explanations before I accept that comprehension isn't the constraint?

How much evidence before I stop assuming the missing ingredient is evidence?

How many ways do I need to say what I need before another person's response becomes information rather than another prompt for me to communicate better?

I don't know exactly where that line is.

But I think there has to be one.

Otherwise "I'm good at making the invisible visible" quietly becomes:

I am responsible for making reality impossible for other people to ignore.

I'm not.