Change Comes From the Top, and Everyone Expects It To
When a French team faces a change, expect it to be decided and announced by the boss or the centre, not assembled from the group. People look upward to see where a real change is supposed to originate — the chef, head office, whoever holds the formal mandate. A change that bubbles up informally from a colleague is often treated as that person’s private initiative rather than something the team is obliged to adopt. This isn’t passivity; people hold strong views and will press them hard. But they want a legitimate authority to own the decision and carry it. If you’re driving change, don’t try to engineer grassroots consensus first. Secure clear, visible backing from the top, then communicate it as a decision properly made by someone entitled to make it. A change with no owner up the hierarchy tends to drift and quietly die.
Nothing Moves Until the Reasoning Holds Up
French colleagues will ask “pourquoi?” — and they mean it. Before people accept a change, they need to see that it makes sense as an idea: that it’s coherent, logically argued, and fits a clear rationale, not just “because the market shifted” or “let’s try it and see.” A change pitched as purely pragmatic or experimental can land as unserious. What persuades is a well-constructed case — the problem, the logic, the conclusion — that survives challenge. Expect intense questioning that can feel like opposition; usually it’s people testing whether the idea is sound. If your reasoning has gaps, they will find them, and the change stalls. So invest in the argument before the rollout. Bring the why, defend it confidently in debate, and accept that “it works in practice” carries less weight here than “it makes sense in principle.”
Open Pushback Is Normal, Not a Crisis
Don’t mistake loud objection for rejection. In French working life, contesting a change openly — debating it, complaining about it, airing every reservation — is how people engage with it, not how they sabotage it. A meeting where the change is criticised from all sides, or colleagues who grumble (râler) about it for days, is people processing the thing, not refusing it. Silence is the worrying sign, not noise. The reflexive first response is often “non” or “oui, mais…”; treat that as an opening position, not a verdict. Give people room to argue, take their objections seriously, and answer them. If you treat contestation as disloyalty or try to shut it down, you lose legitimacy fast and resistance hardens. The colleague who argues hardest is often the one who, once convinced, implements most committedly. Build debate into the timeline rather than treating it as a delay.
Whatever People Already Have, They Will Defend
Expect strong, principled resistance to anything that removes an established practice, right, or standard — even a small one. The logic runs: this was earned, or has always been done this way, so the burden is on you to justify taking it away, not on them to justify keeping it. Long-standing routines, the accepted way of working, arrangements people treat as theirs (an acquis) — touching these triggers more resistance than the practical stakes alone would predict, because it’s felt as a matter of principle. When you must change something established, name what’s being protected, explain why the change is worth it, and where possible preserve or visibly compensate the thing people value. Framing change as building on and respecting the existing standard works far better than framing it as sweeping the old away. “We’re improving what you’ve built” beats “we’re replacing it.”
People Adapt by Working Around the System, Not by Waiting for It to Bend
When the official rules or structures don’t fit a new situation, French colleagues are remarkably good at quietly improvising a workaround — what they call système D, from se débrouiller, “to manage.” Rather than wait for the formal process to adapt, individuals find practical fixes on the ground: an informal arrangement, a shortcut, doing it their own way behind a closed door while the official line stays untouched. So real adaptation often happens invisibly, beneath a structure that looks unchanged. Two implications for you: first, watch what people actually do, not just what the rules say — the working reality may already have moved. Second, don’t assume a change has “taken” just because the procedure changed; and conversely, rigid procedures won’t stop people adapting where they see the need. Give competent people room to improvise, and they’ll often solve the transition for you.
Change Arrives in Jumps, Not Drips
French teams tend to hold a stable line for a long time and then change all at once, rather than adjusting continuously in small steps. People defend the current way of working, pressure builds, and change finally passes through a decisive moment — a breaking point, a crisis, a ruling from above, a “ça suffit.” Continuous incremental tinkering is less the norm than long stretches of stability punctuated by sharper shifts. In practice: don’t expect a smooth, gradual adoption curve, and don’t read the long quiet stretch before a change as agreement — it can be accumulated resistance. When the moment does come, change can move faster and more completely than the prior inertia would suggest. If you need movement, sometimes you have to let the case build to a head and create a clear decision point rather than nudging endlessly. Plan for stillness, then a step-change.