# Giving Your Boss a Performance Review: Example Wording That Works Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/giving-your-boss-a-performance-review-example/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/giving-your-boss-a-performance-review-example.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 Asked to review your manager? Example wording for seven upward review areas, plus how to be specific and honest without damaging the relationship. ## Key facts - Title: Giving Your Boss a Performance Review: Example Wording That Works - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Communication, Building Confidence - Primary keyword: giving your boss a performance review example - Source page: https://headwayskills.com/knowledge/working-with-your-manager/giving-your-boss-a-performance-review-example/ ## What this page covers - Asked to review your manager? Example wording for seven upward review areas, plus how to be specific and honest without damaging the relationship. - Practical guidance for giving your boss a performance review example - How this topic connects to Working with Your Manager ## Detailed explanation The form is open, the box asks what your manager could do better, and you have been sitting with it long enough to consider writing "no concerns." When you are giving your boss a performance review, an example that actually works has four parts: name the situation, [describe the behavior you observed](/knowledge/self-awareness/constructive-feedback/), say what effect it had on your work, and end with one specific thing that would help. Keep it to one or two areas rather than a survey of everything. That shape is most of the job — and it explains why some upward feedback gets acted on while the rest gets thanked and filed. ## What to write when you're giving your boss a performance review Search this and you get phrase banks: Teamflect runs 72 examples, Deel more than fifty, AhaSlides forty-plus, all sorted into a positive column and a constructive one. They are useful for vocabulary and almost useless for the part you are stuck on, because the difficulty was never finding words. It was working out which words you can put your name to. Three rules do most of the work. The first is the behavior-impact-suggestion structure the sources converge on: swap the verdict for the moment that produced it. "Your communication needs improvement" is a judgment your manager can dispute; "in the last project update the instructions were read two different ways, and we lost a day sorting out which deadline was real" is a thing that happened. The second is the substitution rule Windmill and Teamflect both press: strike the loaded words — [micromanages](/knowledge/working-with-your-manager/how-to-deal-with-a-micromanager/), plays favorites, doesn't trust the team — and write down the behavior you actually saw instead. Those words are diagnoses of a person, and they turn a solvable operational problem into an accusation about character. The third concerns anonymity. Upward reviews are usually anonymous by design, and Small Improvements is blunt about why: named upward feedback tends to come back socially safe rather than accurate. But the useful discipline is to write as if it weren't anonymous. Anything you couldn't stand behind in the room is nearly always the part that slipped from observation into judgment — which is the part that would have been discounted anyway. ## Seven review areas, with example wording Upward review forms tend to ask about the same handful of things, and the roundups follow: Windmill organizes its manager improvement areas around leadership behaviors — delegation, coaching, decision-making clarity, prioritization, feedback delivery, context-setting — rather than traits. Named areas keep the review from becoming either a grievance list or a page of vague praise. Pick one or two of the seven below. The wording is a pattern to fill with your own situation, not a line to copy. ### 1. Clarity of direction and decisions The most expensive thing an unclear manager costs you is rework. When a decision sits for two weeks or reverses without explanation, the loss is measured in days of your own effort, which makes it concrete and easy to describe. Anchor the example in a project both of you remember and put the cost in it: *"In the Q2 rebuild, the scope changed twice after I'd started, and I lost close to a week's work. It would help if changes that size came with a line on what prompted them."* Note what you are not saying — nothing about indecisiveness, only about what you had to redo. ### 2. Feedback and one-on-ones The single most repeated constructive example across the sources is a version of the same request: more often, not better. [Regular one-on-ones](/knowledge/working-with-your-manager/one-on-one-discussion/) are where course corrections are cheap; when they slip, the correction arrives at the review instead, which is the worst possible moment for both of you. *"Our one-on-ones get moved most weeks, so I mostly hear how I'm doing at review time. Twenty minutes that stays in the calendar would let me fix things earlier."* The ask is small, specific, and entirely within your manager's control — three properties worth checking any example against. ### 3. Delegation and autonomy Delegation feedback splits cleanly, which makes it a good area to show balance in. The positive half is genuinely specific: expectations, deadline, and resources stated at handoff. The constructive half is almost always about decision rights rather than the handoff itself. Sources recommend asking for a clarity statement on autonomy when work is passed over, or a short debrief once it's done. *"You hand work over with the deadline and resources clear, which I appreciate. What I'm less sure of is how much latitude I have — a line on where I can decide and where I should check first would save me a round of second-guessing."* ### 4. Workload and prioritization This one carries the most risk of sounding like a complaint, so the framing matters more than usual. The recommended pattern keeps the subject on maintaining the quality of the work and asks for a joint look at the list, rather than declaring the distribution unfair. *"My load has grown steadily since March, and I'm starting to trade thoroughness for coverage. Could we go through what comes off the list, or which deadlines have room to move?"* If the real issue is that the same few people carry the critical work, say that as an observation about the distribution — not as a claim about who is being favored. ### 5. Recognition and visibility Recognition is the one area where the audience is part of the request, so name it. Whether the work gets mentioned in the wider update or only inside the team is a decision your manager makes, and most of them make it without thinking about it. *"The migration went well and I don't think anyone outside the team knows we did it. It would mean something if wins like that got named in the monthly update."* Keep it to visibility of the work. The moment it becomes about how appreciated you feel, it stops being reviewable and starts being personal. ### 6. Your development Professional-development support is a standard dimension on upward review forms — Klaar and PerformYard both build it in, covering mentorship, feedback, and career guidance. It is also the area where the useful feedback is usually a request for the *next* step rather than a complaint about the last one. *"The stretch projects are the main reason this year felt worth it. What's missing is what comes after — a rough view of what would need to be true for me to [take the next step](/knowledge/working-with-your-manager/how-to-ask-for-a-promotion/), and what you'd want to see in six months."* Forward-facing, and it makes the review a planning conversation rather than a verdict. ### 7. Context from above Managers absorb pressure from their own management and pass down the outcome without the reasoning. That is a real, fixable gap, and it is easier to raise than most people expect, because it costs your manager nothing to fix. *"When targets change at short notice we usually get the number without the thinking behind it, which makes it hard to hold the line with clients. Even a sentence on why would help."* Describe what you couldn't do as a result. What your manager should have anticipated or felt is not something a review can act on. If choosing between the seven is harder than wording any of them, that's usually a sign the honest answer is about how the relationship runs day to day rather than about this form. It can be worth taking a few minutes to [check your own skill gaps](https://assessment.headwayskills.com/) first, because the area you keep avoiding is often the one worth naming. ## What actually decides how this lands Read back over the seven and notice how little of it is vocabulary. Whether upward feedback gets acted on is mostly settled before anyone writes anything — by what you think the relationship is for, by how you structure a point, and by whether you can hold the point steady when your manager pushes back on it. **Working with Your Manager** is the frame everything else sits in. Once you treat this as a partnership with shared purpose rather than an evaluation flowing one way, honesty becomes part of delivering your part of it, and disagreeing stops being insubordination. It also carries the review-specific moves: prepare rather than react, keep the whole thing pointed at what happens next, and ask for what you actually want. Managers differ — a coaching manager wants the conversation, an authoritarian one wants it short and evidenced — and reading which one you have changes how you deliver the same point. **Communication** is the machinery underneath every example above. Lead with the point instead of circling it, stay brief, keep it concrete, and adapt to how the person receiving it takes in information. There's also a choice most people skip: writing documents a point and lets your manager read it without an audience, while conversation is what handles anything sensitive or complicated. Putting a difficult point only in the form is how it ends up filed. **Building Confidence** is the part the phrase banks can't help with. It isn't a temperament you were issued or denied — it's built by deciding in advance exactly when and how you'll raise the point, then getting through the first sentence rather than rehearsing the whole exchange. Start with the smallest true thing you have. Once you have said one honest thing upward and nothing bad happened, the next one costs far less. Reviews come round again, and the same three decide the next one too. The free Job Skills Test reads all three alongside the other work skills in the set — twelve in total — so you can see [which one is blocking you](https://assessment.headwayskills.com/) instead of guessing at it. ## Where this leaves you Some of this is probably already how you operate: noticing what isn't working, holding it rather than blurting it, wanting the point to be fair before you make it. Where other parts feel unfamiliar, that isn't a fixed limit — handling your manager well is a set of behaviors people grow into, and you can get markedly better at it while still being recognizably yourself at work. It also gets more useful over time, because the more you're responsible for, the more often you're the one who has to say the accurate, unwelcome thing to someone senior. And you went looking for how to do this properly instead of typing "no concerns" into the box, which is the part most people skip. What's left is knowing which of your own gaps to work on. ## See what you're working with The last thing worth doing is finding out which parts of this you already have. The Job Skills Test is a **free** self-assessment of your everyday work skills — it shows you where you stand across all twelve, the three behind every example above included, and points to the ones worth your attention now. There's nothing to prepare and no right answer, and you're under no obligation to do anything with the result; it's simply a quiet way to see what would make the next one of these conversations easier. **[Take the test](https://assessment.headwayskills.com/)** *Free, about seven minutes, and your results appear as soon as 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? Asked to review your manager? Example wording for seven upward review areas, plus how to be specific and honest without damaging 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/giving-your-boss-a-performance-review-example/ Preferred summary: "Asked to review your manager? Example wording for seven upward review areas, plus how to be specific and honest without damaging the relationship." ## Change log - 2026-07-07: Content collection version published.