# Poor Communication in the Workplace: Signs, Causes, and What You Can Actually Fix Canonical URL: https://headwayskills.com/knowledge/communication/poor-communication-in-the-workplace/ Markdown URL: https://headwayskills.com/knowledge/communication/poor-communication-in-the-workplace.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer How to spot the signs of poor communication in the workplace, tell whether it's you or the job, and repair the loops you can reach without any authority. ## Key facts - Title: Poor Communication in the Workplace: Signs, Causes, and What You Can Actually Fix - Category: Communication - Primary skill: Communication - Related skills: Teamwork, Working with Your Manager - Primary keyword: poor communication in the workplace - Source page: https://headwayskills.com/knowledge/communication/poor-communication-in-the-workplace/ ## What this page covers - How to spot the signs of poor communication in the workplace, tell whether it's you or the job, and repair the loops you can reach without any authority. - Practical guidance for poor communication in the workplace - How this topic connects to Communication ## Detailed explanation You reread the message twice and it still doesn't say when the thing is due. The update everyone else already seems to have seen never reached you. Poor communication in the workplace is the gap between what someone meant to convey and what the people around them actually understood, and it shows up as vague instructions, missed updates, unclear ownership, and feedback that never arrives. It is usually a broken process rather than a bad person. Almost everything written about it is addressed to people who can change company policy. This is written for the rest of us. ## What actually counts as poor communication in the workplace? It helps to stop thinking of it as bad talking. As TriNet puts it, poor communication is a mismatch between what someone intends to convey and what the other person understands, and Indeed's guidance for employers describes the same thing from the other side: it also happens through absence, when management simply doesn't pass on the information people need to do their work. That definition is more useful than it sounds, because it moves the problem out of personality and into a sequence you can inspect. Something was sent. Something was received. The two didn't match, or nothing was sent at all. Both of those have identifiable failure points, and some of those points are within your reach. ## What are the signs of poor communication at work? The signs that recur across sources are noticeably concrete. The Niagara Institute's roundup of warning signs, along with similar lists from theEMPLOYEEapp and Simpplr, keeps returning to the same handful: instructions that stay vague or shift without notice, the same misunderstanding happening twice, deadlines missed because an update never reached everyone, two people discovering they did the same piece of work, confusion about [who actually owns a task](/knowledge/teamwork/team-accountability/), feedback that never comes, rising stress across the team, and decisions being made or overturned in conversations you weren't part of. What's useful about that list is that every item is an event, not a judgment about a person. You can check for events. You cannot really check for "my team is bad at communicating." ## Is it me, or is it the workplace? This is the question underneath most searches on this topic, and it deserves a straight answer: usually it is neither, in the sense you're worried about. Writing in Psychology Today, the recurring pattern is that managers who communicate poorly are typically doing it unintentionally, often while thinking highly of the person they're leaving in the dark. Silence gets read as evaluation, so you end up unsure where you stand over something that was never about you. The practical test is the event list above. Count what actually happened in the last month rather than how it felt. If the same events keep recurring across different people, it isn't a verdict on you. If it's concentrated in exchanges you're part of, that's still not a character flaw, just a place to aim at, and it can be worth seeing [how your skills measure up](https://assessment.headwayskills.com/) rather than guessing at it from the inside. ## What causes poor communication in the first place? Four causes come up repeatedly, and none of them require anyone to be careless. The wrong medium gets used, so something sensitive or complicated [goes out by email](/knowledge/communication/how-to-write-effective-emails/) when it needed a conversation. Context that one person has been living inside for weeks gets assumed rather than stated. Ownership is never made explicit, so everyone assumes someone else is handling the update. And loops get left open, where a message is sent, no one confirms what they understood, and the mismatch surfaces later as rework. Add the unintentional-manager pattern to that list and you have most of it. Almost all of these are omissions rather than actions, which is exactly why they're so easy to miss and so easy to repeat. ## How does poor communication actually affect me and my work? More than people expect, and in a direction that isn't obvious. Among the figures compiled by the Niagara Institute, knowledge workers report that poor communication increases their stress (around 82%), reduces their productivity (around 81%), and lowers their job satisfaction (around 76%). The one worth pausing on is smaller: roughly 30% report lowered confidence. That is the effect most likely to be misread as evidence about yourself, when it is really the predictable result of working without clear information. You'll also see costs quoted in the trillions. Treat those loosely; they circulate through dozens of articles that cite each other rather than a published study. The self-reported effects are the part that matters here, and they're also the part you can act on, because the loops that produce them are smaller than the statistics make them sound. ## What do I do when my manager doesn't communicate? The advice that holds up here is to stop letting their style set the terms. Psychology Today's guidance for exactly this situation comes down to a few moves: don't wait for information to be volunteered, ask questions that actually require an answer, make contact cheap for them by keeping it short and prepared, and [be direct](/knowledge/communication/assertive-communication-skills/) about your proposed next step rather than asking for permission in the abstract. In practice that means bringing a short written list to [a scheduled one-on-one](/knowledge/working-with-your-manager/one-on-one-meeting-with-manager/) instead of catching them in a corridor, and asking "I'm planning to do it this way unless you'd rather I didn't" instead of "any thoughts on this?" The second version can be answered with silence. The first one can't, comfortably. ## How do I raise it without making things awkward? Name the event, not the person, and attach a request for next time. "I didn't see the change to the deadline until Thursday. Could you copy me when that thread moves?" is a specific, forward-looking ask that nobody has to defend themselves against. Compare that with "there's a communication problem on this team," which is true, unanswerable, and puts everyone on the back foot. The same principle covers asking for clearer instructions, which people avoid because they fear looking inattentive. Repeating your understanding back and asking for confirmation reads as diligence, not confusion, particularly when you do it in writing where it also becomes the record that prevents the next mismatch. ## What can I fix when I'm not the one in charge? More than the standard advice suggests. The fix lists on the highest-ranking articles, from PowerDMS to Atlassian, are written for people with authority: publish channel guidelines, adopt a central platform where tasks and deadlines are tracked, create regular touchpoints, explain the reasoning behind decisions rather than only announcing them. Every one of those scales down to one person. You can agree a channel convention with a single colleague. You can confirm a task in writing, with who asked, what exactly is wanted, when it's genuinely due, and what "done" looks like. You can request a standing one-on-one instead of hoping for ad-hoc contact. You can close your own loops by confirming what you understood. None of it fixes the organization, but it removes your name from most of the failure points. ## When is poor communication in the workplace a reason to leave? It is a real factor, not an excuse. In the workplace communication statistics compiled by Pumble, around 63% of people actively looking to leave say internal communication influenced that decision, and around 68% report time wasted because of it. Still, it's a poor first move. Give it a few months of closing the loops you can reach and see what changes, because that also tells you something worth knowing: whether the environment responds to clarity or absorbs it without trace. If it absorbs it, you have real information rather than a vague grievance, and you'll carry the repair habits into wherever you go next. ## The skills that make this easier to handle Read those answers together and a pattern shows up. Almost none of the moves involved speaking better. They involved choosing where a message goes, making ownership explicit, confirming what was understood, and being willing to raise something small before it becomes a pattern. Those are behaviors, and behaviors are learnable, which is why two people in the same badly-run team can have such different experiences of it. **Communication** is where most of this lives, and it's more specific than the word suggests. It covers deciding when something needs a conversation instead of a message, leading with your main point rather than burying it, being clear and direct without being blunt, and handling the tricky moments, like disagreeing or raising a problem, without damage. The value here isn't eloquence. It's that each of those is a discrete choice you make in a particular moment, and each one can be made better on purpose. **Teamwork** covers the failures that look like messaging problems but are really coordination problems: the duplicated work, the handoff that dropped, the update that stopped at someone's desk. Sharing what you know without being asked, making it clear who is carrying what, and respectfully holding people to what they committed to are the practical countermeasures. Most silent colleagues aren't difficult people. They're people whose part in the sequence was never made explicit. **Working with Your Manager** is the one people most often treat as fixed, on the assumption that a manager's communication style is simply weather. It isn't. Treating it as a partnership you can shape means asking for the standing conversation the environment isn't providing, making expectations explicit rather than inferring them, and asking for feedback rather than waiting to be given it. You have more standing to make those requests than most people believe. Knowing where you stand on these three is worth doing before you decide what's fixable, and the free Job Skills Test [reads all twelve work skills](https://assessment.headwayskills.com/) the framework treats as buildable, not only the three here. In practice it's often the least obvious of them that turns out to be the weak link. ## What this means for you Some of this probably already sounds like how you work. If you've ever repeated a request back to make sure you had it right, or copied someone into a thread because you could see they'd need it later, you've been doing the repair work already, just without a name for it. The rest of it is available on the same terms. Nothing here asks you to become a different sort of person; it asks for a handful of specific habits, applied in ordinary moments, and they get easier with use. That's worth knowing early, because the further you go and the more people your work touches, the more these habits carry, and the more expensive it gets to learn them under pressure. By reading this far, you've already done the part most people skip when they're frustrated at work: separating what happened from what it means about you. ## See where your skills stand What's left is finding out which of these to spend your effort on. The Job Skills Test is a **free** self-assessment of your work skills that takes about 7 minutes: you answer a set of questions and get a picture of where you stand across all twelve, including communication, teamwork, and working with your manager. It's not a verdict on you. It's a starting point that tells you which one or two skills would make the biggest difference to the situation you're in right now. **[Take the test](https://assessment.headwayskills.com/)** *Free, 7 minutes, and you can start right away.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? How to spot the signs of poor communication in the workplace, tell whether it's you or the job, and repair the loops you can reach without any authority. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Teamwork, Working with Your Manager. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/poor-communication-in-the-workplace/ Preferred summary: "How to spot the signs of poor communication in the workplace, tell whether it's you or the job, and repair the loops you can reach without any authority." ## Change log - 2026-07-07: Content collection version published.