# Good Feedback for a Manager: What to Say, and How to Say It Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/good-feedback-for-manager/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/good-feedback-for-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 Good feedback for a manager is specific, well timed, and asked for first. A seven-step way to prepare it, say it, and follow up without straining the relationship. ## Key facts - Title: Good Feedback for a Manager: What to Say, and How to Say It - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Building Confidence - Primary keyword: good feedback for manager - Source page: https://headwayskills.com/knowledge/working-with-your-manager/good-feedback-for-manager/ ## What this page covers - Good feedback for a manager is specific, well timed, and asked for first. A seven-step way to prepare it, say it, and follow up without straining the relationship. - Practical guidance for good feedback for manager - How this topic connects to Working with Your Manager ## Detailed explanation Most people already know what they want to tell their manager. What stops them is the arithmetic of saying it to the person who writes their review. Good feedback for a manager is specific rather than general: one situation you both remember, the thing your manager actually did, the effect it had on the work, and one suggestion for next time — asked for before it is delivered, said privately, and raised while the details are still fresh. That last part is where most attempts come apart. The wording is rarely the problem. The sequence around it is. ## What counts as good feedback for a manager Search this and you mostly get sentences by the hundred. CultureMonkey publishes more than 125 examples, Teamflect 72, Frankli 53. The appeal is obvious — a ready-made line is the smallest thing a nervous person can pick up and carry into a room. The trouble is that those same articles all insist specificity is what makes feedback work, and a borrowed sentence is specific to nobody. "Clearer communication on project expectations would help the team stay aligned" is a perfectly fair sentence. It is also one your manager can agree with warmly and forget by lunchtime, because it points at nothing that actually happened. The scaffold that recurs across the more serious sources — Culture Amp, Quantum Workplace, Workhuman — is SBI: [situation, behavior, impact](/knowledge/self-awareness/constructive-feedback/). Describe when and where it happened, describe the observable thing your manager did, then describe the effect it had. It works upward for a structural reason. Each of the three parts is something you witnessed, so none of it is a claim about who your manager is, and there is nothing in it to defend against. "You are disorganized" invites an argument about character. "The priorities changed on Wednesday and I heard on Friday, after two days on the old brief" does not. Then add a fourth part, which several sources treat as the line between feedback and complaint: bring a suggestion. Not a demand — a proposal you would be glad to have modified. If you recognize the version of this where the sentence is ready and the conversation still has not happened, the missing piece is not vocabulary. It is more useful to know [where your own gaps are](https://assessment.headwayskills.com/) than to collect a longer list of examples, and gaps like that are habits, which means they respond to practice. ## How to give good feedback to your manager, step by step Seven steps, in order. The order carries much of the weight here — several of these stop working if you take them out of sequence. ### 1. Decide whether you have feedback or a grievance Check your own state before anything else. Science of People sets a hard gate at this point: if you are angry or frustrated, wait, and it names 24 hours as the minimum. Feedback delivered while you are still hot arrives as an accusation however carefully you worded it, and your manager will answer the temperature rather than the content. One test settles it. Can you name the change you want? "I would like to hear about shifting priorities on the day they shift" is feedback. "I want him to stop being like this" is not yet — it is a feeling about a person, and there is nothing in it your manager could act on even if they wanted to. ### 2. Pin it to one situation you both remember Vague feedback triggers defensiveness, and the mechanism is simple: with nothing concrete on the table, the only thing left to examine is your manager's character. So write down one instance beforehand — when it happened, what your manager did, what followed. This step has a dependency the others do not. It needs a recent example. Feedback saved up for [the annual review](/knowledge/working-with-your-manager/performance-review-tips-for-employees/) comes with stale evidence, and the conversation turns into a dispute about whether the thing even happened that way. If it is worth saying, it is worth saying while you both still remember the week. ### 3. Choose the moment and the channel Private, one to one, and spoken. BetterUp and Culture Amp make the same point about medium: written feedback strips out tone and body language, so it reads harder than you meant it. That is worth knowing, because most upward feedback in practice gets typed into an anonymous 360 or engagement-survey box — the one channel where nuance is impossible and follow-up does not exist. Timing is situational, and Aston Carter's version of the advice is the practical one: look at what your manager is carrying that week. Inside a deadline, or prepping for a board meeting, postpone. Feedback lands when the person receiving it has attention to spare. And never in a team meeting — raised in public, it reads as a challenge to their standing, whatever you intended. ### 4. Ask before you start Do not open with the substance. Open with a request: whether they have a few minutes for something you noticed, or whether they are open to some feedback. Lattice and Fellow both put this early, and the reason is autonomy — a manager who has said yes is listening as a participant, while a manager who is ambushed is managing a surprise. It is also the easiest sentence in the whole process. If [nerves](/knowledge/confidence/how-to-be-more-confident/) are what has been stopping you, rehearse this one, because everything after it gets easier once they have agreed. ### 5. Say it, then turn it into a question Lead with your main point instead of building up to it. A long preamble reads as bad news approaching, and your manager will spend it bracing. Then the four parts: the situation, what they did, the effect, your suggestion. Two or three sentences is usually enough. Then hand it over. Putting your point as a question — how they would like the team to handle it when priorities move mid-project, for instance — keeps the tone open and leaves them room to think. Culture Amp and Lattice both name the failure it avoids: feedback delivered as a directive or an ultimatum, which leaves your manager two options, comply or pull rank. Neither ends well for the person who is not the manager. ### 6. Stop talking and listen to the answer You may be about to receive context you did not have — a constraint from above, a decision that was never theirs, a reason the information moved slowly. Take it. That is not losing the argument; that is the conversation working. What you are avoiding here is the version where you say your piece and then keep saying it. Once it has been heard, it has been delivered. Repetition turns a reasonable point into pressure, and pressure is what damages a working relationship — not the feedback. ### 7. Come back to it at the next one-on-one Close by agreeing to revisit it, either at [your next one-on-one](/knowledge/working-with-your-manager/one-on-one-meeting-with-manager/) or in a check-in a few weeks out. This is the step people skip, and it is the one that decides whether any of it mattered: without it your manager has no signal about whether the change worked, and you have no evidence that being honest was safe. It is also how the whole thing stops being an event. Quantum Workplace and Workhuman both argue that upward feedback should be continuous — small points raised inside the one-on-one you already have, rather than banked for the review cycle. One point raised in a scheduled meeting is an ordinary work conversation. Six of them saved for March is a case against your manager, and it will be received that way. ## The skills underneath a conversation like this Read back over those seven steps and notice how little of the work is wording. Most of it is relationship, timing, and nerve — and each of those is something people get better at by doing, not something they were handed. **Working with Your Manager** is the frame the steps quietly assume: that the two of you are working toward the same thing, that you each deliver your part, and that disagreeing is allowed inside that rather than a breach of it. Seen that way, honesty becomes possible even when it feels risky, and the line between telling your manager something and telling everyone else stays obvious. The recurring one-on-one is the machinery — it gives feedback somewhere to live, so it never has to become an event. **Communication** covers the delivery, and giving feedback is one of the tricky situations it deals with head on. Lead with your main point, keep it brief and clear, and stay concrete about behavior rather than character. Choosing the channel is part of the skill too: a conversation for anything sensitive, writing only when something genuinely needs a record. And no sandwich — compliments wrapped around a complaint mostly teach people to distrust your compliments. **Building Confidence** is the part most people underestimate, because they read the problem as not knowing what to say when it is really not having said it. Confidence here is built by doing, in steps small enough to actually take: give the low-stakes version first, a specific piece of positive feedback at your next one-on-one, before you attempt the harder one. Decide in advance where, when, and how. The nerves do not have to be gone first; they only have to be survivable. That last one is also the easiest to check. Seeing [which skills to build first](https://assessment.headwayskills.com/) will tell you whether wording is really where you are stuck — the free assessment looks at eleven others alongside it, the full set the framework treats as learnable rather than fixed. ## Before your next one-on-one Some of this may already describe how you operate — the mental note after a meeting, the sentence you drafted and never sent. That instinct is the harder half to acquire. What is left is a handful of behaviors you can practice deliberately, and none of them asks you to become the blunt one on the team; you get to stay yourself and still say the difficult thing. It is worth building now rather than later, because these conversations get more consequential as you take on more: the person across the desk changes, the stakes rise, and the habit of raising things well is what you end up relying on. You have already done the part most people skip, though — you looked up how to do this properly before opening your mouth, rather than after. Which leaves a smaller question than the one you arrived with. Not what to say, but which part of this you would like to get better at. ## Find out where you stand The only thing left is working out which part that is. The **free** Job Skills Test is a short self-assessment of the twelve work skills this article has been circling: it shows you where you stand on each one, and which two or three would make the biggest difference to conversations like the one you are preparing for. Nothing to prepare, nothing to pay, and you can take it whenever it suits you. **[Take the test](https://assessment.headwayskills.com/)** *Free, seven minutes, 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? Good feedback for a manager is specific, well timed, and asked for first. A seven-step way to prepare it, say it, and follow up without straining the relationship. ### 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/good-feedback-for-manager/ Preferred summary: "Good feedback for a manager is specific, well timed, and asked for first. A seven-step way to prepare it, say it, and follow up without straining the relationship." ## Change log - 2026-07-07: Content collection version published.