If you want to know whether a team will survive pressure, do not start with its strategy. Start with its breathing. Oxygen is invisible. No one applauds it. No one puts it on a PowerPoint slide. Yet remove it for three minutes and the conversation becomes irrelevant. Teams are no different. When information flows cleanly, people work. When it clots, they guess. And guessing in an operational environment is a dangerous hobby.

Most communication breakdowns do not begin with malice. They begin with assumption.

‘I thought you knew.’
‘I assumed it had been covered.’
‘I didn’t want to make a fuss.’

Each sentence sounds reasonable. Collectively, they suffocate performance.

Walk into two control rooms. In the first, screens glow with live data, but the real signal is in the conversation. Operators speak up when something looks odd. A supervisor asks, ‘What are we missing?’ Decisions are logged. Actions are visible. You can almost hear the air moving.

In the second room, the screens glow just the same. Yet the conversation is thinner. People speak in fragments. Updates are partial. A concern hovers but never quite lands. No one wants to be the one who slows things down. The room feels tighter, as though the windows have been painted shut. Both rooms have information. Only one has circulation.

Information Is Infrastructure

We have been trained to think of communication as a soft skill. Something about tone and empathy and perhaps eye contact if time permits. In truth, communication is infrastructure. It is pipes and valves and pressure gauges. If the pipes are blocked, the system overheats. If the valves stick, pressure builds where it should not. If the gauges lie, decisions drift from reality. High-reliability teams treat information as a life-support system. They do not leave it to personality.

Consider meetings. The word alone can drain morale. Meetings are accused of many crimes, some deserved. Yet when designed properly, they are oxygen exchangers. They pull in what is known, surface what is unclear, and push out agreed action. When poorly designed, they are humidifiers. Plenty of vapour. Little breath.

A well-run meeting begins with context. ‘What is the purpose of this session?’ That simple framing clears the throat of the room. It signals that this is not a ceremonial gathering but a working one. Updates are brief and relevant. Questions are invited. Decisions are summarised. Actions are written down where all can see them. Nothing dramatic occurs. That is the point.

How Information Gets Lost

Contrast this with the meeting that meanders. Updates spiral into anecdotes. Decisions are implied rather than declared. Actions are assumed rather than assigned. Two weeks later, someone asks why nothing has progressed. The answer is usually, ‘I thought someone else was doing it’. That sentence is the organisational equivalent of shallow breathing. Information dies in two common ways. The first is hoarding. The second is flooding.

Hoarding is often dressed as efficiency.

‘I will sort this out and then tell the team once it is resolved.’

The intention is noble. The effect is isolation. When information is withheld until perfect, others cannot adjust their own work. They operate on yesterday’s map. By the time the update arrives, it is less helpful than it might have been.

Flooding is its mirror image.

Every email copied to everyone.
Every minor shift broadcast as a crisis.
Noise overwhelms signal.

People learn to skim. Important details drown in the deluge. In such environments, silence is not peace. It is withdrawal.

High-reliability teams learn to discriminate. What must be shared immediately. What can wait. What requires face-to-face conversation. What deserves a written record. They establish simple ground rules. If there is a safety concern, it is raised in the room, not left to fester in an inbox. If there is a decision, it is recorded with a name and a date, not buried in the middle of paragraph four.

Creating a Culture Where Information Can Surface

The emotional climate shifts when information flows well. People stop scanning for hidden traps. They do not waste energy trying to decode tone or second-guess motives. Clarity reduces friction. Friction consumes time. Time, in most operational settings, is not abundant.

There is also a moral dimension to information. When someone spots a risk and stays silent, the silence is rarely neutral. It usually arises from a learned pattern. Perhaps speaking up once led to ridicule. Perhaps bad news has historically been punished. Over time, people learn which truths are welcome and which are not. If bad news is unwelcome, it does not disappear. It simply goes underground.

The strongest teams reverse that pattern deliberately. Leaders ask for dissent.

‘What could go wrong?’
‘Who sees this differently?’

The questions are not rhetorical. When someone raises a concern, it is examined rather than swatted away. Over time, people learn that raising an issue is not career suicide. It is part of the job. That shift alone can prevent disasters.

Keeping Information Moving Across Teams

Communication is also temporal. Information has a half-life. A near miss discussed immediately yields insight. The same near miss dissected three weeks later becomes folklore. Memory fades. Detail erodes. Lessons become generalities. ‘We need to be more careful’ is not a lesson. It is a shrug.

Embedding brief reflection into regular routines tightens the feedback loop. At the end of a shift, a simple question: ‘What went well? What needs attention tomorrow?’ Two minutes. Nothing ornate. Yet that small act refreshes the air. It prevents stale assumptions from accumulating.

Inter-team communication adds another layer. Most teams are interdependent. What one does, another absorbs. When relationships across boundaries are weak, information stalls at the border. Frustration grows. Blame circulates.

‘They never tell us in time.’
‘They always change things at the last minute.’

The pronouns multiply. The oxygen thins.

Strong teams map their key connections. They clarify who needs what, how often, and in what form. They do not assume alignment. They construct it. Over time, those deliberate links become habitual. A quick call before a change. A heads-up before a shutdown. Small courtesies that prevent larger ruptures. None of this is glamorous. No one writes ballads about clear agendas. Yet the teams that treat information as infrastructure outlast those that treat it as etiquette.

Keeping the System Breathing

The practical benefit is straightforward. When information flows, decisions improve. When decisions improve, rework decreases. When rework decreases, morale rises because effort produces results rather than loops.

The personal benefit is subtler but no less powerful. Working in a team where information is shared openly reduces anxiety. You are not guessing. You are not bracing for surprises. You are part of the picture. That sense of inclusion matters more than most leaders realise.

So, if you want to strengthen a team, audit its ‘breathing’.

How do meetings start and end?
How are decisions captured?
How are risks surfaced?
How are actions tracked?
Where does information stall?
Where does it swamp?

Then adjust the pipes. Clear the blockages. Reduce the noise. Make commitments visible. Encourage dissent before it becomes dissent in private. You do not need a grand transformation. You need circulation.

Oxygen rarely gets credit. It simply keeps things alive. In high-reliability teams, information plays the same role. Ignore it and performance fades quietly. Design it well and the system breathes with ease.