Effective Workplace Communication

Communication is mostly habit, not budget

In the years I have edited workplace-communication material for this site, one pattern has held up better than almost anything else I have published: the teams that communicate well rarely have the fanciest tools or the biggest budgets. They have habits. Someone decided that decisions get written down, that meetings need a reason to exist, that bad news travels fast and honestly. None of that costs money. It costs the willingness to be a bit less comfortable.

The McKinsey Global Institute put a number on this in 2012: organizations whose employees are well connected through clear information-sharing are 20 to 25 percent more productive than poorly connected ones. What strikes me is what the finding does not say. It does not say the productive companies communicate more. They communicate with structure, so different message types have a home and nobody is drowning in parallel threads about the same decision. When that breaks down, projects stall, work gets done twice, and good people tire of the friction and leave.

The gap between a high-performing team and a struggling one almost never comes down to raw talent or the software they bought. It comes down to norms. Amy Edmondson's 1999 study of 51 work teams, published in Administrative Science Quarterly, found that teams willing to admit mistakes and ask hard questions learned faster and performed better, and that the deciding factor was whether people felt safe enough to speak. She called it team psychological safety, and two decades of research have not dislodged it. Tools do not create that safety; the people running the team do. Active listening sits underneath all of it.

What has changed in 2026

The biggest shift is that the team is rarely in one room anymore. Most workers now split the week between home and office, and a smaller group works wherever they happen to be. The consequence shows up in nearly every company I talk to: the channel that reaches the person at headquarters does not reach the one on a factory floor or three time zones away. So the job has quietly changed from distributing a message to designing a system that carries it through several channels and still lands for everyone.

And then there is AI, which I have mixed feelings about. The useful side is real: tools now transcribe and summarize meetings, translate across languages, and flag when a team's tone is sliding toward disengagement. The other side is that AI generates content faster than people can absorb it, so the technology promising to cut the noise often adds to it, and people reasonably wonder who is reading what a tool records. The efficiency is worth having, but it does not replace empathy, active listening, or the judgment to know when a human needs to deliver the message in person.

Building a culture where people actually talk

Culture is the part nobody can buy and everybody underestimates. Patrick Lencioni, in his 2002 book The Five Dysfunctions of a Team, put trust at the very bottom of the pyramid, and I think he was right to. When people do not trust each other, they protect themselves instead of doing the work, and a team that cannot trust will not argue productively, commit, or hold each other accountable. You can install the best chat tool in the world on top of that and it will not help.

So the work starts with whoever is in charge. Managers who say "I am not sure yet" out loud, who ask for feedback and do not punish the person who gives it, who admit a call they got wrong, build the safety that lets everyone below them speak honestly. That matters more than it sounds, given Gallup's repeated finding that managers account for about 70 percent of the variance in team engagement. The manager is the weather. Regular check-ins and decisions written down where people can find them cut the friction, and our workshops give teams room to practice.

Picking the right channel for the message

A lot of communication breakdowns are really just channel mistakes. Hash out a thorny strategy question over chat and you get a mess of half-arguments nobody can follow. The McKinsey Global Institute found in its 2012 social-economy study that knowledge workers spend about 28 percent of the week on email and close to another fifth just looking for information. A surprising amount of that is recoverable, not by working harder, but by agreeing on which channel does what.

The teams that get this right write it down. Call it a channel charter, or just a wiki page saying decisions go here, quick questions there, and this is how long before you should expect an answer. Hand it to a new hire and you save them weeks of guesswork; our business email guide covers the email half in detail. It also pays to default to public. A few years back I went through the messaging data for a fully remote company: only about one in eight messages landed in a channel anyone else could see. The founder had no idea most of what the company knew lived in private conversations. We added one rule, "default to public," and within a month the searchable knowledge had roughly doubled.

How to run a meeting people do not resent

Meetings are where good intentions go to die. They are expensive, everyone complains about them, and we keep scheduling more. Harvard Business Review reported that 71 percent of senior managers find their meetings unproductive, while the average professional now loses something like 23 hours a week to them, up from under 10 in the 1960s. The fix is to be ruthless about which ones happen and disciplined about how they run.

Start by asking whether the meeting needs to exist at all, the step everyone skips. If the goal is just to tell people something, a written update does it better, since people can read it when their head is clear. A meeting earns its place when you need real-time give and take, a decision made together, or feedback in the moment. Otherwise, cancel it and write the email.

If it does need to happen, send a real agenda the day before: what you will cover, roughly how long each item gets, what you want out of it, and anything to read first. Give them that and they arrive ready to contribute rather than forming opinions on the spot.

Be stingy with the invite list. Everyone in the room should know something the group needs, need something the group has, or be the one making the call. Every extra body is salary spent and another half-listener. For a real decision, five to eight people is about the ceiling.

Pick someone to run it. A facilitator keeps time, drags the conversation back when it wanders, and makes sure the quiet person with the right answer gets heard. Without one, the loudest voice wins. I rotate the role, since running a meeting well is a genuine leadership skill.

Then write down what happened while it happens: decisions made, who owns which next step, by when, and anything still open. Send it out within the hour. This one habit, which costs about ten minutes, kills the "wait, I thought we agreed on the other thing" argument that haunts teams with sloppy follow-through.

