The most common failure in collaborations with partners in Vietnam is not a disagreement. It is a foreign team believing something was agreed when it was not.
Silence is not agreement
In a meeting, a proposal that draws no objection may simply have drawn no objection that anyone felt able to voice — particularly if you are senior, foreign, or holding the funding.
Phrases like "we will try", "let me check", or a pause before answering often carry doubt. Read them as questions still open.
What works: ask specific closed questions instead of general ones. "Is six weeks enough for this, or do you need more?" gets a usable answer. "Does that work for everyone?" reliably gets a yes.
And ask individually rather than in a group meeting. A concern that cannot be raised in front of a room is often raised readily one-to-one.
Hierarchy shapes who speaks
In many Vietnamese research settings, a junior member contradicting a senior colleague in an open meeting is not normal practice. If your meeting includes a department head, expect the room to defer.
This has a practical consequence: the person who actually knows whether the fieldwork timeline is feasible may be the most junior person present, and they will not say so.
Options that work: ask the junior team members directly and by name; hold a separate working meeting without the senior figures; or ask your counterpart to collect input and report back.
None of this requires anyone to change how they operate. It requires you to stop treating meeting silence as data.
Feedback
Direct criticism of work in front of others lands harder than it does in settings where it is routine. The content may be entirely correct and still damage the working relationship.
Give substantive criticism in writing or privately. Say what is strong as well as what needs work — not as politeness but because it tells your partner what to keep.
Equally, do not soften criticism into vagueness. "This section could perhaps be developed" may be heard as a minor suggestion when you meant the analysis does not hold. Be plain about what must change; choose the setting carefully.
Email and response time
Email response times are often slower than you may expect, and messaging apps are frequently the faster channel for anything time-sensitive. Ask your counterpart which channel they prefer, and use it.
A message with no reply usually means it is queued behind teaching load and administrative work, not that it was ignored.
Also keep in mind that many colleagues carry heavy teaching loads alongside research — often much heavier than the equivalent role at your institution. Timeline expectations built around a research-only workload will not fit.
The calendar
Lunar New Year reshapes any plan it touches: institutions, transport and services operate very differently for an extended period. Schedule around it rather than through it, and do not set a deliverable immediately after it.
Ask about the academic calendar too. Examination and admission periods absorb faculty time almost completely.
And ask about the rainy season for your specific field sites, since it determines road access and differs substantially by region.
Administrative time is real work
Your partner will absorb permissions, local approvals, procurement, and financial reporting under a system you do not see. These take considerably longer than the equivalent at your institution, and they are work.
Build them into the timeline, and into the budget as staff time. Treating them as background favours your partner performs for free is the most common form of quiet inequity in these partnerships.
Five things to settle in the first meeting
Who is the main contact on each side, and which channel they use.
Meeting rhythm and progress reporting rhythm.
What happens when either side slips — who is told, how far ahead.
Both sides' holiday and teaching calendars.
How disagreement gets raised, given that it may not surface in group meetings.
The fifth is the one foreign teams skip, and it is the one that determines whether you find out about problems early.
The thing worth checking in yourself
If your partner keeps agreeing to everything you propose, that is not a sign the collaboration is going well. It usually means the power imbalance is large enough that disagreement feels unavailable.
Ask what they would change about the plan, and make it easy to answer honestly — privately, and with a genuine signal that a changed plan is acceptable to you.
Does no objection in a meeting mean agreement?
Often not. Ask specific closed questions, and ask individually rather than in a group — concerns that cannot be raised in a room are often raised readily one-to-one.
Why might the most knowledgeable person stay silent?
Hierarchy shapes who speaks in many settings. The junior member who knows the timeline is unfeasible may not say so in front of senior colleagues.
How should we give critical feedback?
In writing or privately, plainly about what must change, and naming what is strong so the partner knows what to keep.
What do foreign teams most often underestimate?
Administrative work — permissions, procurement, financial reporting — and teaching loads. Both are real work and belong in the timeline and budget.
