How do you design two companies into one team?
The conventional approach is an integration plan full of systems, a kick-off event, a culture presentation. The alternative is small, deliberate changes to the context that actually produces shared behaviour: systematically mixed seating, shared workspaces built from scratch, a shared canteen as the first point of contact. These small contextual changes generate the thing integration actually depends on, which no kick-off speech can manufacture: frequent, informal, equal contact between people from the two sides.
The integration plan that forgets behaviour
The conventional response to a merger is to plan the integration of systems and structures. Align the processes. Merge the platforms. Hold a kick-off meeting. Deliver a presentation about the combined culture. The logic treats integration as a problem of joining up the machinery, and assumes that once the systems are merged, the people will follow.
But mergers fail on behaviour, not machinery. Two cultures bring two sets of unwritten rules, two ways of running a meeting, two assumptions about how things are done, and these collide constantly, in every interaction, long after the systems are aligned. The integration plan addresses the systems and never touches the context that would produce genuinely shared behaviour. A kick-off event and a culture slide do nothing to change the daily environment in which the two groups either become one team or remain two tribes. The plan optimises the visible machinery and ignores the invisible behaviour, which is exactly where mergers actually fail.
The alternative is to change the context that produces shared behaviour, through small, deliberate design choices. Mix the seating systematically so people from the two sides sit together rather than clustering with their own. Build shared workspaces from scratch, belonging to neither legacy company. Make a shared canteen the first place the two groups meet. None of this is a grand integration initiative. It is a set of small changes to the daily environment that manufacture the contact from which a shared culture can actually grow. The behaviour is not exhorted in a kick-off. It is produced by the redesigned context.
Why this is design, not team-building
You could read the mixed seating and shared canteen as nice touches, softer accompaniments to the real integration work. But that misses the mechanism, and the mechanism is what actually merges the cultures.
These changes do not motivate the two groups to bond by encouraging them to embrace one another. There is no campaign urging unity, no appeal to the new shared identity. The integration comes from the context generating contact, frequent, informal, equal contact, from which relationships and shared norms form on their own. People do not become one team because they were inspired to; they become one team because the environment kept putting them in contact until the dividing line blurred. The bonding is not requested. It is produced by the design.
That is the difference between design and motivation, and in mergers it is decisive. Motivation tries to persuade two cultures to embrace each other, usually through events and presentations that change nothing about the daily reality of two tribes sitting apart. Design changes the daily reality so the contact, and the integration, happen without anyone being persuaded. You cannot reliably inspire two groups into one identity through a kick-off speech. You can design an environment that mixes them constantly, and let the shared culture grow from the contact.
The failed integration was never only about resistant people. It was about a plan that changed the systems and left the context that shapes behaviour untouched.
Turn your instinct for progress into a method
The Behavioural Design Method gives you tools to find the friction in any situation and redesign the path. For your organisation, your team, or your own work.
The principle: contact and informal interaction
The research underneath this is well established, and naming it turns the mixed seating from a soft touch into a usable principle.[1]
Two ideas combine here. The contact hypothesis, with deep roots in social psychology, holds that contact between groups, under the right conditions of frequency, equality and informality, is one of the most powerful ways to reduce division and build cohesion across group lines. And research on organisational socialisation finds that frequent, equal, informal encounters are the strongest predictor of cohesion that crosses group boundaries. The key word in both is informal. It is not the formal, structured meeting that merges cultures; it is the unplanned encounter, the shared lunch, the proximity that turns strangers from the other side into colleagues.
This is why the small contextual changes outperform the grand integration plan. Mixed seating, shared workspaces and a shared canteen are machines for generating exactly the kind of contact the research identifies as decisive: frequent, equal, informal. The kick-off event, by contrast, produces a single formal encounter and then sends everyone back to sit with their own. The plan that ignores informal contact ignores the very mechanism by which cultures actually merge. Design the contact in, and integration follows. Leave it to a presentation, and the two tribes remain.
The persistence of two cultures was never only about people refusing to mix. It was about an environment that never gave them the frequent, informal, equal contact integration requires.
The word equal in that finding deserves particular attention, because it is where most merger integrations quietly fail even when they do try to engineer contact. If the two groups meet, but one is plainly the acquirer and the other the acquired, one occupies its own building and the other is a guest in it, one's systems and norms prevail and the other's are tolerated, then the contact happens on unequal terms, and unequal contact tends to harden division rather than dissolve it. This is why building shared ground that belongs to neither legacy company matters so much. Neutral territory, mixed from the start, is what makes the contact equal, and equal contact is what the research identifies as the version that actually builds cohesion. Contact alone is not enough; contact between a host and a guest can make things worse.
What you can design this week
You do not need a merger to apply this. The principle, that frequent informal equal contact builds cohesion, works wherever groups need to become one.
Engineer informal contact, not just formal meetings. The research is clear that informal encounter does the integrating. Shared lunches, mixed seating, proximity that produces unplanned interaction matter more than any structured kick-off. Design for the contact that happens between the meetings.
Mix people by design, not by chance. Left alone, people cluster with their own. Systematically mixing seating, teams and spaces ensures the cross-group contact that cohesion depends on, rather than hoping it occurs.
Build shared ground that belongs to no one. A workspace or canteen that belongs to neither legacy group gives people neutral territory to meet on. Shared ground that favours neither side removes the sense of one group hosting and the other visiting.
Stop integrating only the systems. This is the deeper shift. Mergers pour effort into joining the machinery and almost none into the context that produces shared behaviour. The systems matter, but the behaviour is where mergers fail. Design the contact that produces a shared culture, alongside the systems.
The thread is the one that runs through everything we do at SUE. You rarely merge two cultures by exhorting them to unite. You merge them by designing the frequent, informal, equal contact from which a shared culture grows. The integration was never a matter of a better kick-off. It was a matter of building the daily contact that does the actual work.
If you want to learn how to design the contact that turns two groups into one team, rather than relying on events that change nothing, that is exactly the kind of work our Behavioural Design training is built around.
Start designing for behaviour, not hoping for it
The SUE Behavioural Design Method teaches you to find the friction, redesign the path, and make the right behaviour the easiest option. In two days live or at your own pace online.
1.5 minutes on influence
10,000+ readers · Free · Unsubscribe anytime