One story makes the point. At a 200-person tech company I looked at, people sat in roughly 62 hours of meetings a month and rated them, on average, 2.1 out of five. The founder's instant reaction: "But we need those to stay aligned." We cut about 40 percent of the recurring ones for a structured written update. Six months on, alignment scores had gone up, not down, and meeting hours had dropped to 38.

Feedback, the part everyone dreads

Feedback is how communication actually turns into better work, and almost nobody enjoys either end of it. Giving it feels risky. Receiving it feels worse. And a lot of it does not even help: Gallup has found that only about a quarter of employees strongly agree the feedback they get helps them do their job better. Three out of four people are getting feedback that does not move them. That is not a people problem. It is a delivery problem, which is fixable.

The structure I trust most is SBI, which the Center for Creative Leadership built and which has held up because it is simple. You describe the situation, the behavior you actually saw, then the impact: "In yesterday's client meeting, you ran the financials without the comparison numbers we had agreed on. The client asked questions we could have headed off, and we went 20 minutes over." It stays on the observable thing rather than the person's character, so the listener can hear it without bracing. One rule I will not bend on: deliver anything that carries weight in person or on video, never over text. When the feedback touches a live disagreement, our conflict resolution guide goes further.

Taking feedback well is the harder skill, and the one people work on least. The instinct is to explain, defend, or quietly minimize, and all three stop you from hearing the thing. The discipline that helps me is dull but it works: do not respond for a beat, just take it in. Ask a question or two to be sure you understand the behavior and the impact they mean. Thank them even if part of you disagrees, because they took a risk to say it. Then decide later what is worth acting on, once you are not defending yourself in real time. That kind of listening turns a confrontation into something you can use.

When everything is changing at once

Restructurings, mergers, a new boss, a pivot, layoffs. These are the moments when communication matters most and goes wrong most. A large share of major change efforts stall or fail outright, and when people study why, communication keeps turning up near the top of the list. It makes sense given what change does to people. It threatens what they have built their working life around, and the natural response to a threat you do not understand is to resist it. Good communication does not remove the threat. It removes the fear that comes from not knowing.

The mistake I see again and again is treating the all-hands as the communication. One announcement, leadership feels they have told everyone, done. They have not. There is an old rule of thumb that people need to hear a significant message several times, through several channels, before it sinks in, and my experience says that is about right. The town hall plants it, the team meeting reinforces it, the one-on-one makes it personal, and the written FAQ catches the questions people are too nervous to ask aloud. Each pass lets someone absorb the change emotionally, not just intellectually. Leaders who think one clear message is enough are usually the ones whose change efforts fall apart. Our leadership communication guide and a workshop on change scenarios are worth the time beforehand.

Frequently Asked Questions

What does poor communication actually cost a company?

More than most leaders realize, and rarely as a budget line. The widely cited Holmes Report figure runs to tens of millions a year at large firms, but the mechanism convinces me more than the dollar amount. It shows up as the project that slipped because two teams each assumed the other had it, the work done twice, and the good people who tire of the friction and leave.

Which communication channel should I use for what?

It depends on the message, which is the whole point. Email is for things you want on record or anything external. Chat handles quick questions. When something is genuinely complicated, get on a video call, and save in-person for the sensitive stuff, including most conflict. The biggest improvement, though, is not picking the perfect channel each time. It is agreeing as a team on which channel does what.

How do you make a hybrid team communicate well?

The rule that matters most is that nothing important should live only in someone's memory or a closed-door chat. Write decisions down where the team can find them, record meetings so people in other time zones are not left out, and be explicit about reply times. In meetings, actually pause and pull your remote folks in, or the room dominates while the screen goes quiet.

What is the SBI feedback model?

SBI stands for Situation, Behavior, Impact, and it came out of the Center for Creative Leadership. You name when and where it happened, what you actually saw the person do, and the effect it had. Sticking to what you observed, rather than what you assume they intended, gives the other person a description to hear rather than a verdict to brace against.

What is the secret to running a good meeting?

Honestly, asking whether you need the meeting at all. If you are just passing along information, send a note and give everyone their time back. When a meeting is warranted, the rest is simple: an agenda sent ahead, only the people who need to be there, someone running the clock, and a written summary of decisions afterward. None of it is hard; it just takes the discipline to do it every time.

What role does AI play in workplace communication now?

A growing one, and a double-edged one. The useful part is the grunt work: AI now transcribes and summarizes meetings, translates across languages, and drafts the routine messages nobody enjoys writing. The catch is that it produces content faster than anyone can read it, so the tool that promises less noise often adds more. AI is a fine assistant for the mechanical side, but empathy and real listening stay on us.

How do you deliver bad news to a team?

Quickly and straight, which is harder than it sounds, because the instinct is to soften and delay. Lead with the actual news instead of burying it. Explain why, since people handle a hard decision far better than an arbitrary one. Acknowledge that it lands badly. Then give concrete next steps, leave space for questions, follow up with whoever it hits hardest, and put it in writing.

The advice here draws on published research and patterns I have seen hold up across many teams, but your own organization's policies come first in any specific case. Read our terms.

Editorially reviewed: May 24, 2026