When Silence Isn't Agreement: Running International Projects Well

I've lived and worked on both sides of this – in Latin America and in Europe – and seen the friction from both directions, not as an outside observer applying a framework after the fact, but from inside delivery teams.

The pattern

On paper, it looks like alignment. A design decision is presented in a workshop, the room nods, the minutes say "no objections," and the project moves on. Weeks later, that same decision turns out to have been misaligned with how the local team actually works, and nobody raised a hand while there was still time to change course.

This repeats across international rollouts spanning Europe and Latin America. It isn't a question of competence or commitment. It's about what silence in the room actually means.

The sequence is almost always identical:

1. A target process is defined during scoping, and no pushback surfaces.
2. User testing either happens under time pressure or gets compressed, but sign-off is granted either way.
3. Months after go-live, the operational reality emerges: the process was formally approved at every gate, but it was never truly adopted.

Why it happens

1. Power distance vs. open contradiction

German and Northern European project delivery relies on the explicit expectation that disagreement gets voiced immediately. If an approach is flawed, someone is expected to say so – in the room, before sign-off. Absence of objection is treated as consent.

Many Latin American organizational cultures operate with higher power distance. Contradicting management or senior leads openly in a group setting carries social and political costs that simply don't exist in flatter teams. Staying quiet isn't passive agreement or lack of insight; inside that structure, it is often the only rational choice.

Put a standard "speak now or forever hold your peace" workshop format in front of that dynamic, and assumptions get rubber-stamped – not because they are solid, but because the room wasn't designed to catch them.

2. The language hurdle

Cross-border initiatives typically run in English. While most participants can communicate operational basics, raising a nuanced, high-stakes objection in a second or third language is an entirely different barrier.

Nobody wants to lose face in front of colleagues and leadership either. When in doubt, a quick "yes, understood" is the safer path than a detailed clarifying question that might expose a perceived language gap.

3. The capacity imbalance: HQ vs. site reality

Beyond culture and language sits a purely operational constraint: bandwidth. Headquarters typically staffs dedicated specialists – one lead for testing, one for security, one owner per sub-process. At the sites, the same scope often sits with one or two people wearing ten hats at once. I've seen this in Workday projects and in an SAP implementation where a single person owned Book-to-Record, procurement and HR processes at the same time.

These colleagues are genuinely versatile, but nobody can go deep into five process areas at once while also running 100% of their day-to-day operational workload. When central project teams expect a local generalist to interrogate a decision with the same depth as a dedicated HQ expert, a quiet "ok" isn't consensus. It's simply someone who has no capacity left to look closer.

What changes when you design for it

Naming the dynamic isn't enough on its own. Governance and workshop formats have to adapt to it.

• Move disagreement out of group settings: schedule brief 1:1 follow-ups right after key workshops. A private, low-stakes setting lets colleagues surface real risks without contradicting a manager or peers in public.
• Ask for objections indirectly: replace "any concerns?" with "what would have to be true locally for this process to fail?" – a question about the plan, not a challenge to the person presenting it.
• Treat sign-offs as provisional: build in a short, low-friction review window after each workshop instead of treating the session itself as final. That quiet window is where the real feedback tends to land.
• Empower local bridges without filtering them out: a respected local lead who can voice the unspoken realities on the team's behalf is invaluable, but only if that person also has a direct, unfiltered channel to whoever is actually making the call.

The takeaway

Cross-regional rollouts rarely stumble because local teams lack capability. They fail because project governance assumes everyone pushes back the same way, has equal bandwidth to interrogate a decision, and is equally comfortable doing so in a language that isn't their own.

A one-off cultural sensitivity workshop won't fix that. What works is designing the process around these realities – hierarchy, language, and site capacity – at every decision gate, not only the ones that are visibly about culture.

Planning a cross-regional rollout, or already feeling the friction between headquarters and your local teams? Get in touch to talk through a project governance setup that surfaces the real picture early.