Reading the air: high and low context communication in teams

Reading the air: high and low context communication in teams

Picture the scene: you’re in a meeting with your new team. You ask what you think is a reasonable question, and knowing glances are exchanged across the room. A couple of people suppress laughter, and the team lead moves on. It’s clear that you’ve said something wrong, but you have no idea what. The rest of the team are picking up on, and sharing, cues you can’t read and you are suddenly and obviously the outsider. There is an implicit communication at play, and you’re not in on it.

This dynamic can be thought of in terms of the context of the communication. The rest of the team are operating with a high level of shared context – they are reading something into your words, and implicitly communicating something back to you, but you don’t have the shared context to understand what that is. This is a concept that anthropologist Edward Hall identified through his work which began in the 1930s, exploring how different groups of people communicate in different ways with their own shared norms, including how people who have known each other for a long time often communicate more implicitly than strangers who have just met. He later came to term this ‘high and low context’ communication, a framing which Erin Meyer brought to a wider organisational audience through her book The Culture Map. The idea of high and low context communication is a framework that has a lot to offer anyone thinking about how teams actually function.

High and low context: what the framework says

In high context communication, a great deal of meaning is carried implicitly. It lives in relationship history, shared understanding, tone, non-verbal signals and what is deliberately left unsaid. The speaker may be saying one thing explicitly while something else entirely is being communicated, and the onus is on the listener to read between the lines. Japan is often cited as a key example of a high context culture; Meyer describes how someone who fails to pick up on implicit cues risks being labelled a kuuki yomenai – literally, “a person who can’t read the air.” Korea, Indonesia and Iran are also broadly high context cultures.

High context communication tends to flourish in societies with long, dense shared histories – populations who have had many centuries, sometimes even millennia, to develop layered, sophisticated codes of meaning and to become fluent in interpreting them with each other.

Low context communication works differently. Meaning is made as explicit and external as possible – it lives in the words themselves, in clear and precise instructions and in expectations that are named directly rather than gestured toward. The US is Meyer’s go-to example of a very low context culture. She explains that in the US, a country shaped by successive waves of immigration, with diverse populations bringing different languages, histories and backgrounds, people quickly learned that if you wanted your message to land, you had to make it as explicit as possible. Australia, Canada and the Netherlands sit similarly on the low context end of the spectrum.

But the framework isn’t only about national culture, it cuts across many kinds of grouping. A tight-knit friendship group who have grown up together will often have developed a highly implicit, almost private communication style that is opaque to anyone outside it. A group of students thrown together in university halls of residence for the first time will need to be much more explicit if they’re going to organise anything at all. The same applies in organisations. A small, long-established, relatively autonomous team will often communicate in a higher context style than a newly convened multidisciplinary group drawn from across different functions.

The problem with high context in diverse teams

And here is where we go beyond something that’s academically kind of interesting into something that’s really important for the way we work…

High context environments favour insiders. They require a depth of shared knowledge and reference that takes time and proximity to build. Anyone who doesn’t share that implicit frame – for instance new joiners, people from different cultural backgrounds, neurodivergent folks, people from outside the dominant professional culture – is operating with less information, greater ambiguity and a greater risk of getting things wrong. They’re having to work harder just to follow what everyone else seems to be understanding effortlessly. And they’re typically far less likely to speak up when they’re uncertain, because, as we know, uncertainty makes speaking up feel more risky.

This is where high context communication becomes an equity issue, not just a style preference. The implicit meanings, unspoken norms and in-jokes that mark the insiders all create gradients of access to conversation that track closely with who was there first, who shares the dominant cultural background and whose communication style is treated as the default.

This connects directly to how teams foster psychological safety. When norms are implicit, expectations are gestured at rather than named and people are expected to absorb the rules by osmosis, the barrier to speaking up rises sharply, especially for those newest to the group or furthest from the implicit reference frame. When we make our communication norms explicit, we widen the circle of people who can understand what kind of participation is welcome and how to make their voice heard.

Multidisciplinary teams

The challenge of communicating across contexts compounds when you bring together people not just from different cultural or social backgrounds but from different professional disciplines. A product manager, a clinician, a data scientist, a policy specialist and a sales lead have all been shaped by the norms, language and implicit assumptions of their respective fields. They each bring a professional context and assumed way of working and communicating that the others aren’t party to. Perhaps the clinician uses clinical terminology, which they assume everyone else will understand, while the policy specialist has a knowledge of the legislative landscape that underpins all that they say but is never made explicit. Perhaps the sales lead starts from the assumption that the team’s goal is purely commercial. None of them are wrong to carry their expertise, and in fact it’s the diversity of their backgrounds that could allow the work they do together to be hugely successful. But when their contextual assumptions go unexamined, misunderstandings and misalignments proliferate.

