Between field visits, a collaboration is the sum of its video calls. Which means how you run them determines how much of your partner's expertise actually reaches the project.
Rotate the bad hour
With a five-to-seven-hour difference, someone is always inconvenienced. The problem is not that — it is that it is almost always the same side.
Check what time your standing meeting is in Hanoi. If it is consistently evening or night there, that is a choice you made by default, and your partner is unlikely to raise it while you hold the funding.
Rotate it. Propose the rotation yourself rather than waiting to be asked.
And always write both time zones when scheduling. Daylight-saving shifts on your side move the meeting for them without warning, and missed calls get attributed to the partner rather than to the clock change.
An agenda that makes contribution possible
Send it at least a day ahead, with three separated sections: decisions needed, discussion, information only.
Send the information-only items in writing and do not read them out. A call where thirty of forty minutes is progress narration leaves the decisions to be rushed at the end — and the rushed part is where your partner is least able to intervene.
For each decision, state the proposal rather than opening a general question. "Should we adjust the timeline?" invites silence; "we propose moving milestone three to June — does that work at your end?" invites an answer.
Language load is higher live than on paper
Following a multi-speaker call in a second language, in the evening, after a full teaching day, is substantially harder than reading the same content.
Three things that help, all cheap: send materials in advance; circulate minutes afterwards; and slow down slightly, avoiding idioms and abbreviations.
Also watch the overlap. If your side is in one room and your partner is remote, your side will talk over each other and the remote participant will not get in. Assign someone to notice and invite them explicitly, by name.
Silence is not agreement
This matters more on video than in person, because the cues you would use to read hesitation are mostly absent.
If a proposal draws no objection on a call, do not record it as agreed. Ask a specific closed question — "is six weeks enough, or do you need more?" — and if the answer is quick and positive, ask one follow-up.
And check individually afterwards. A concern that cannot be raised on a call with six people and a funder present is often raised readily in a one-to-one message.
Minutes, rotated
One short note after each call: decisions, actions with owner and date, open items.
Rotate who writes them. If your side always writes the minutes, your side also defines what was agreed — and over a three-year project that asymmetry compounds.
Ask your partner to correct anything that does not match their understanding, and mean it. After two months the written record becomes the truth.
What should not be settled on a call
First conversations about authorship and data rights. These need writing, and a call is where someone can appear to agree without having fully followed the implications — particularly across a language gap and a power gap.
Substantive criticism of an individual's work in front of the group. Do it privately.
Any significant decision when the person most affected could not attend because of the hour.
Cadence and the channel between calls
Fortnightly is usually sustainable for an active project. Weekly becomes a formality; monthly lets problems accumulate too long.
Between calls, ask which channel your partner actually uses. Messaging apps are often far faster than email in practice, and insisting on email because it suits your workflow slows the project.
And do not cancel a call because there is nothing new. That is when it matters most — collaborations die from silence more often than from conflict.
One thing worth asking directly
Every few months: is there anything about how we are running these meetings that makes it harder for you to contribute?
Ask it privately, and expect the first answer to be "no, it's fine". Ask once more, specifically — about the hour, about the pace, about whether the agenda arrives in time. That is usually where the real answer is.
How should the inconvenient meeting hour be handled?
Rotate it, and propose the rotation yourself — your partner is unlikely to raise it while you hold the funding.
Why send information-only items in writing?
Because reading them out consumes the call and leaves decisions rushed at the end, which is where the remote participant can least intervene.
Does no objection on a call mean agreement?
No. Ask a specific closed question, then check individually afterwards — concerns that cannot be raised in a group call are often raised in a one-to-one message.
Who should write the minutes?
Rotate it. If one side always writes them, that side also defines what was agreed, and over a long project the asymmetry compounds.
