A strong manager review stays brief, specific, behavior-based, and tied to results with one or two practical next steps.
Writing upward comments can feel risky, yet it’s a chance to shape how your team works. The aim is simple: describe what helped you do great work, what got in the way, and what would raise the bar next quarter. The notes below give you a structure that’s direct, fair, and easy to act on.
Write A Review For Your Boss: What Good Looks Like
A helpful review reads like field notes, not a rant or a fan letter. It names specific wins, points to tough spots with neutral language, and proposes one change per theme. Keep it short; precision beats length.
Use Situation → Behavior → Impact
Frame each point with three parts: the moment, the action, and what changed for the team. This keeps your tone neutral and avoids guessing motive. You can say, “In the Q3 planning meeting (situation), you set scope in five minutes (behavior), which let engineering size work by noon and saved a week (impact).” The same frame also works for friction.
Prioritize Outcomes Over Opinions
Swap adjectives for data. Times, dates, shipped items, cycle time, customer scores, and hiring outcomes land better than soft labels. Two crisp data points beat a paragraph of vague praise.
Balance Praise And Friction
Leading lines with a real win shows you see the full picture. Then move to the sticky bit with plain words and end with a single step your manager can try. One theme per paragraph keeps it clean.
Manager Feedback Cheatsheet
Use the table to turn fuzzy thoughts into plain, fair lines that land well.
| Situation | Stronger Phrasing | Weaker Phrasing |
|---|---|---|
| Weekly standups run long | “In Monday standups, we exceed 30 minutes, which delays QA handoff. Could we cap updates to two bullets and move blockers to a sidebar chat?” | “Meetings waste time.” |
| Clear goals helped delivery | “Your sprint kickoff one-pager listed owner, scope, and ‘done’. Velocity rose from 22 → 30 points for two sprints.” | “Great leadership.” |
| Slack pings after hours | “Late pings at 10–11 p.m. pull the team back online. Setting a ‘non-urgent after 6 p.m.’ tag would help recharge time.” | “You message too late.” |
| Public praise boosts morale | “Shout-outs in the all-hands raised survey ‘recognition’ scores from 7.1 → 8.0.” | “Nice job calling people out.” |
| Scope changed mid-sprint | “Mid-sprint scope change on Oct 3 added three stories; two rollovers followed. A 24-hour freeze before release would steady delivery.” | “Stop changing your mind.” |
| 1:1s are helpful | “Bi-weekly 1:1s with shared notes unblocked access to the data warehouse within two days each time.” | “I like our chats.” |
Plan Your Upward Review In Five Steps
This flow gets you from raw notes to a tight review that reads fair and lands action.
Step 1: Gather Proof
Skim your calendar, shipped pull requests, sprint boards, and any survey comments. Pull three wins and three frictions tied to your manager’s actions or support. Pick items with dates and outcomes. Skip hearsay.
Step 2: Draft With The SBI Frame
Write each point in three lines: situation, behavior, impact. Keep emotion out; the frame does that for you. If you need a quick primer on the approach, the Center for Creative Leadership explains it well; see their page on the SBI method.
Step 3: Weigh What Matters For The Team
Rank your notes by effect on delivery, quality, hiring, safety, and retention. Lead with items that move those needles. A review with three high-value points beats a laundry list.
Step 4: Offer One Next Step Per Theme
End each paragraph with a single, doable change. Cap meeting time, add a decision log, move approvals to a weekly slot, or set a quiet-hours policy. Pick steps that fit your team’s stage and tools.
Step 5: Keep Tone Neutral And Brief
Use short words and active verbs. Aim for 250–400 words total unless your form asks for more. Read it out loud; trim any line you wouldn’t say face-to-face.
What To Praise, What To Flag
Balance is the goal. Praise shows respect for effort and results; flags point to better ways of working.
Praise That Lands
Spotlight actions that made work easier or raised quality. Clear goals, fast decisions, timely feedback, resource wins, and credit-sharing belong here. Tie each to an outcome: speed, fewer defects, customer kudos, successful hire, or saved budget.
Flags That Help The Team
Pick frictions that block delivery or drain people. Common themes: shifting scope without trade-offs, late approvals, thin resourcing, unclear ownership, and noisy communication. Name the moment, not the person. Offer a step your manager can try this month.
Sample Paragraphs You Can Adapt
These ready-to-tweak lines fit most forms. Swap dates, teams, and metrics.
Clarity And Direction
“In the Sept 2 roadmap review, you narrowed the Q4 scope to two bets and cut three stretch items. That kept design and data focused and raised on-time delivery to 92%.”
Decision Speed
“When procurement stalled on vendor A, you set a 48-hour SLA for legal review. The contract signed on Aug 14, and onboarding finished a week sooner.”
Coaching And Growth
“Your async code notes on Tuesdays are clear and actionable. New hires closed their first tickets in nine days vs. 15 last quarter.”
Communication Habits
“Project updates arrive across Slack, email, and Notion. A single weekly digest with owners and dates would cut status churn.”
Team Health
“Last-minute meeting adds after 6 p.m. spike after-hours work. A guardrail for non-urgent pings would help energy and focus.”
Align With Company Process
Many orgs want upward feedback as part of a two-way review. The Society for Human Resource Management notes that reviews work best when they’re a conversation, not a lecture; see their guidance on a two-way review. If your HR form has prompts, write to those cues first and keep extras short.
Sticky Topics: Handle With Care
Some issues sit outside a normal performance form. If pay equity, safety, or discrimination enters the picture, route it through the channels your company provides. In the United States, the Equal Employment Opportunity Commission explains protections against retaliation when raising EEO concerns; see their retaliation guidance. Use dates and facts, and keep copies of what you submit through official paths.
Common Mistakes To Avoid
Vague Labels
Words like “great,” “poor,” or “strong communicator” don’t say much. Swap them for a date, a moment, and an outcome.
Guessing Motives
Phrases like “you don’t care about quality” or “you favor Team A” escalate fast. Stick to visible actions and effects.
Lists Without Fixes
Five complaints with no path forward feel like a dead end. One clear step per theme keeps it useful.
Over-Sharing Private Details
Leave personal history and medical info out of a performance form. Keep the review about work and outcomes.
Using Sarcasm Or Loaded Words
Snark may feel sharp in the moment, then live forever in the file. Plain words age better.
Short Template You Can Fill
Paste this into your form and swap the brackets. Keep each bullet to one-two sentences.
Template
- What Helped: [Situation/Date]. [Manager Action]. [Impact on delivery/quality/hiring].
- What Blocked Work: [Situation/Date]. [Manager Action]. [Impact]. A step to try: [One change].
- Communication: [Where updates show up]. A tweak that would help: [Digest/Cadence/Owner].
- Team Health: [Hours/Load/On-call]. Guardrail to try: [Policy/Rotation/Freeze].
- Looking Ahead: One goal where your backing would help most: [Hiring/Tooling/Budget/Cross-team decision].
Tone, Length, And Delivery
Tone
Warm and direct wins. Write like you talk to a trusted peer. If a line sounds sharp when read out loud, cut or soften it.
Length
Most managers get dozens of reviews in a cycle. Tight writing helps yours get read. Fit the form limits; if none exist, 250–400 words is a sweet spot.
Delivery
If the process allows, send your notes a day before the 1:1. That gives time to think and raises the odds of a steady, productive chat.
Checklist Before You Submit
Run your text through this quick pass. It trims noise and keeps the message steady.
| Check | What To Do | Done? |
|---|---|---|
| SBI Shape | Each point has situation, behavior, impact. No motive reading. | [ ] |
| Outcome Ties | Use delivery, quality, hiring, safety, or retention as anchors. | [ ] |
| One Step Each | Close with a single, doable change per theme. | [ ] |
| Plain Words | Short sentences, active verbs, zero jargon or loaded terms. | [ ] |
| Proof | Dates, metrics, links to tickets or docs where allowed. | [ ] |
| Balance | At least one clear win and one clean friction. | [ ] |
Sample Full Review (Adaptable)
Use this as a model. Keep the structure; swap details.
What Helped — In the July 8 sprint kickoff, you narrowed scope to two features and named owners for each. That clarity raised throughput to 28 points and kept QA load steady. Your weekly shout-outs during the all-hands lifted the ‘recognition’ score from 7.1 to 8.0 in the last pulse survey.
What Blocked Work — Mid-sprint scope changes on Oct 3 added three high-risk stories; two rollovers followed. Proposing a 24-hour freeze before release would steady delivery. Project updates land across Slack, email, and Notion, which leads to status churn. A single Friday digest with owners and dates would help alignment.
Looking Ahead — The team would gain from a weekly 30-minute decision slot with design and data present. That should cut cross-team wait time on approvals and speed handoffs.
Ethics And Safety Notes
Upward feedback should never name private health details or gossip. Stick to work. If you raise protected topics (EEO, harassment, pay equity), use the channels your company outlines, log dates, and keep copies. See the EEOC page linked above for rights and process basics.
Bring It All Together
A steady, fair review does three jobs at once: it gives your manager clear signal, it lifts team output, and it builds trust. Lead with real wins, flag the tough bits with neutral wording, and close with one step that moves the needle. Short, specific, and kind beats long and vague every time.