After the merger: two ways of working that do not talk to each other

The teams merged on paper. Each keeps its rules, its tools and its reflexes. How to make the gaps visible, and pick a target rule instead of an average.

7 min readUpdated August 21, 2026

A legal merger happens on a date. An operational merger happens rule by rule, and nothing forces it to happen at all. In between, two organizations keep running side by side, each convinced the other will eventually fall in line.

What merges, and what does not merge on its own

Legal entities, contracts, scopes and often tools are handled as a project: someone owns it, there is a date, you know when it is done.

Ways of working have neither owner nor date. The level at which a spend is approved, the delay considered normal for answering a client, what gets written down and what gets settled verbally, what a meeting is supposed to produce: none of it is written, so none of it compares, so none of it gets decided.

That is where the friction attributed to culture lives. Culture is the name we give to a gap in rules nobody has laid out yet.

Where the gaps sit

Four families cover most of it. Decision thresholds first: who commits what, above which amount, with whose approval. Rhythms next: how often people meet, what gets decided in a meeting and what gets decided between two.

Vocabulary comes third, and it costs more than it looks. Two teams calling client, project or approved two different things will believe they understood each other, and find out otherwise at the worst possible moment.

Quality expectations last: what is acceptable to ship, what triggers a review, what gets fixed afterwards. A gap here reads as sloppiness on one side and bureaucracy on the other — never as a different rule.

Question both populations in exactly the same way

The condition is symmetry: same questions, same moment, same terms on both sides. A questionnaire sent to the acquired entity first and to the other one later no longer compares, and reads as a one-way audit.

Every answer has to be attachable to the original entity, the team, the role and the site. Without the original entity, the very gap you care about disappears from the analysis; without the team, you will not know whether it is general or concentrated on one handoff.

Expect gaps in perception before gaps in practice: the two populations did not live through the same announcement. Asking each what it believes the other thinks is often more instructive than comparing the practices themselves.

Pick a target rule rather than an average

Once the gaps are laid out, the temptation is to split the difference. It is the worst option: an average matches nobody's practice, and it asks both populations to change without either recognising its own.

Decide rule by rule, and own where each one comes from each time: on spend thresholds, one side's rule; on client relationships, the other's. An explicit choice, even an unfavourable one, holds up better than a compromise nobody will claim.

Write them down, with an effective date and an owner. A target way of working that only exists in an executive meeting does not exist.

Where to start, and what to track

Start with the busiest handoffs — the ones where the two populations have to pass something between them every week. They produce most of the friction people feel, and they are quick to fix.

Then re-measure with the same questionnaire a few months later. The signal to follow is not a satisfaction level: it is the narrowing of the gap between the two populations. That is what tells you whether the merger happened.

Two signals deserve particular attention: departures concentrated on one side, and answers from front-line managers when they diverge sharply from the rest — they are the ones absorbing the gap day to day.

Key points

  • The legal merger has a date; merging the ways of working has none unless you set one.
  • Same questions, same moment, both sides — and keep the original entity in the analysis.
  • Decide rule by rule and own its origin: an average matches nobody's practice.
  • Success shows as a narrowing gap between the two populations, not as an overall score.

These steps are tooled in Syntonie

Questionnaires, transcribed interviews, analysis by team and by role: the platform runs a firm's method on your organization, described once.