# Downward Communication and Upward Communication at Work Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/downward-communication-and-upward-communication/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/downward-communication-and-upward-communication.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Downward communication sends instructions down the line; upward communication sends feedback back up. How each works, why upward stalls, and how to be heard. ## Key facts - Title: Downward Communication and Upward Communication at Work - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Influence - Primary keyword: downward communication and upward communication - Source page: https://headwayskills.com/knowledge/working-with-your-manager/downward-communication-and-upward-communication/ ## What this page covers - Downward communication sends instructions down the line; upward communication sends feedback back up. How each works, why upward stalls, and how to be heard. - Practical guidance for downward communication and upward communication - How this topic connects to Working with Your Manager ## Detailed explanation Downward communication is information that travels from managers to employees: instructions, policies, goals, work assignments, and performance feedback. Upward communication travels the other way, from employees to managers: progress reports, suggestions, concerns, and complaints. Both move along the same reporting lines, but they behave very differently once they get there. Most people notice the difference before they can name it. A message from above reaches you the same day; the point you raised three weeks ago has gone quiet. That gap is built into how the two directions work, and once you can see the mechanism, you can work with it. ## What is the difference between downward communication and upward communication? The comparison pages that dominate this topic, such as Key Differences and TermsCompared, line the two up along the same four axes. **Direction of flow.** Downward runs from superior to subordinate. Upward runs from subordinate to superior. **Nature.** Downward is directive. It tells people what is expected. Upward is participative. It offers a view that management can accept, question, or ignore. **Purpose.** Downward exists to give direction and keep everyone working from the same instructions. Upward exists to carry information back to the people making decisions. **Content.** Downward carries goals, policies, procedures, and assignments. Upward carries feedback, ideas, problems, and status. Those sources also note a difference in speed: downward tends to be faster and more formal, while upward is slower, because it passes through more hands that can choose what to do with it. ## What is downward communication at work? It is most of what arrives in your inbox and your team meetings. Study.com and Connecteam list the same content types across their coverage: organizational goals, policies and procedures, job assignments, work instructions, significant notices, and performance feedback. The reason so much of working life arrives as instruction is structural, not personal. Downward flow is how an organization keeps hundreds of people pointed the same way. Those sources credit it with organizational discipline, efficiency, clearer goals, easier delegation, and consistency across departments and locations. A company with a thousand employees cannot negotiate every procedure individually. So the volume of instruction coming your way is not evidence that your input is unwelcome. It is what a one-way channel is for. ## What is upward communication, and what does it look like in practice? Look at how the standard examples are described and something stands out. Indeed, Pumble, and BetterUp all list roughly the same instruments: suggestion boxes, employee surveys, manager-feedback surveys, employee polls, open-door policies, upward performance reviews, team meetings, and one-on-ones. Almost every item on that list is something the organization sets up and you wait for. The survey arrives when HR sends it. The suggestion box exists or it does not. One item on the list is different. The [one-on-one with your manager](/knowledge/working-with-your-manager/one-on-one-meetings/) is the channel you can use on your own initiative, at a cadence you help set, with a person who already knows your work. For a single employee, that meeting is not one upward channel among many. It is the main one. ## Why is upward communication harder than downward communication? Because of an asymmetry in how the two kinds of message are received. A downward message carries positional authority. It is expected to be acted on, and every management layer between the sender and you has an incentive to pass it along. An upward message carries no such weight. It has to earn attention from someone whose day is already full. That is not a flaw in your idea. It is the same message traveling against the grain rather than with it, and it means an upward message needs more preparation than a downward one to achieve the same effect. ## Why do instructions get distorted on the way down? Study.com and ClearInfo list distortion first among the disadvantages of downward communication, alongside slow feedback, interpretative problems, and lower morale when messaging feels purely authoritative. The mechanism is layering. Each management level that relays a message re-words it, compresses it, and adds its own emphasis. By the time a directive reaches the bottom of a long chain, it can differ noticeably from the one that was sent, without anyone intending to change it. This is directly useful. When an instruction reaches you and it seems odd, incomplete, or harsher than the situation warrants, transmission loss is the more likely explanation than bad intent. The practical response is to ask what the original intent was rather than guess at it, and to ask the person who sent it to you rather than infer from tone. ## Why does nothing happen when I send a suggestion up? Two well-documented mechanisms, neither of them a verdict on your idea. The first is gatekeeping. As material from Lumen Learning's principles of management course describes, messages moving up can be delayed, watered down, or stopped by middle managers. Yours may never have reached the person who could act on it. The second is filtering, and this one runs in the other direction. Sources on barriers to upward flow note that employees soften or omit negative detail to present a better picture, which leaves management with an inaccurate view of what is actually happening. Both mean the same thing for you. Informal asides get lost easily. A point raised with a named recipient, in a scheduled conversation, with a follow-up attached, survives the journey far better. If you are unsure how much of the problem is the structure and how much is how you tend to raise things, it is worth getting [a read on your habits](https://assessment.headwayskills.com/) before you conclude the door is closed. ## Is downward or upward communication more important? Neither ranks above the other, and the sources are unusually consistent about this. Sociabble and Status.net both describe organizational communication as a two-way street: downward provides direction, upward lets what employees actually see reach the people deciding. The more useful question is what breaks when one is missing. Without downward flow, people work hard on the wrong things. Without upward flow, decisions get made on an out-of-date picture, and the people closest to the problem watch it repeat. ## How do you raise something upward without it backfiring? Fear is named across the barrier literature as the single biggest obstacle to upward communication: [fear of saying the wrong thing](/knowledge/professional-behaviors/how-to-speak-up/), of overstepping, or of being the one who brought bad news. That hesitation is normal and widely documented. It is also a habit rather than a fixed trait, which means it can be worked on. A few things make an upward message land: - **Use the channel that exists.** Raise it in your one-on-one rather than in a corridor. - **Say what you want up front.** A decision, information, support, or simply awareness. An upward message with no clear ask is easy to nod at and forget. - **[Lead with the main point](/knowledge/communication/concise-communication/).** The context can follow it. - **[Bring a proposal](/knowledge/working-with-your-manager/bring-solutions-not-problems/), not only a problem.** Even a rough one gives the conversation somewhere to go. - **Follow up.** One check-in later turns a suggestion into a live item. None of that requires seniority or a different personality. It is preparation, and preparation is what upward messages need more of than downward ones. ## How is horizontal communication different from both? Horizontal communication runs sideways, between peers at the same level, and it is mostly about coordination: handing work between two people or two teams, sharing what you know, sorting out overlaps. There is no authority gradient in it, which is exactly why it usually moves faster than either vertical direction. It is worth knowing as the third flow, but it is not what determines whether your voice reaches a decision. ## What actually makes upward communication work Read back across those answers and a pattern appears. The definitions differ, but every practical difficulty landed in the same place: not the direction itself, but what one person does with the direction that runs against the grain. **Working with Your Manager** is where upward communication becomes concrete. Not an abstract arrow on an organizational chart, but a recurring conversation you prepare for, take notes in, and use to check that your understanding of priorities matches your manager's. The behaviors that make it work are specific: treat the relationship as a partnership rather than a chain of command, be honest even when honesty feels risky, bring solutions rather than only problems, and make your results visible so that what you send upward has something behind it. **Communication** decides whether the message survives the trip. State your main point first, be clear and brief, adapt to how the other person takes in information, and choose the right medium — a real conversation for anything sensitive or complicated, writing when the other person needs time or the exchange needs a record. Disagreeing well belongs here too, since that is where upward flow most often stalls. **Influence** — getting it and applying it — explains why two identical suggestions get different responses. Preparation matters: understanding what is in it for the person receiving it, knowing how the decision actually gets made, keeping the pitch simple, being honest about the drawbacks, and following up rather than assuming silence is a no. Underneath all of it sits a reputation for delivering what you said you would, which is what makes management read your input as signal. Those three sit inside a set of twelve work skills that this framework treats as learnable rather than innate — every one of them a set of habits, not a personality type. The free Work Skills Test covers all twelve, so if you want to know [which to build first](https://assessment.headwayskills.com/), that is the quickest way to find out. Some of this probably describes things you already do. You may already prepare before a one-on-one, or already sense which points need a conversation rather than a message. The parts that feel less familiar are not fixed. Preparing an upward message, saying the uncomfortable thing clearly, following up without nagging — these are practiced, not inherited, and you can build them while remaining entirely yourself. What is worth knowing is that they count for more as your responsibilities grow. The more your work depends on decisions made above you, the more it matters whether your view reaches those decisions. You read past the definitions to the part about actually being heard. That is the part most people skip. ## See where your own skills stand The one thing left is to find out which of these to work on first, rather than guessing. The Work Skills Test is a **free** self-assessment of your work skills. It gives you a picture of where you currently stand across all twelve, including the three in this article, and shows which ones would make the biggest difference to you right now. You answer, you get your profile, and you have a concrete place to start. **[Take the skills test](https://assessment.headwayskills.com/)** *Free. About 7 minutes. Covers all twelve work skills.* ## 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? Downward communication sends instructions down the line; upward communication sends feedback back up. How each works, why upward stalls, and how to be heard. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Communication, Influence. ### 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/working-with-your-manager.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/working-with-your-manager/downward-communication-and-upward-communication/ Preferred summary: "Downward communication sends instructions down the line; upward communication sends feedback back up. How each works, why upward stalls, and how to be heard." ## Change log - 2026-07-07: Content collection version published.