Kicking off a project with a foreign partner
"Urgent", "approved" and "almost ready" don't mean the same thing everywhere. The best moment to fix that is before kickoff.
The project started well: a cordial kickoff, an approved timeline, good chemistry between the teams. Eight weeks later, the first serious friction: the milestone the partner considered "approved" was still, for your team, "pending review". Nobody lied. Each side simply arrived with its own language, its own way of planning and its own idea of what "urgent", "approved" or "almost ready" means. The first weeks of an international project set the tone for everything that follows, and they're precisely the weeks with the most misunderstandings per square metre.
Misunderstandings that cost real money
The ones we see repeat themselves share one trait: none of them looks serious on the day it happens.
- The elastic deadline. In one working culture, a date is an immovable commitment; in another, a reference to be adjusted by talking. The clash doesn't appear when the date is set, it appears when it's missed, by which point it's a conflict.
- Minutes each side reads its own way. Ambiguous wording ("the proposal will be considered") lets each team walk away with its own version of the meeting. Weeks later, the two versions meet.
- Decisions closed… or not. One side believes it was decided; the other, that it was discussed. The project moves forward on a decision that exists in only half the heads.
- The state of progress. "Almost ready", "in progress", "a few loose ends": expressions that don't measure the same thing across working cultures, with direct effects on the schedule.
Each of these, on its own, is solved with a conversation. The problem is accumulating them: trust between teams erodes exactly when it's needed most.
Preparing the project team: language and context together
A prepared project team shares three things. A common glossary, agreed at the start: what exactly "approved", "blocked" or "urgent" means on this project, in both languages. The skill of writing without ambiguity: minutes, agreements and emails that admit only one reading, a concrete, trainable language skill with an enormous payoff. And a read on the partner's working culture: how decisions get made, how disagreement is expressed, and what a follow-up meeting is expected to look like in their way of working.
That's language training and context training at once, tailored to the specific project, our speciality. With the target-language method, the training doesn't talk "about" the project: it's done with the project. Meetings are rehearsed before they happen, real minutes get corrected with the why explained, and the vocabulary practised is the one on the timeline pinned to the wall. Our cases include direct examples, from a project team focused on China to an integration with a German group.
Support while the project runs
Because projects don't wait for the next session, every programme includes salistem hub: participants can get an explained correction of a delicate email before sending it, rehearse tomorrow's meeting with the role-play tutor, and keep practice alive with challenges tied to the project's phase. HR and the programme owner see progress on their dashboard in real time, with reports ready for management, and for FUNDAE, since this training is fundable in Spain and we can handle the whole process.
It costs less than one misunderstanding
The arithmetic is easy to check: compare the cost of preparing the team with the cost of a single misunderstanding at the wrong milestone: weeks of delay, rework, and trust to rebuild. Our process starts with a free discovery session and training begins within days. The best kickoff is the one your team has already rehearsed.
Frequently asked questions
When should a project team be trained for international work?
Before kickoff or in the first weeks, when the tone, the channels and the misunderstandings all get established. Our programmes start within days and can accompany the whole project cycle, as one-off workshops or ongoing training.
Which misunderstandings are the most expensive in international projects?
The ones that touch commitments: deadlines one side considers flexible and the other immovable, minutes read differently by each team, decisions some consider closed and others open, and the real state of progress ("almost ready") understood in incompatible ways.
What does project-team preparation include?
Language and context together: the project's vocabulary (with a shared glossary), writing minutes and agreements without ambiguity, running follow-up meetings, and the partner's working culture. All of it built on the project's real material, not a syllabus.
What if the project is already underway and there's friction?
That's a good moment too: we diagnose the friction points (meetings, minutes, deadlines), train on the real cases and establish the shared glossary. A small investment compared with one misunderstanding at the wrong milestone.