Date:
001
The quiet inheritance
There is a particular sound a room makes when someone says "we" and means only half the people in it. I heard it clearly in a workshop with a leadership team, two years after their organisations had legally become one. Someone referred to "the old way of doing performance reviews," and I watched half the table nod in recognition while the other half looked faintly, politely lost. Nobody in the room seemed to notice this had happened. It had become entirely ordinary.
Mergers are usually narrated in the language of structure, systems integrated, reporting lines redrawn, entities combined, a defined date by which the new organisation exists on paper, in its systems, in its financial statements. What almost never appears in the transaction documents is the thing that takes the longest to actually merge: the quiet, half-conscious sense two groups of people carry about who they are and how things are properly done.
Across the mergers we have been part of, a consistent pattern emerges, and it is rarely the one leadership expects. It is not that the two cultures clash openly. It is that one culture, almost without anyone deciding it should, becomes the default, the meeting rhythms, the tone of emails, the unspoken rules about how disagreement is voiced. While the other is gradually folded in as a set of exceptions to be politely accommodated rather than strengths worth actively keeping. I have come to think of this as the quiet inheritance: not a hostile takeover of culture, simply water finding its lowest point, unless someone deliberately intervenes.
We saw it plainly in an organisation formed from the merger of two long-established, member-owned institutions, each with a genuinely proud history and a genuine belief that the merger served their members well. Operationally, everything had gone smoothly. Branding had changed. Leadership spoke, often and sincerely, about "one organisation, one future."
002
How we worked
We spent the first stretch of the engagement deliberately without an agenda, separate listening sessions with people from each legacy institution, before ever bringing the two together in a room. The goal was to hear, without steering, how each group described "how things are properly done here." That was the actual phrase we used in every session, and the answers people gave to it became the raw material for everything that followed.
From there, the KLAR diagnostic turned those conversations into a structured culture map, comparing both groups against three lenses: how decisions got made, whose approval genuinely mattered, and which meetings actually moved things forward versus which were simply attended. The pattern was consistent, and to the leadership team, genuinely uncomfortable to see laid out plainly, one legacy institution's habits had become the default across all three lenses. The other's had not been rejected. They had stopped being asked for.
We did not leave that discovery as an observation for leadership to sit with. We ran a series of joint sessions explicitly designed to force deliberate choices, which practices from each legacy institution to formally carry forward, which to retire, and which to blend into something neither had done alone. Each choice was documented and communicated back to both legacy groups, so the new "normal" was visibly decided rather than quietly inherited by whoever happened to speak first in meetings.
The final phase built that decision into daily life: a small set of shared rituals, co-designed rather than borrowed from either side, and a six-month check-in against one deliberately simple marker, whether people had started saying "we" without a pause, and whether "the old way" was fading from meetings in both directions rather than one.
By the close of the engagement, the conversation in that leadership team had moved from finishing the integration to something more deliberate: which parts of each legacy identity were worth actively carrying forward, on purpose, rather than allowing one to fade just because nobody had been asked to protect it.
003
A SkyKlar Reflection
A merger can be completed on a balance sheet in a single financial year. Completing it in the way people understand who they now are tends to take a great deal longer, and almost nobody puts a date on that second kind of completion.
I have started asking leadership teams, sometimes years after the paperwork is finished, whose history they have been calling the only history. The silence that follows is usually longer than the question seems to warrant.
