I’ve asked this question more times than I can remember:
“Did you understand?”
Sometimes the answer came quickly.
Sometimes with a nod.
Sometimes with a polite smile and a firm “Yes.”
And more often than I like to admit, that “Yes” turned out to be unreliable.
Not because anyone was lying.
Not because anyone was incompetent.
And not because of bad intentions.
The conversations were polite.
Professional.
Perfectly acceptable on the surface.
And still, things went wrong later.
Requirements were implemented differently than expected.
Assumptions surfaced far too late.
Responsibility was unclear — or silently misplaced.
At some point, it becomes tempting to reach for easy explanations.
Culture.
Language barriers.
Communication style.
Those explanations sound reasonable.
They also feel suspiciously convenient.
Because they locate the problem somewhere else —
with them, their background, their way of speaking.
What took me much longer to see was something less comfortable:
Language didn’t fail because people came from different cultures.
It failed because I treated language as if it were neutral —
as if words travelled unchanged through hierarchy, fear, and unequal risk.
They don’t.
Meaning Doesn’t Travel Intact
Inside organizations, language is not a clean pipe.
It behaves more like a risk‑aware protocol.
Every exchange silently answers a different question than the one being asked:
What is safe to say here?
Every hop — manager to team, expert to non‑expert, native to non‑native speaker — transforms context.
Some meaning is lost.
Some is added.
Some is carefully reshaped to avoid danger.
Intent is reinterpreted.
Assumptions sneak in.
Risk is recalculated.
Culture influences how this happens.
But culture alone doesn’t explain why it keeps happening.
To understand that, you have to look at the situations where one particular word becomes suspiciously reliable:
Yes.
Three Situations Where “No” Is the Risky Answer
1. When “No” Risks Reputation
In one project, I worked with an Indian offshore team.
During refinement or clarification, I would ask:
“Did you understand?”
The answer was almost always yes.
Later, gaps appeared.
Not small ones.
Foundational ones.
For a long time, I explained this culturally:
reluctance to challenge requirements, respect for hierarchy, conflict avoidance.
What I missed was the risk embedded in the question.
Saying no did not mean “I need clarification.”
It could mean “I didn’t get it.”
Or worse: “I’m not competent.”
Under those conditions, yes is not agreement.
It’s self‑protection.
The unspoken contract is simple:
I acknowledge what you said.
I am not challenging you.
I am not putting myself at risk.
The system works exactly as designed.
2. When “No” Risks The Relationship
In another context, with Chinese colleagues,
the same question produced the same answer:
Yes.
But the risk was different.
Here, the question wasn’t heard as
“Did you understand the content?”
It was heard as
“Did I explain this well?”
Answering no would imply that the other person — often a superior — had failed.
That would cause loss of face.
So again, yes was the safe choice.
Not to protect myself this time.
But to protect the relationship.
The silent contract here is:
I won’t embarrass you.
I won’t damage our relationship.
We keep harmony intact.
Different culture.
Different risk.
Same outcome.
3. When “No” Risks Flow
Then there were situations much closer to home.
Same language.
Same nationality.
No obvious cultural distance.
When I asked “Did you understand?”, yes usually meant exactly that:
I understood.
Nothing more.
But that yes was often read as something else.
As agreement.
As alignment.
As “we can move on.”
Sometimes even as ownership.
Saying no here wasn’t dangerous in a dramatic way.
It didn’t threaten competence or face.
It threatened flow.
It meant:
- prolonging the conversation
- reopening something that was already considered settled
- being perceived as pedantic, resistant, or not pragmatic — someone who slows things down
So yes became a way to avoid friction.
The unspoken contract:
I won’t slow this down.
I won’t turn this into a discussion.
Later, when assumptions surfaced, both sides were surprised — for different reasons.
Why Only Saying “It’s Cultural” Is Too Cheap
These three situations are often treated as three different problems.
They aren’t.
They are the same system adapting to different risks.
Hierarchy creates unequal exposure.
Incentives decide what is punished or rewarded.
Language adapts accordingly.
Culture doesn’t create these distortions.
It encodes survival strategies into them.
Saying “it’s cultural” sounds sophisticated.
It also stops the inquiry too early.
It allows us to avoid the harder questions:
What about this interaction makes honesty risky?
What kind of behavior does the system quietly reward?
Language as a Mirror
Language doesn’t just transmit meaning.
It reflects power.
If people consistently answer in ways that later turn out to be incomplete, overly optimistic, or misleading, that’s not primarily a communication problem.
It’s a signal.
A signal that:
- disagreement is unsafe
- doubt is inconvenient
- alignment is valued more than accuracy
In such environments, language tells you less about what people think —
and more about what they believe is survivable to say.
A Quiet Conclusion
Nobody in these stories was lying.
Nobody was acting maliciously.
The protocol worked.
Which is precisely the problem.
As long as we treat language as neutral and immutable,
we will keep being surprised by outcomes that were, in hindsight, entirely predictable.
Not because people are different.
But because systems quietly teach people
what yes and no are allowed to mean.