Six months into a collaboration, something surfaces that your partner apparently saw from the start. Your recollection is that nobody objected. Theirs is that they raised it twice.
Both recollections are accurate. The objection was made in a form you did not register as one.
Silence is not consent
In many Vietnamese working contexts, disagreement is expressed by not agreeing rather than by objecting: a question instead of a counter-proposal, a remark about practical difficulty, a noncommittal "we will try to look at that", or simply nothing.
Colleagues inside that context read these as clear signals. You, working from a convention where the absence of objection constitutes assent, read them as assent — and then act on it, in good faith.
The cost lands later, and it lands mostly on your partner: work proceeds down a path they cannot sustain, and by the time it becomes visible they are the ones who must explain a delay.
Signals that usually carry an objection
Not a decoding chart — people differ, and hierarchy inside their institution matters more than nationality. But these four are worth treating as yellow flags rather than as agreement:
A question about feasibility where you expected a yes. "How long do you think the approval would take?" is often a statement that it will take too long.
"We will try." In your convention this is a commitment; it frequently is not one.
A long pause before agreement on a call, especially from the more junior person on their side.
Nothing at all from people who were in the room. If only the senior person spoke, the group's view has not been expressed — and the junior members are often the ones who will do the work.
When you see any of these, do not proceed on the assumption of agreement. Ask again, differently.
How to ask so objections actually surface
Do not ask "does everyone agree?" In a hierarchical setting that question produces agreement almost automatically.
Ask what would make it fail. "What is most likely to go wrong with this plan on your side?" This invites a problem statement rather than a challenge to your proposal, which is far easier to voice.
Ask for a specific number. "How many weeks would the ethics approval realistically take?" A concrete question gets a concrete answer, where a general one gets reassurance.
Give the option of answering later, in writing. Say it explicitly: "You don't need to answer now — send me your concerns in writing this week." Writing in a second language is easier than speaking in it under time pressure, and it removes the audience.
Ask the junior members separately. A short call without the senior colleague, if it can be arranged without awkwardness, often yields the real constraints. Frame it as a working session on details, not as going around anyone.
Say what silence will mean. "If I don't hear back by Friday I'll take that as agreement — so please tell me if you need more time." This makes your convention explicit instead of assumed.
Giving critical feedback that lands
Your normal register — "this analysis is wrong" — is about the work, and you mean nothing personal by it. It may not be heard that way, particularly by a junior researcher, and particularly in front of others.
Three adjustments that cost you nothing:
Criticise in writing or privately rather than in a group call, when the point is substantial.
Attach the criticism to the object. "In Table 3 the denominator looks wrong to me" travels better than "the analysis is wrong", and it is also more useful.
Say what should happen next. A criticism with a proposed action reads as collaboration; one without can read as a verdict.
None of this means softening the content. It means making clear the target is the work.
Structures that make dissent safe
Individual technique helps; structure helps more, because it does not depend on anyone being brave in the moment.
Written decisions after every meeting — a short list of what was agreed, sent round with an explicit invitation to correct it. Correcting a written line is much easier than objecting live.
A standing item for problems. Every meeting ends with "what is blocked or at risk". When it is a routine slot, raising something is not a complaint.
Ask the partner to draft the work plan for their own part rather than reviewing yours. What is missing from their draft tells you what they consider infeasible, without anyone having to say no.
Name one person on their side as the channel for concerns, and ask them directly and regularly.
One thing to say at the start
Early in the collaboration, say plainly that you want disagreement, that you will not read it as difficulty, and that a plan changed at week three is normal while a plan changed at month six is expensive.
Then do the part that determines whether it is believed: the first time your partner raises an objection, change something visibly in response. That single act establishes more than any amount of encouragement.
Why doesn't silence mean agreement?
Because in many Vietnamese working contexts disagreement is expressed by not agreeing — a feasibility question, a remark about difficulty, or nothing — which colleagues inside that context read clearly.
What should I ask instead of does everyone agree?
Ask what is most likely to go wrong on their side, ask for a specific number, and offer the option of answering later in writing.
How should I give critical feedback?
In writing or privately when substantial, attached to a specific object rather than the work as a whole, and paired with a proposed next step.
What structure makes dissent easier?
Written decisions circulated after each meeting with an invitation to correct them, and a standing meeting item for what is blocked or at risk.
