Frame 1 · Two cultures
Two teams, two triangles
Every team has its own culture: a whole of values, norms, habits and communication style. As long as those worlds stand apart, the edges collide.
Culture compatibility describes how far the unwritten rules and behaviours of teams fit together. Differences in values, norms, habits and communication style explain why teams such as Sales and IT collide regularly.
Culture compatibility describes how far the unwritten rules and behaviours of teams fit together. Differences in values, norms, habits and communication style explain why teams such as Sales and IT collide regularly, while both are simply trying to do their work well.
The sly part of culture collisions is that nobody is doing anything wrong. Every behaviour is entirely logical inside its own culture: the developer who keeps their door shut is protecting quality, the account manager who walks in is protecting the customer. Only whoever sees the layer underneath, the value that steers the behaviour, can read the other’s behaviour as a different logic instead of as obstruction. And that is exactly the same movement as in every conflict: under the behaviour sits a driver, and that is where understanding begins.
Culture compatibility does not mean all teams have to share one culture. Different perspectives are precisely what makes an organisation stronger: you want an IT that stands for stability and a Sales that brings speed. What teams do need is an understanding of each other’s way of working, drivers and communication. That mutual recognition makes effective cooperation possible, despite the cultural differences. In the picture: two triangles that do not have to cover each other, but do have to overlap.
In a mediation between teams we walk through the four layers together: which values, rules, routines and language does each team have, and where do they rub? Naming that without judgement takes the question of blame out: the other’s behaviour becomes a different logic instead of unwillingness. If this is happening after a merger, also read tension after a merger. Read more about how we work →
With recurring friction between departments that each have their own trade: Sales and IT, production and planning, head office and sites. With teams that have to work together after a merger or a reorganisation and keep failing to find each other. And beforehand: whoever lays the four layers side by side before a collaboration starts knows where the collisions will come, and can be ahead of them.
Then it helps to walk through the four layers together: where does the difference sit, and what is the logic behind it. We are glad to support that conversation.