# Giving Feedback to Your Manager Without It Backfiring Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/giving-feedback-to-manager/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/giving-feedback-to-manager.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 Giving feedback to your manager feels risky. Here are the five kinds of upward feedback, how to raise each one privately, and what actually makes it land. ## Key facts - Title: Giving Feedback to Your Manager Without It Backfiring - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Building Confidence - Primary keyword: giving feedback to manager - Source page: https://headwayskills.com/knowledge/working-with-your-manager/giving-feedback-to-manager/ ## What this page covers - Giving feedback to your manager feels risky. Here are the five kinds of upward feedback, how to raise each one privately, and what actually makes it land. - Practical guidance for giving feedback to manager - How this topic connects to Working with Your Manager ## Detailed explanation Giving feedback to your manager is one of the few conversations people rehearse for weeks and then never have. If you have been carrying something for a while, the method matters less than the dread suggests: treat it as an ordinary part of a [working relationship](/knowledge/working-with-your-manager/improving-your-relationship-with-your-manager/) rather than a one-off risk, raise it privately in your one-on-one, describe a specific behavior and the effect it had rather than the person, bring two or three examples, and stay on one issue. That is most of it. What is striking is how little of it is about wording — which is odd, because wording is almost the only thing people search for. ## Five kinds of feedback, five different levels of risk "Feedback for your manager" sounds like one thing. In practice it covers at least five, and they carry very different weight. Working out which one you are actually about to give is the fastest way to make the conversation less frightening, because two of these five are barely risky at all — and one of them often resolves what looks like a much bigger problem. ### Appreciative feedback This is telling your manager, specifically, what they do that helps you: shielding the team from noise, setting priorities you can actually act on, backing you in a room you were not in. It reinforces behavior worth repeating. It is the only kind with essentially no downside, and it is also the most skipped — managers give far more of it than they receive. It is worth doing for its own sake, but it also does something practical: it establishes that you comment on how the relationship works, so the first time you say something is not the first time you say something critical. ### Developmental feedback This is naming a pattern that is costing something — unclear priorities, decisions that arrive too late to act on, [oversight so close](/knowledge/working-with-your-manager/how-to-deal-with-a-micromanager/) that nobody can take ownership — along with its concrete effect on the work. This is the kind you probably came here for, and the only one carrying real relational risk. It is defined by a gap between what is happening and what the work needs, which is exactly why it requires evidence rather than an impression. An impression can only be agreed with or denied. A pattern can be examined. ### Working-relationship feedback This is about the mechanics between the two of you rather than about your manager's performance: how often you meet, how much context you need before starting something, how decisions get communicated to you, what you would like more or less of in your one-on-ones. It is a request about a shared process, not a judgment of a person, which makes it by some distance the lowest-risk route into a difficult subject. It is also underrated. A surprising number of things that feel like performance problems turn out to be process problems — you were never told the reasoning, so the decision looked arbitrary. ### Culture and values feedback This covers how your manager's behavior lands against the team's stated norms: how meetings include or exclude people, how credit gets distributed, whether policies are applied consistently. It is the only kind where the reference point sits outside the two of you, which both strengthens your standing to raise it and raises the stakes. Handled as an observation about a specific situation, it is legitimate. Handled as an accusation about character, it becomes something your manager has to defend rather than consider. ### Solicited and formal-channel feedback Sometimes the feedback has been asked for — a 360 review, an engagement survey, an anonymous tool, or a manager who directly asks what they should do differently. This is a difference of channel rather than of content. The invitation settles the question of whether you have permission, but it introduces a different constraint. Anonymous and survey channels remove the follow-up conversation, so there is no chance to clarify what you meant. Specific, actionable wording matters more there than anywhere else, because the words are all that arrives. ## Giving feedback to your manager: what actually makes it land Search results for this topic are dominated by example banks — pages promising 50, 72, even 125 sample lines. The volume tells you how real the demand is, but the format quietly makes a claim that does not hold up: that the difficulty is finding the right sentence. It usually is not. The same well-chosen line lands completely differently depending on where you say it, how much you have said before it, and how much evidence sits behind it. A few structural choices do more work than any phrasing. **Say it privately.** Nearly every source on this converges on [the one-on-one](/knowledge/working-with-your-manager/one-on-one-meetings/), and is emphatic about the negative case — not in a team meeting, not in front of colleagues. The reason is mechanical rather than about politeness: public criticism of someone with status forces them to defend that status in front of an audience, which turns a solvable issue into a confrontation. **Have the conversation, don't write it.** Written feedback strips out tone and expression, and it leaves a permanent record that can be reread later in a worse mood than the one it was written in. A video call is a reasonable substitute when in-person is not possible. **Describe the behavior, not the character.** Lattice illustrates the difference with a contrast worth holding onto: instead of "you're such a control freak," something closer to "in our last two projects, there was a lot of fine-grained oversight, and it reduced the team's ability to take ownership." The first is a claim about who someone is, and it can only be accepted or denied. The second describes something observable, and your manager can change it without conceding anything about themselves. **Bring two or three instances, not a file.** This is the standard that recurs across sources, and the reasoning cuts both ways. Fewer than two and it reads as a one-off. A page of them and it reads as a prosecution — which is the most common failure mode here, because people who have been silently collecting evidence for months tend to deliver all of it at once. **Raise one thing.** The usual reason given is that more is overwhelming. The practical reason is sharper: raise three issues and your manager will answer the weakest one and treat the conversation as handled. **Assume they are not doing it on purpose.** This is a preparation step rather than a courtesy. Going in with the assumption of good faith changes your own tone before you have said a word, and it is the cheapest available lever on how the first thirty seconds go. None of these are natural, and none of them are really about your manager — they are habits in how you handle a [difficult conversation](/knowledge/communication/difficult-conversations-at-work/) with anyone. If you are not sure which of them you already have, it is worth [seeing where your habits stand](https://assessment.headwayskills.com/) before you decide how much to raise. ## How much risk are you actually taking? Some. It is worth being honest about that rather than pretending the power difference is imaginary. The risk is real enough that anonymous 360 channels exist largely because named upward feedback carries it. And the structural picture explains why this feels so unfamiliar: by one industry count reported by Quantum Workplace, only around a third of organizations use upward feedback as a formal mechanism, against near-universal use of manager-to-employee feedback. So when you go to do this, you are usually not stepping into an established practice. You are inventing the behavior on the spot, which is why it feels like a transgression rather than a routine part of the job. But the risk is assessable, not unknowable. You have watched this person receive criticism before — from their own manager, from a client, from a peer in a meeting. You know whether they ask questions or get defensive, whether they revisit things later or let them drop. That evidence is worth more than any general rule about bosses, and it should shape how much you raise and how you open, not whether you say anything at all. ## The skills underneath a conversation like this Read back over what actually determines the outcome here and something becomes clear: the venue, the evidence, the framing, the timing. Very little of it is knowledge about feedback. Most of it is a handful of behaviors that show up whenever the stakes involve another person. **Working with Your Manager** is the one that changes the whole shape of the problem. Treat the relationship as a partnership with a shared purpose — where you deliver your part, where being honest is expected even when it is uncomfortable, and where disagreement is allowed — and upward feedback stops needing a special occasion. The standing one-on-one is already the channel. You are not asking for an exception; you are using the relationship as intended. **Communication** covers the part you came looking for, and it is more specific than "be tactful." Lead with your main point rather than circling it. Be brief. Choose a conversation over writing when the subject is sensitive and the relationship matters. Adapt to how this particular person takes in information — some want the context first, some want the issue named in the opening sentence and the reasoning afterward. **Building Confidence** is what gets you into the room. Confidence here is not a feeling you wait to arrive; it comes from having decided in advance exactly when and how you will raise it, accepting that you will be uncomfortable rather than postponing until you are not, and starting with something small before something large. Most people who search this have been putting the conversation off for weeks, which is the real obstacle — not the phrasing. Each of these is a behavior you can build rather than a temperament you were issued, and the free Work Skills Test covers all twelve that this framework treats as learnable — a straightforward way to see [which ones to build first](https://assessment.headwayskills.com/), including the two or three that would make this particular conversation easier. Some of this may already be familiar. You may find you handle one of these instinctively and have never had to think about it, while another has always felt like the hard part. That mix is normal, and it is also useful information — knowing which is which tells you where the effort actually belongs, and none of it requires becoming a different kind of person at work. The behaviors change; you do not. What is worth knowing is that this gets more consequential rather than less. The conversations that need honesty tend to get larger as your responsibilities do, and the habits you build on a small one now are the ones you will have available later. You have already done the part most people skip — you have thought carefully about how to raise this instead of either swallowing it or blurting it out. ## A quiet place to start Before you go anywhere near the conversation, there is something you can do on your own. The **free** Work Skills Test is a short self-assessment of the twelve work skills that shape how these situations tend to go — including how you work with your manager, how you handle a difficult conversation, and how you act when you are not feeling particularly brave. It shows you where you currently stand across all twelve and which one or two would make the biggest difference to you right now. Nobody sees the results but you. **Take the test** *Seven minutes, free, and nothing to prepare beforehand.* ## 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? Giving feedback to your manager feels risky. Here are the five kinds of upward feedback, how to raise each one privately, and what actually makes it land. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Communication, Building Confidence. ### 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/confidence.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/giving-feedback-to-manager/ Preferred summary: "Giving feedback to your manager feels risky. Here are the five kinds of upward feedback, how to raise each one privately, and what actually makes it land." ## Change log - 2026-07-07: Content collection version published.