This is why taking some time to get to know one another’s ways of working, and, even more importantly, to establish some explicit, shared team norms at the outset of a multidisciplinary project matters so much. What this means in practice is a deliberate, intentional move to lower context communication – being as explicit and clear with each other as possible. All the dialogue that flows from there can be built on shared understanding.

When the stakes are highest: crisis and time pressure

The case for practising low context communication in ordinary conditions becomes even harder to ignore when you consider what happens when those conditions break down.

Under pressure, in a crisis, where decision making is time pressured but the stakes are high, we might feel as if we need to communicate more implicitly in order to go faster, but actually the time cost of ambiguity and flawed assumptions can be even higher. 

In their work on ‘Crisis-Ready Teams’ Waller and Kaplan described the characteristics of high-performing teams in terms of their early interaction patterns, and discovered that higher performing teams spent significantly more time in what they called the early structuring phase, where they clarified team member’s roles and created ground rules around communicating – what we would call the social contract. They observed:

“While other teams seemed to jump into the problem feetfirst with very little effort given to structuring activities, high performing teams seemed to approach the crisis situation knowing if all team members weren’t on the ‘same page’ from the beginning, coordination would become more problematic as things became more complex.”

What these high performing teams were effectively doing was taking the time to build shared mental models of their work environment and how they could work together. They were explicitly building shared context. What’s more, these high-performing crisis teams also spent more time in what Waller and Kaplan call the information sharing phase – where they pool the information they have individually with each other to augment each other’s understanding. And the authors are keen to emphasise that this doesn’t mean pausing and deliberating before you ‘stop the bleeding’ or take any immediate actions needed as part of the first response phase of a crisis. But it does mean that as we tackle complex and evolving crises, we need teams who can continually monitor the situation, “freely sharing information about the situation without fear of reprisal,” as Waller and Kaplan put it. In other words, the teams need psychological safety.

Making low context communication an explicit group norm in ordinary conditions is partly preparation for these times. Teams that have practised stating expectations clearly and treating explicit communication as a mark of respect rather than an insult to intelligence are much better placed to communicate effectively when clarity becomes critical.

Building the habit: low context as a team norm

In practice this means taking time to build a social contract deliberately, and discussing the value of low context communication with the team from the start, not assuming that clarity will emerge naturally, but treating it as something the group actively commits to.

A happy outcome of this, of course, is that the more we work on making expectations explicit, encouraging information sharing and getting clear about our roles, the more we are actually building a shared context. In time that can mean more of our coordination becomes implicit again, the team reading each other well without needing to spell everything out. The difference is that this is an implicit understanding the group has built, rather than one it took for granted at the start.

A note on the costs

So does this mean the real goal was never low context communication at all, only creating the shared context that lets us work implicitly again? Not quite. In most teams the conditions for that never fully stabilise. New joiners arrive, team boundaries shift and the shared reference frame that makes implicit working reliable is always partly under construction. Diversity of background, discipline and cognitive approach adds to this: the assumptions any group builds will always be more accessible to some members than others. As Meyer puts it, “Multicultural teams need low-context processes” – and we would extend that further: so do teams with diversity of any kind, whether of discipline, background, neurodiversity or anything else.

But it is worth acknowledging that low context communication is not a universal good that everyone will welcome naturally. For those accustomed to high context styles, a move toward explicitness can feel slow, or even patronising:  “You don’t need to spell it out – I get it!”. 

There is a risk that imposing low context communication without acknowledging this discomfort lands as a power move in its own right, as if the explicit style were simply better, rather than better suited to working with team members who come from different contexts and have different histories. As Meyer describes, we might need to be really honest and upfront about why we’re communicating like this, saying things like:

I’ll put what we discussed and agreed in writing, not because we don’t trust each other but because then we have a clear agreement we can refer back to and catch any misunderstandings or confusions. 

We can apply the principles of low context communication even to the process of moving to lower context approaches!

What a team is really developing is the capacity to move between the two styles deliberately: to grow enough shared context that it can work implicitly where that genuinely serves the group, while maintaining the discipline to switch to something more explicit whenever the situation demands it (which it often will). The way in is an honest conversation about how we communicate, and that conversation is itself an act of low context communication. We start by naming what we’re doing and why.

Further Reading

Contracting and Recontracting

Ambiguity, Predictability and Psychological Safety

Déformation professionnelle

The Calculus of Voice

The Culture Map by Erin Meyer

Crisis-Ready Teams by Mary J. Waller and Seth A. KaplanUnderstanding High- vs. Low-Context Cultures by Pablo Lamino and John Diaz