A group arrives for a week. They have raised money, taken leave from work, and flown a long way. Somewhere in the first afternoon it becomes clear that the one person who speaks both languages is now going to spend the entire week translating instead of doing anything else.
The bilingual host is the bottleneck
They meant to organise the week. Instead they stand between two groups repeating sentences from breakfast until the evening, and the visiting team never has a single conversation the host is not part of.
Both sides end up with a relationship to the interpreter rather than to each other. The team goes home having met one person well and twenty people through a filter, and the local group has the same experience in reverse. That is the specific loss, and it is larger than the inconvenience.
It is also exhausting in a way nobody accounts for. See where a human interpreter struggles — a week of this is considerably worse than a Sunday of it, and the host usually has a job to return to.
Sort the sessions from the conversations
These trips have two kinds of talking, and they need different answers. Getting this distinction right is most of the solution.
The sessions — a talk, a training day, an evening meeting, a presentation to a room. One person speaking, everyone else listening, usually prepared. This is exactly what live translation is for, and it removes the largest single block of the interpreter's week in one move.
The conversations — meals, corridors, the walk between places, the evening on the porch. Short, two-directional, informal, and constant. A phone app is genuinely fine here, and so is patience and a shared sense of humour. Do not over-engineer this part.
The mistake is trying to solve both with one thing. Nothing covers both well, and attempting it usually means the sessions get the informal treatment they cannot survive.
Prepare the vocabulary before they land
Every partnership has its own words: place names, the name of the project, the roles people hold, the villages, the local term for the thing everyone calls by a nickname.
Fifteen minutes spent listing these before the trip prevents the same mistranslation being repeated for a week — and it is a week, because nobody corrects it. Supply the list to whatever you are using; on the difficult audio of an unfamiliar room it makes a measurable difference.
Ask the host for it rather than writing it yourself. They know which words matter and you do not.
Translate in both directions
The mistake teams make is treating the visitors as the ones who need translating. The evening where local members speak and the visiting team listens is usually the more important one — and it is the one that gets skipped, because it is harder to arrange and nobody planned for it.
If your setup can broadcast from whoever is holding the microphone, use it both ways. Deliberately schedule at least one session where the direction is reversed. Teams consistently report that this is the thing they remember, and it is the thing that turns a trip into a relationship.
The rooms you will actually be in
Plan for the practical realities of these trips, which are rarely a well-equipped hall:
- Bring a clip-on microphone. Do not assume a sound system, and do not assume the one that exists works. A single microphone in a bag solves most rooms.
- Check the connection on day one, in the actual rooms, not from the guesthouse. Where connectivity is genuinely poor, know that before you have planned a week around it.
- Charge everything. Power may not be continuous, and a dead broadcasting device ends a session.
- Have a fallback. If the connection fails on the day, the host interprets that session and you carry on. Say so in advance so nobody panics.
Brief the visiting speakers
Visitors speak differently when they know they are being translated, and it takes one conversation before the first session: one voice at a time, finish your sentences, pause at the end of a thought, and avoid the idioms.
That last one is worth being specific about. Sports metaphors, cultural references and jokes that depend on wordplay do not survive translation in any direction, human or machine. A speaker who drops them loses nothing and gains a room that follows.
Leave something behind
The week ends and the material leaves with the team. If the sessions were captured and translated, the local group keeps the content in their own language after the plane has gone — the teaching, the training, the whole week, readable.
That is the difference between a visit and a partnership, and it costs nothing extra once the sessions are being translated anyway. Ask the host what they want kept, and honour it: some material is welcome and some is not, and the visiting team is not the one to decide.
A short checklist for the organiser
- Decide which sessions are translated before the team arrives, not during.
- Test the room and the microphone on day one, not five minutes before the first session.
- Give the visiting speakers the list of habits that make translation work.
- Free the bilingual host from the sessions so they can run the week.
- Schedule at least one session in the other direction.
- Agree with the host what gets kept, and keep the transcripts for the group that stays.
Set it up for the week only
InMyTongue meters by the hour, so a one-week visit costs a week rather than a year. New accounts include free credit. Set it up before the team lands.