28 October 2026 · 12 min read

Poor communication in the workplace: why one more update does not fix it

The note went out on Thursday and everybody read it. Nobody read the same one.

That is the odd thing about a communication breakdown. The sender can see that the message left. What arrived stays in other people's heads.

The note Ruth is pleased with

Ruth is managing director of a firm of about a hundred and forty. On Thursday afternoon, straight out of the board meeting, she sends everyone two lines: "We will prioritise the Northfield account for the next quarter. Please plan accordingly." It is short and decisive, and she is rather pleased with it.

On Monday she walks the floor. Femi in design has cleared his week for Northfield and told two other clients their dates will slip. Imogen, who runs delivery, has changed nothing: to her, "prioritise" means Northfield gets the first call when two jobs collide. Ruth meant a third thing, which she explains to both of them in the corridor. Northfield's dates are fixed, and anything that threatens them comes to her.

Nobody was careless. Femi acted on the note and so did Imogen. The word arrived without the board meeting that gave it its meaning.

Ruth's first thought is to send another note, a longer one.

How common is poor communication in the workplace?

Ruth is invented. The surveys are not.

In the CIPD's 2026 survey, 26% of employees rated their manager poor or very poor at keeping employees informed of management discussions or decisions, and 41% rated them good or very good (CIPD, Good Work Index 2026: Survey report, July 2026, Figure 41). That is about being kept informed by a manager, which is Ruth's note and Imogen's relaying of it, a decision travelling down a line.

As of August 2025, 16% of US employees thought their organisation's leadership communicates effectively, in Gallup's leadership indicator (Gallup, Global Indicator: Leadership and Management, August 2025). It covers US employees only, and Gallup's page names no sample size or comparison group.

Both measure what people think. Neither says which messages failed or why, and neither can tell you that Ruth's Monday was typical. They are a reason to look, no more.

The numbers a sender actually gets are worse at this. The average internal email is opened by 76% of its recipients and clicked by 9% (ContactMonkey, Internal Email Benchmark Report 2026, 19 June 2026, updated 1 October 2026). That is a vendor's data, from more than 255,000 internal campaigns. Ruth's note would have looked fine on that dashboard. Femi opened it, Imogen opened it, and both acted on it. An open rate tells you the message reached an inbox. It has nothing to say about what reached the reader.

What causes communication breakdowns at work?

Ruth is in the position of Elizabeth Newton's tappers. In her tapping study at Stanford, people tapped out the rhythm of a well-known song and expected the listeners to name it about half the time. Almost none could, because the tappers heard the tune in their heads and the listeners heard only taps (Newton, Stanford dissertation, 1990). For Ruth, "prioritise" came with the board meeting attached. For Femi it was taps.

Writing adds a second gap. Justin Kruger and Nicholas Epley's research on email found that writers overestimate how clearly their tone comes across to the reader.

Words that set direction are elastic too. The intelligence analyst Sherman Kent found that people who read the same estimate took a phrase like "a serious possibility" to mean very different odds. Kent studied intelligence estimates, not office email. The step to "prioritise", "soon" and "urgent" is my reading.

Then there is how much you send. A meta-analysis of team communication and performance found that communication quality had a significantly stronger relationship with team performance than communication frequency (Marlow, Lacerenza, Paoletti, Burke and Salas, Organizational Behavior and Human Decision Processes, 2018). It studied teams, so a company-wide note is a step beyond it, and it cannot say how much communication is the right amount.

The detail inside that study is the part worth keeping. Of what it measured, information elaboration had the strongest link to performance and both frequency measures the weakest. Elaboration is the back-and-forth of working out together what something means. That is what Ruth's two lines left out: nobody asked anything, so "prioritise" was never worked out at all.

Nothing here counts which failure is commonest. My reading is that the message that was sent and never arrived hides best. The sender has a sent message to point to, and the confusion sits with the people who received it.

The signs of a communication breakdown a manager can see this week

Nobody reports these, because each one looks like an ordinary annoyance on its own. Look for any two.

• The same decision gets made twice, in different rooms. Both rooms think they were first.
• "I thought you meant" is heard most weeks. It has stopped being an apology and become a way of starting a meeting.
• A handover needs a meeting before anyone can use it. The document exists. So does the call to explain it.
• Long threads end with nobody owning what happens next. Everyone read it, and everyone believes the follow-up is someone else's.
• People forward a message with "can you decode this?" That note, not the original, is now the real update.
• People wait for the corridor version. Nobody acts on the note until someone has said what it really means, which is the tell of a stated priority and a real one drifting apart.

Who pays when a message never arrives

Tuesday, ten past nine. Anya, a project coordinator in Imogen's team, is on the phone to one of the two clients Femi wrote to. The client wants to know why their date has moved. Nothing in Anya's plan says it has, because Imogen changed nothing. She says she will call back, and goes to find out which of her colleagues is right.

The sender rarely pays for a note like Ruth's. Ruth lost ten minutes in a corridor. Femi lost a week. Anya is explaining a decision she was never in the room for to a client who has started to wonder who is in charge.

The work pays too. In PMI's 2013 survey of project professionals, ineffective communication was a contributing factor in 55.7% of unsuccessful projects, which the report puts at 21.0% of all projects (Project Management Institute, Pulse of the Profession In-Depth Report: The High Cost of Low Performance: The Essential Role of Communications, May 2013, Figure 2). It is thirteen years old and about project delivery, and "contributing factor" is as far as it goes.

