Communication Culture: what it is and how to measure it

"We need to communicate better" is the most common line in team retrospectives and the least useful, because it names two different problems as one. The first is plumbing: does information reach the people who need it, in time, through channels they actually read? The second is voice: when someone has an opinion, a doubt or a different reading of the situation, does it get said and does it get heard? A team can have excellent plumbing and no voice, which is a well-informed team that never argues. It can have plenty of voice and bad plumbing, which is a team that debates passionately on the basis of different facts.

The Communication Culture KPI measures both halves, and it is built so you can tell them apart.

What Communication Culture means

In PEAKTEAMS, Communication Culture measures how openly and transparently a team communicates: whether information is shared, whether people listen to each other, whether different opinions are respected, and whether concerns can be raised. It is a Process KPI, which in the input-process-output model of Ilgen and colleagues (2005) means it describes how the team converts what it has (people, goals, resources) into what it produces. Communication is the process most other processes run on; coordination, feedback and conflict resolution all happen through it.

Why it matters

The team-effectiveness literature treats communication less as a KPI in its own right than as the carrier of every other process. Marks, Mathieu and Zaccaro (2001), whose taxonomy of team processes is still the standard reference, describe teams as cycling through transition phases (planning, goal setting) and action phases (monitoring, coordinating, backing each other up); every one of those activities is a communication act. Alex Pentland's 2012 Harvard Business Review article reported that, in the teams his group studied with wearable sensors, patterns of communication such as how much people talked face to face, how evenly contributions were distributed and how much people explored outside the team were the strongest predictor of team success. And Elizabeth Morrison's 2014 review of employee voice and silence documents the other half: people routinely withhold ideas and concerns when they expect the message to be unwelcome or futile, and organisations lose the information without ever knowing it existed.

The practical conclusion is uncomfortable. Most teams that score low on this KPI do not have a communication problem they can see. They have information they are not receiving and opinions they are not hearing, and both are invisible from inside the meeting.

What high and low look like in a real team

A team with strong Communication Culture has a place where decisions are written down, and people check it before asking. Status updates are shared before they are requested. In discussions, the lead speaks last on contested questions, and someone regularly says "I see it differently" without the temperature in the room changing. Misunderstandings get caught within a day because people ask "did you mean X?" rather than assuming. New members can find out how things work without having to know whom to ask.

A team with weak Communication Culture finds out about changes from other teams. Important messages arrive in a channel some people muted months ago. Meetings are reports, not discussions: one person updates, the others wait for their turn. Disagreement is expressed after the meeting, to allies, in the form of "I did not want to say this in front of everyone". Two people hold different versions of the plan for weeks and only discover it when the work does not fit together.

How PEAKTEAMS measures it

Communication Culture is one of the ten Process KPIs. The Snapshot survey asks two statements for it, one per half, on a five-point agreement scale.

The Deep-Dive survey asks thirteen items for this KPI: twelve positively worded statements that cover active listening, proactive updates, clarity, appropriate channels, whether important information reaches everyone, how quickly misunderstandings are cleared up, and whether concerns can be raised without hesitation; plus one reverse-scored statement, "Important information often reaches some team members late or not at all", which guards against members who agree with everything.

Results appear only once at least five team members have answered; the owner's own answer does not count. The report then plots this KPI's items on the Consensus Matrix, each item's average against agreement. For Communication Culture, low agreement is itself a finding: if half the team says information reaches them and half says it does not, the plumbing is fine for the people near the source and broken for everyone else, which is the most common pattern in teams split across locations or time zones.

How to improve it

Fix the half that is actually broken. The order below starts with plumbing because it is cheaper and because voice rarely improves while people are arguing from different facts.

1. Name one source of truth per topic. Most "nobody told me" complaints come from information that was shared, in a place the complainant does not look.
2. Write decisions down with the reasoning. A decision log that says why cuts the number of times the same question is reopened, and lets absent people catch up without a meeting.
3. Make updates push, not pull. A short written update on a fixed rhythm reaches everyone at the same time; relying on people to ask favours those who sit nearest the lead.
4. Ask for the dissenting view by name. "What would someone who disagrees say?" gives a reluctant member a safe way in, because they are reporting a view rather than owning it.
5. Have the lead speak last on contested questions. Once the most senior person has an opinion, the discussion tends to become a search for reasons to agree with it.
6. Close the loop on every concern raised. People stop raising concerns not when they are rejected but when nothing happens; a visible "here is what we did with it" keeps the channel open.

Related KPIs

The voice half of this KPI depends on Trust & Safety: nobody raises a concern in a team where concerns are held against them. The way disagreements are handled once voiced is measured separately by Conflict Navigation. And the plumbing half overlaps with Delivery Methodology, because a good way of working builds the information flow into the process rather than relying on goodwill.