# Negative Feedback to Your Manager: Examples and How to Say It Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/negative-feedback-to-manager-examples/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/negative-feedback-to-manager-examples.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 Real examples of negative feedback to a manager - unclear expectations, micromanagement, workload, recognition, decisions - plus how to say it safely. ## Key facts - Title: Negative Feedback to Your Manager: Examples and How to Say It - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Building Confidence - Primary keyword: negative feedback to manager examples - Source page: https://headwayskills.com/knowledge/working-with-your-manager/negative-feedback-to-manager-examples/ ## What this page covers - Real examples of negative feedback to a manager - unclear expectations, micromanagement, workload, recognition, decisions - plus how to say it safely. - Practical guidance for negative feedback to manager examples - How this topic connects to Working with Your Manager ## Detailed explanation Looking up examples of negative feedback to a manager is usually a sign that you already know what the problem is. You just don't want the sentence to come out wrong, and the person it lands on is the person who writes your review. Most workable negative feedback to a manager follows one shape: name the specific behavior, describe its effect on the work, then ask for something concrete. "When the brief changes mid-week, I lose about a day — could we settle the scope on Mondays?" The examples below apply that pattern to the five areas managers most often get feedback about. Which of those five you are actually in matters more than the wording does. ## What makes negative feedback to a manager land The sentence is the last step, not the first. Three choices ahead of it do most of the work. **Choose the setting on purpose.** Deel's guide to negative feedback sets out the conditions most sources land on: a private conversation, a calm delivery, and a focus on behavior you can point to rather than judgments about the person. Your existing [one-on-one](/knowledge/working-with-your-manager/one-on-one-meeting-with-manager/) is usually the right slot — already private, already about the work, already recurring, so raising something there registers as a normal agenda item rather than an escalation. **Talk about the effect on the work, not the failing.** Business Management Daily's advice for upward feedback is to anchor the point in operational terms: if you are not getting enough information to do a task correctly, say what that does to how long the task takes. A manager hearing a criticism of themselves has to decide whether to defend; a manager hearing a specific cost to delivery has something to fix, and fixing it is their job. **Use "I" for what you experienced.** Feedback phrased as "you always" reads as an accusation and invites a defense, which is why upward-feedback guides such as Workhuman's recommend the "I" framing instead: *I felt overwhelmed when deadlines were changed without notice.* The information is identical; the verdict has been removed. Then close with something concrete — a request, an option, or a real question. The examples that circulate most widely all do this. The Muse suggests meeting repeatedly rejected input with "I noticed you didn't consider my last three campaign ideas. How can I make my pitches more effective?" The criticism is still fully there; it now arrives with a route forward, which is most of the distance between a complaint and feedback. One popular technique deserves a caution. The feedback sandwich — compliment, criticism, compliment — turns up on nearly every list on this topic, but the padding tends to bury the point. CareerBuilder's advice runs the other way: cut wavering openers like "it's not a big deal, but", because they invite your manager to agree that it isn't. ## Negative feedback to a manager: five areas, with examples The upward-feedback surveys employers run tend to measure the same small set of dimensions — communication clarity, coaching and development, recognition, decision-making, trust, and [workload](/knowledge/time-management/prioritise-workload/). That set is a useful map, because vague discomfort is hard to say out loud and a located problem is not. "Something feels off between us" has no answer. "I need clearer acceptance criteria" does. ### Communication and unclear expectations The most common category, and the most fixable, because it is about information flow rather than intent. You cannot tell what finished is supposed to look like, direction changes mid-task, or a draft sits unanswered while everything behind it waits. Try: "I'm not always sure what you want the finished version to look like, so I end up guessing and reworking. Could we spend five minutes at the start of each piece agreeing what done means?" Or, on response times: "When a draft sits for a week, I hold the work behind it. Would it help if I flagged which ones are blocking something?" The fix here is a process rather than a change of character, which makes this the safest area to start with if you have never given your manager feedback before. ### Autonomy and micromanagement The riskiest one, because any direct version implies something about trust. The circulating examples handle it by asking what would earn more room rather than by naming the behavior. The Muse offers: "Sometimes I feel like you don't trust my abilities. Are there steps I can take to show you my work and make you feel more confident, or is there anything I could improve?" A flatter version, if that one feels too exposed: "I'd like to take the next one through to a full draft before we review it. Would you be comfortable trying that once and seeing how it goes?" Both put you and your manager on the same side of the question, which is the framing sources keep returning to here: [close oversight](/knowledge/working-with-your-manager/how-to-deal-with-a-micromanager/) usually comes from wanting the work to be right, and more independence is what builds a team able to carry that weight itself. ### Workload, deadlines, and priorities The one area where what you are asking for is literally part of your manager's job, which means it barely has to be framed as criticism at all. One of the most-repeated examples across these guides is simply: "I have a lot on my plate right now. Can you help me prioritize, or is there some wiggle room on deadlines?" Where the problem is shifting dates rather than volume: "I felt overwhelmed when the deadlines moved without notice. Could we agree that changes landing after Wednesday move the delivery date with them?" Neither version asks your manager to admit they overloaded you. Both ask for a decision they can make on the spot. ### Recognition, feedback, and development Easy to get wrong, because it can sound like fishing for praise. Anchor it in visibility instead: "The migration work hasn't come up outside our team. Could we include it in the next department update?" On feedback that only arrives in [formal reviews](/knowledge/working-with-your-manager/performance-review-preparation/), a widely used phrasing: "Your feedback during reviews is detailed. More frequent, informal check-ins would keep performance conversations ongoing and less stressful." That second one tends to open a follow-up you may not be ready for — what, specifically, do you want to get better at? A development conversation goes further when you can name something precise rather than agreeing that growth sounds good, and a free look at [where your work skills stand](https://assessment.headwayskills.com/) is a quick way to walk in with an answer. ### Decision-making and follow-through Decisions that arrive late, reverse after the work has started, or get made without the people who will carry them out. Here the cost is most countable, so keep the feedback to what you observed and what it cost: "When the scope changed after we'd started building, we lost about two weeks of work. Could we hold the kickoff until it's signed off?" Restrict this one to decisions that touched your own work directly. Feedback about decisions you heard about secondhand is much harder to make concrete, and concrete is what survives a defensive listener. ## What not to say - **Absolutes.** "You always" and "you never" are rarely accurate, and the inaccuracy is what gets argued about instead of the point. - **Character verdicts.** "You're a micromanager" cannot be acted on. "I'd like to take the next one further before review" can. - **Speaking for people you haven't asked.** "Everyone feels this way" turns your feedback into a claim about the team that your manager may go and check. - **Dilution.** Openers that pre-apologize invite your manager to agree it isn't worth discussing. - **The saved-up list.** Six grievances at once cannot be made specific and will read as an ambush. Raise the one that costs you most, alone. And keep it out of group settings entirely. On that, the sources are unanimous. ## After you have said it If your manager hears you out or agrees to come back to it, thank them for the time — Workhuman's guidance treats that as part of the act rather than a nicety, because it strengthens the relationship you were protecting. Then agree a check-in point, and watch what changes. Sometimes nothing does. That is information too, and better acquired from one well-delivered piece of feedback than from months of guessing. ## The skills that make this conversation easier Read back over those examples and the wording is the smallest part of any of them. What does the work is a judgment about what to raise, a plain way of saying it, and enough steadiness to start. Three separate things, each of which can be worked on. **Working with Your Manager** is the one that reclassifies the whole situation. Treated as a partnership rather than a hierarchy, disagreement stops being a breach and becomes part of delivering your side of a shared purpose — being honest is part of the job, including when it feels risky. Practically, it shows up as the things that make the examples above work at all: raising it in the standing one-on-one rather than ambushing them, preparing what you want to say, bringing a proposal rather than only a problem, and keeping the relationship focused on the work rather than the personalities. **Communication** covers the mechanics underneath every phrasing on this page. Expressing disagreement and giving feedback are among the genuinely tricky situations to handle, and the principles behind them are visible in the good examples: be clear and direct, be brief, lead with the main point rather than circling it. It also settles a choice most people make without noticing — a sensitive subject belongs in a conversation, not in writing. **Building Confidence** is usually the actual bottleneck. Most people reading this already know roughly what they want to say and still haven't said it. Confidence here gets built by acting rather than by waiting to feel ready: decide in advance exactly when and where you'll raise it, keep the first attempt small and specific, and accept that the discomfort will be present rather than trying to remove it first. Only the first conversation is difficult in the way you're imagining. None of the three is a personality type you either got or didn't; they're behaviors, and they can be measured. The free Job Skills Test gives you [a read on all twelve](https://assessment.headwayskills.com/) work skills the framework covers, these three included — a fast way to find out whether what's keeping this conversation on your desk is the judgment, the wording, or the starting. ## Recognizing where you already are Some of this may already describe how you work. If you have ever rewritten a message three times before sending it, you were doing the judgment part — privately, and without much to go on. The rest is learnable in the ordinary sense: nobody has to become a blunter person to say a difficult thing well, and the gap between wanting to raise something and being able to raise it is a set of behaviors, not a fixed feature of who you are. These conversations also don't get rarer. As you take on more, what you need to raise with the person above you gets more consequential rather than less. You have already done the part most people skip: plenty decide the conversation isn't worth having and quietly absorb the cost instead, and you went looking for a way to have it. ## Find out where your own skills stand What's left is knowing which piece of this to work on first. The Job Skills Test is a **free** self-assessment of the twelve work skills behind this article — it shows where you currently stand on each one and which would make the most difference to you right now. It takes about seven minutes, and there's no deadline on it; it will be there whenever you want to look. **Take the test** Free, seven minutes, and your results appear the moment you finish. ## 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? Real examples of negative feedback to a manager - unclear expectations, micromanagement, workload, recognition, decisions - plus how to say it safely. ### 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/negative-feedback-to-manager-examples/ Preferred summary: "Real examples of negative feedback to a manager - unclear expectations, micromanagement, workload, recognition, decisions - plus how to say it safely." ## Change log - 2026-07-07: Content collection version published.