The cost I would worry about most is slower, and no survey counts it. Femi did what the managing director's note told him to, and it cost him a week and two awkward calls. Next time he will wait. So will everyone he tells. My reading is that each note that misfires teaches people to treat the next one as a draft until a corridor confirms it, and a firm of a hundred and forty then moves at the speed of its corridors.

Why more updates do not fix a communication breakdown

Ruth has three easy moves, and each turns up the volume at her end.

An all-hands gets the same word to a hundred and forty people at once. The question that matters, "what do I do on Tuesday?", now has to be asked in front of all of them.

A weekly update email is more frequency, written from the same head. Marlow and colleagues found quality mattering more.

A longer announcement can help. A sentence on what "prioritise" does not mean would have saved Femi's week. But length is still the sender's decision, made without seeing what arrived.

What all three lack is a way back, a route for what the receiver understood to reach the person who wrote it while it is still cheap to correct.

How to improve communication at work, starting tomorrow

None of this needs a product.

Test the draft on someone who was not in the room

Before the next change of plan goes out, show it to one person who missed the meeting and ask two questions. "What would you do differently on Monday because of this?" and "What would you assume it doesn't change?" Where their answer differs from yours, edit the note, not the reader. It borrows a receiver's ears before the message commits, which the tappers could not do.

Define the word that carries the weight, and say what stays the same

Find the one or two words the note depends on - prioritise, soon, urgent, restructure - and put what they mean beside them. "Prioritise: Northfield's dates are fixed; other clients keep theirs unless I have spoken to you." Then one line on what is not changing. Kent's readers each filled the gap with their own odds, and Femi filled his by clearing his week.

Ask the people who will relay it to say it back, the same day

A team lead who tells their team "Ruth wants us on Northfield" has become the message. Ask each of them how they will put it, in two sentences. This is the read-back that aviation and medicine use to confirm an instruction, because a misheard word costs too much to leave to chance.

All three have to happen at the moment you feel finished, which is the moment you press send.

Four questions about communication at work

What are the main causes of poor communication at work?

The main cause is usually the gap between what the sender knows and what the message carries, not a shortage of messages. The sender hears the meeting behind the words, and the reader gets only the words. Elastic terms such as "soon" widen the gap, and with no route back nobody finds out in time.

How much communication is too much?

Nobody has a number, and the research here does not offer one. Marlow and colleagues found quality mattering more than frequency, which is not the same as less being better. A useful test is whether a reader could say what they will do differently. If they could not, the message added nothing at any volume.

Is poor communication a leadership problem or a team problem?

It is usually both, which is why fixing one end rarely holds. A leader can write a clearer note, and it still has to pass through a manager who restates it and a team that never says it back. Treat it as a property of how the line passes things on, not of anyone's eloquence.

How do you tell someone they communicate poorly?

Describe one message, never their character. Name the moment, what was written and what it caused for you: "Thursday's note said prioritise, I read it one way and Imogen another, and I lost the week." That gives them something to change. "You are a poor communicator" gives them only something to argue with.

How MeaningFuel helps with poor communication

A daily email is a bold thing to offer at the end of a piece on too many messages, so take the objection as read. It is one more message. The case for it is that it is short, that it gives the reader something first, and that it asks them something back, which is more than Ruth's note did.

The daily insight

A company chooses the values and skills it holds, and each working day everyone gets one short insight on one of them. Three bear on this: Communication, which is saying things clearly and listening well so that meaning arrives intact; Feedback, which is giving honest comment on work and asking for it; and Collaboration, which is working jointly across teams and differences. In an ordinary week a reader might meet a line on how a message sounds from the other end, and another on why people stop asking. A communication breakdown is a problem, and a problem cannot be chosen for the daily culture. A team that has one gets a module.

The module: Clear Communication

Clear Communication is a module for a team where "I thought you meant" is heard most weeks. A module is a short course of daily lessons for a team's named people. Whoever runs the account or the team books it, it invites the team, and those who join get one short lesson each working day, ten in all.

The lesson on the read-back opens with two colleagues who finish a conversation each sure the follow-up is theirs. The move is the one above: say back what you heard, in your own words, before you act ("so I draft it, you review it before it goes out"), and say back the words that carry weight, so that "soon" becomes "before the end of the week". In the last lesson the team is asked to pick one norm to keep, the read-back, a one-line decision written where everyone can find it, or agendas written as questions, and to say where it lives. It draws on research by Elizabeth Newton and Sherman Kent.

Around those sit the habits Ruth's firm is short of: a handover that says what is being passed on, where it can be found and that it landed, and a hard note said in a conversation before it is sent, because tone travels badly in writing. The team lead runs two ten-minute debriefs from a written guide, and before the first asks the team for one specific note on their own work.

What Ruth could read, and what no dashboard can

Insights shows how much of a team takes part and how the insights land, pooled, with nobody named. Ruth could see whether design and delivery are both reading in the mornings. She could not see whether Femi and Imogen mean the same thing by "prioritise", and no dashboard could, which is the whole argument of this piece. The only instrument for that is somebody saying it back. So read Insights as a sign of whether the habit is alive, never of whether the last note arrived.

What it does not do

It works at the level of a team's habits. It will not write Ruth's next note or change what her board decides, and it promises no outcome. It puts the read-back in front of the team every working day for two weeks.

Back to Thursday

Ruth's next note can be as short as the first. It goes to someone who missed the board meeting before it goes to everyone, and on the day Imogen tells her how she will put it to her team. That takes a few minutes before sending, and it would have kept Femi's week.

• Poor Communication
• Communication Breakdown
• Clear Communication
• Leadership
• Workplace Culture