Every time I sit down with an HR manager who’s rolling out a 360 review cycle, the question is never “what is 360 feedback.” They already know that. The real question is always, “What do I actually write?”
I’ve watched people stare at a blank feedback form for 10 minutes because they know what they want to say but can’t find the right words. That’s the gap I want to close here. This is not another explainer on how 360-degree feedback works. I’ve written that one already.
This is your 360-degree feedback examples bank of ready-to-use lines and phrases you can adapt for any competency, role, or relationship, whether you’re reviewing your manager, your peer, your direct report, or yourself. Let’s get into it.
What Is 360-Degree Feedback?
A 360-degree feedback comment, phrase, or written response is used in a multi-rater review process (covering managers, peers, direct reports, and sometimes clients) to describe a specific behavior and its impact. This helps the feedback stay actionable, balanced, and free of vague generalities.
I lean on examples instead of asking people to write feedback cold because they:
- Remove the blank-page problem: Most reviewers freeze up not because they lack an opinion, but because they don’t know how to phrase it professionally.
- Standardize quality across the team: When everyone has access to the same example bank, feedback quality stops depending on who’s a “good writer.”
- Protect against generic praise: A specific example pushes people past “great job, keep it up.”
- Speed up the whole review cycle: Less time staring, more time writing something the recipient can genuinely use.
How I Recommend Using These Examples
Don’t copy-paste these words for word into someone’s review. Use them as a skeleton, then swap in a real project name, a real behavior, or a real outcome.
- Match the role: A peer comment reads differently from a manager comment. Adjust the tone accordingly (more on this below).
- Cite behavior, not personality: Anchor every comment to something the person did, not who they are.
- Balance the tone: Pair one strength with one growth area wherever the form allows it. A report that’s all praise or all criticism gets dismissed.
- Keep it recent: Pull from the last full review period, not just the last two weeks. This is the single biggest source of unreliable 360-degree feedback.
- Reread before submitting: Ask yourself if this comment would make sense to someone who wasn’t in the room when it happened.
12 Feedback Examples by Competency for Managers & Peers
I’ve paired a positive example with a negative (growth-area) example for each competency below, side by side, along with why each one actually lands with the person reading it.
| Competency | Typical Role | Positive Feedback | Negative Feedback | Why It Works |
| Communication | Manager or team lead reviewing a report | “During the November product launch, you ran the daily standups so tightly that engineering, marketing, and support all knew their blockers by 9:15 am, and the launch shipped without a missed handoff.” | “In the vendor pricing call last month, three people had to ask you to repeat the numbers. Slowing down and confirming understanding before moving to the next point would prevent that.” | Both examples tie to a specific event, the launch’s clean handoffs and the pricing call’s mix-up, so the feedback reads as a fact from a moment in time rather than a general compliment or a vague ask to communicate better. |
| Teamwork | Peer reviewing peer | “When the design and engineering teams disagreed on the checkout flow, you got both sides talking instead of picking a side, and the team shipped a version everyone actually backed.” | “In the retro after the Q3 sprint, the same three voices did most of the talking again. Directly asking a quieter teammate for their take before wrapping the discussion would widen the input you’re getting.” | Both draw on a real meeting or conflict, the checkout flow disagreement, and the retro’s repeating pattern, which makes each comment harder to dispute than a general team-player rating. |
| Leadership | Manager reviewing a report | “You laid out the migration plan in a single one-pager that the whole team could reference for six weeks straight, which cut down on ‘what are we doing again’ questions almost entirely.” | “You’re still the one merging every pull request personally. Handing that off to a senior engineer on the team would free up two or three hours a week for planning.” | Each ties to a tangible artifact or habit, the migration one-pager and the pull-request bottleneck, and quantifies the cost or benefit so the feedback feels practical rather than abstract. |
| Problem-solving | Peer or manager reviewing a report | “You caught the API rate-limit issue two weeks before the client demo, when everyone else assumed the slowdown was a database problem.” | “On the outage last month, you jumped straight to a fix before looping in the on-call engineer. Looping others in before acting would catch blind spots you can’t see alone.” | Both reference a real incident, the API issue caught early, and the outage response, which makes the praise credible and the suggestion feel earned rather than generic advice. |
| Time management | Manager reviewing a report | “You carried both the client renewal and the internal audit in the same week without either one slipping, which isn’t something I’ve seen most people pull off.” | “The board deck came together the night before three cycles in a row now. Blocking two hours earlier in the week for a first draft would remove that pattern.” | Both name a specific instance, juggling two priorities in one week and the recurring last-minute board deck, so the feedback reflects a pattern rather than a single lapse. |
| Adaptability | Manager reviewing a report | “When the client pulled funding mid-project, you had a scaled-down proposal ready within a day instead of waiting for direction.” | “When the reporting structure changed in April, the first reaction was to push back rather than explore what the new setup made possible. Taking a beat before reacting to change would help that land better next time.” | Each is anchored to a real disruptive change, the funding pull, and the reporting restructure, which keeps the feedback about the specific moment rather than a personality trait. |
| Emotional intelligence | Peer reviewing peer | “When a teammate’s project got cut after months of work, you were the one who checked in privately instead of just moving the meeting along.” | “In the postmortem after the missed deadline, frustration came through in a way that made two people go quiet for the rest of the meeting. Taking a short break before discussing setbacks would keep the room open.” | Both describe an actual moment and its effect on the people around it, the private check-in and the postmortem tension, which makes the point about impact, not personality. |
| Initiative | Manager reviewing a report | “Nobody assigned the client onboarding audit, but you ran it anyway and found a gap that was costing us renewals.” | “The dashboard rebuild started strong, but stalled once the initial excitement wore off. A short plan up front, even a rough one, would help initiatives like that one land all the way through.” | Each names a specific unassigned task or stalled project, the onboarding audit, and the dashboard rebuild, so the comment is about a concrete instance rather than a vague trait. |
| Collaboration | Peer reviewing peer | “You walked the new hire through the entire deployment pipeline without being asked, and she was shipping code solo within a week.” | “On the pricing model, input only went out after the numbers were finalized. Asking finance for a gut check earlier would have caught the assumption that got flagged in review.” | Both cite a measurable outcome or cost, the new hire’s fast ramp-up and the pricing model’s late input, rather than a general claim about being collaborative. |
| Accountability | Peer reviewing peer | “When the integration broke in production, you were the first to flag it publicly instead of waiting to see if anyone noticed.” | “The missed handoff on the client contract got explained as a calendar issue rather than addressed directly with the team it affected. A direct conversation with them would close that loop better than an explanation after the fact.” | Each references a specific moment of ownership or avoidance, the production flag, and the missed handoff, which distinguishes real accountability from just explaining after the fact. |
| Decision-making | Manager reviewing a report | “Choosing to delay the launch by a week, even under pressure from sales, turned out to be the right call once the load testing came back.” | “The vendor selection got made solo, and it later came out that support’s concerns about response time were never raised.” | Both point to a real decision under pressure, delaying the launch and skipping a stakeholder in vendor selection, which carries more weight than a general “good decision maker” label. |
| Dependability | Peer reviewing peer | “Across four sprints in a row, every commitment made in planning showed up done by the date promised, no exceptions.” | “On the two-month compliance project, updates only came when directly asked. A weekly two-line update, even with no news, would build the same trust without the extra effort of a full report.” | Each is grounded in a pattern across time, four sprints of met commitments and two months without proactive updates, which is what makes dependability feedback credible instead of a single instance. |
20 Feedback Examples by Role
Who’s writing the feedback changes how it should sound. A manager has visibility that a peer doesn’t, a peer sees day-to-day behavior that a manager misses, and upward feedback needs a different tone entirely, so it reads as constructive rather than risky to give. Here’s a deeper set for each relationship.
Manager Reviewing Employee
These 360-degree feedback examples for managers lean on outcomes only a manager typically has visibility into, not just the day-to-day behavior a peer would see.
| Example | Why It Works |
| “In the last product launch, your ability to reprioritize under pressure kept the team on schedule. For the next cycle, I’d like to see you delegate more of the execution so you can focus on the roadmap conversations only you can have.” | A manager has visibility into strategic tradeoffs, so the feedback leans on outcomes the employee might not fully see from inside the work. |
| “Your onboarding of the two new analysts this quarter meant they were contributing to client decks within two weeks, well ahead of our usual month-long ramp. Writing up that approach so other leads can reuse it would multiply the impact.” | Ties a coaching strength to a measurable ramp-up speed and gives a specific, scalable next step rather than generic praise. |
| “You addressed the missed targets on the East region rollout directly and early, rather than waiting for the quarterly review, which gave the team real time to course-correct. Bringing that same directness into mid-cycle check-ins with the rest of the team would help beyond just this one situation.” | Names a specific management behavior (early, direct feedback) and extends it as a habit, not a one-time fix. |
| “You’ve built next quarter’s OKRs almost entirely on your own. Bringing your two team leads into that process earlier would surface constraints they see day to day that don’t always make it into your view.” | Points to a specific process gap (solo goal-setting) with a concrete fix (earlier involvement), rather than a vague call to “collaborate more.” |
| “Your write-ups for the last calibration cycle were specific enough that the leadership panel didn’t need clarifying questions, unlike most submissions that quarter. That saved real time in a two-hour meeting.” | Uses a comparative, measurable detail (fewer clarifying questions, time saved) to make the praise concrete and credible. |
Peer Reviewing Peer
These double as 360-degree feedback examples for peers and as 360-degree constructive feedback examples for colleague reviews, since peers see day-to-day behavior a manager usually misses.
| Example | Why It Works |
| “On the two projects we’ve shared this quarter, you’ve flagged risks early enough that we’ve had time to react instead of scramble. Getting those flags a day or two sooner would help me plan around them even better.” | Peers share day-to-day context, so the feedback stays collaborative and specific to shared work rather than a broad performance judgment. |
| “When I got stuck on the reporting migration, you walked me through the mapping logic instead of just fixing it for me, which meant I could handle the next three tickets on my own.” | Ties a collaboration strength to a specific, measurable follow-on result (three tickets handled solo), not just “helpful teammate.” |
| “In the vendor selection meeting, pushing back on the timeline assumption came across as confrontational rather than exploratory. Framing it as a question, like ‘what happens if this slips,’ would land the same point without putting people on the defensive.” | Names a specific meeting and tone issue, then offers an exact phrasing fix, which is more useful than “be less blunt.” |
| “You’ve kept our shared project doc updated after every client call for two months straight, which means nobody’s scrambling before quarterly reviews anymore.” | Uses a streak (two months, every call) to make dependability credible between peers rather than a single nice gesture. |
| “You gave the design team public credit for the checkout redesign win, even though half the technical lift was yours. That kind of visibility matters for a team that doesn’t always get recognized.” | Highlights a specific, generous behavior with its effect on team morale, which is a distinctly peer-level observation a manager wouldn’t typically see. |
Direct Report Reviewing Manager (Upward Feedback)
Upward feedback needs a different tone entirely, framed around support and clarity rather than authority, so it reads as constructive instead of risky to give.
| Example | Why It Works |
| “You give me real autonomy on my projects, which I value. A standing 15-minute check-in every other week would help me catch misalignment before it costs a full sprint.” | Frames the ask around support and clarity instead of authority, which keeps upward feedback constructive rather than accusatory. |
| “Priorities shifted three times last quarter without a clear explanation of why, which made it hard to know what to protect time for. A short note on the reasoning behind a pivot would help, even when the decision itself doesn’t change.” | Names a specific, countable pattern (three shifts) rather than a vague complaint about direction changing too often. |
| “My work on the migration got folded into the team update without a specific mention, even though it was a solo six-week effort. Calling out individual contributions, not just team wins, would mean a lot.” | Ties the ask to a concrete, named project and its actual scope, which makes the request for recognition feel earned rather than needy. |
| “Our team has absorbed requests from three other departments this quarter without pushback, and it’s landed on our plate each time. Advocating for our bandwidth in those conversations would help us actually hit our own goals.” | Uses a specific, repeated pattern to justify an ask about protecting the team, which reads as constructive rather than a complaint about workload. |
| “Our one-on-ones are almost entirely status updates. Fifteen minutes each month focused specifically on my growth, separate from project check-ins, would help me plan further ahead.” | Distinguishes between two concrete meeting formats (status vs. growth), which gives a manager something specific and easy to act on. |
Self-Evaluation
These lean on outcomes and data rather than adjectives, so a self-review reads as credible instead of self-promotional or falsely modest.
| Example | Why It Works |
| “I led the onboarding redesign this quarter, which cut new-hire ramp time from three weeks to nine days. Going forward, I want to document decisions as I make them so the team isn’t relying on me to explain context after the fact.” | Anchors self-assessment in a measurable outcome instead of adjectives, which keeps it credible rather than self-promotional. |
| “I made the call to push the vendor integration launch by two weeks rather than ship with a known data-sync issue. It meant renegotiating the client timeline, but it avoided a production incident during our highest-traffic period.” | Owns a real, consequential decision and its tradeoffs, which reads as accountable rather than defensive. |
| “I under-scoped the compliance audit at the start of the quarter and had to pull in two extra people mid-cycle to hit the deadline. Next time, I’ll build in a buffer based on how the last two audits actually ran, not the original estimate.” | Names a real mistake with a specific, actionable fix, which is more convincing self-awareness than a generic “I could improve my planning.” |
| “I took over the client escalation on a key account after the account lead left mid-project, and kept the renewal on track despite the handoff gap.” | Demonstrates resilience through a specific, high-stakes scenario rather than a general claim about handling pressure well. |
| “I’ve relied on the same two people for technical sign-off on every release this quarter. Building a wider review rotation would reduce that bottleneck and give newer engineers more exposure.” | Flags a structural growth area (a bottleneck the person created) with a concrete next step, which shows ownership beyond just individual output. |
Start, Stop, Continue Examples
This is the format I recommend most when reviewers are unsure how to structure open-ended feedback.
It naturally balances praise with growth, and if you’re specifically after 360-degree feedback, stop doing examples. The Stop row below is built exactly for that, behaviors to drop entirely, not just adjust.
| Type | Example | Why It Works |
| Start | “Start sharing draft ideas earlier, even before they’re fully formed. On the last two proposals, the team only saw a finished version and had no chance to shape the direction.” | Ties the ask to two real instances instead of a general habit, which makes it feel earned, not arbitrary. |
| Stop | “Stop taking on every ad hoc request from other teams. Three of the last five sprint slips traced back to unplanned work absorbed mid-cycle.” | Uses a specific, countable pattern (three of five slips) to justify the ask, rather than a subjective impression. |
| Continue | “Continue running retros the way you do now, with a clear format and a hard stop at 30 minutes. It’s the one recurring meeting nobody dreads.” | Names the specific mechanic (format, time limit) worth preserving, not just a vague “keep it up.” |
Self-Evaluation Example Answers
Self-assessments carry their own challenge: sounding confident without sounding arrogant, and objective without sounding falsely modest. If you’re after 360-degree feedback example answers you can adapt directly, the four types below cover the situations that come up most.
| Type | Example | Why It Works |
| Strength | “I coordinated the cross-functional launch across three teams this quarter and hit every milestone date, including the one we thought we’d miss after the vendor delay.” | Uses a specific, verifiable outcome rather than a self-descriptive adjective like “great coordinator.” |
| Growth area | “I want to get better at pushing back earlier when a timeline isn’t realistic, instead of absorbing the pressure myself and burning out trying to hit it anyway.” | Names a real behavior pattern and its personal cost, which reads as self-aware rather than performative humility. |
| Achievement | “I redesigned the onboarding checklist, which brought the average new-hire ramp time down by roughly a week based on manager feedback from the last two cohorts.” | Cites a measurable result with a source (manager feedback, two cohorts), which is harder to dismiss as a subjective claim. |
| Collaboration | “I started looping design in during the discovery phase instead of after the spec was final, which cut rework on two of our last three releases.” | Describes a specific process change and its result, rather than a general claim about being collaborative. |
Anonymous Feedback Examples That Protect Identity
Confidentiality is the number one concern I hear about 360-degree feedback, and reviewers often water down honest input because they’re worried they’ll be identified. Here’s how the same observation can stay specific without narrowing down to you.
| Technique | Identifying Version | Anonymous Version | Why It Works |
| Drop the project tag | “As your partner on the Johnson account, I noticed the client updates were often a day late.” | “On recent shared projects, client updates have sometimes landed a day later than expected.” | Removes the one detail (the account name) that would immediately tell the recipient who wrote it. |
| Describe the pattern, not the incident | “In last Tuesday’s standup, you cut off two people mid-sentence.” | “In team meetings, there have been a few moments where a teammate’s point got cut off before they finished.” | Shifts from a single, traceable meeting to a recurring pattern, which reads as broader team feedback. |
| Use grouped language | “I noticed you missed my emails twice this month.” | “The team has noticed that email response times have slipped this month.” | Reframes an individual observation as a shared one, which is harder to trace back to a single reviewer. |
| Strip identifying detail | “During the March 14th client call with Acme, you spoke over the client twice.” | “During recent client calls, there have been a couple of moments where the client didn’t get to finish their point.” | Removes the date and client name, the two details most likely to expose the reviewer’s identity. |
A quick aside on anonymity: the techniques above work fine when you’re editing one comment by hand, but they fall apart fast once you’re managing this across an entire team in a shared spreadsheet or a Google Form.
Someone still has to manually strip out identifying details before anything gets shared. PeopleGoal’s 360 Feedback Software captures anonymous input by design, so reviewers get confidentiality without you rewriting every comment after the fact.
Vague vs. Specific Feedback Examples
Generic praise is one of the biggest complaints I hear about 360-degree feedback results. Here’s the difference in practice, with the reasoning behind each fix.
| Vague | Specific | Why It Works |
| “Needs to communicate better” | “Consider raising your hand in meetings before decisions are finalized, so your input shapes the outcome, not just the recap.” | Gives an exact moment (before decisions are finalized) and action (raise your hand), which the person can act on immediately. |
| “Be more assertive” | “When a deadline feels unrealistic, say so directly to the project lead instead of raising it after the fact.” | Replaces a personality label with a single, repeatable behavior tied to a specific situation. |
| “Great team player” | “You stepped in to cover two teammates’ tasks during a tight sprint without being asked, which kept the release on schedule.” | Swaps a compliment for a documented action and its outcome, which is what makes praise feel earned rather than automatic. |
| “Needs to manage time better” | “Blocking focus time for the top two priorities each morning would reduce the late-week scramble seen on the last three deliverables.” | Names the recurring cost (three deliverables) and a specific fix (morning focus blocks), not just a general habit change. |
Role-Specific Feedback Examples
Generic competency examples only go so far. Here’s how the same idea, giving feedback that ties to business impact, plays out differently by function.
| Department | Example | Why It Works |
| Sales | “You handled the pricing objection on the Meridian deal calmly and kept the conversation moving instead of getting defensive. Bringing that same composure into internal pipeline reviews, where the tone tends to get tense, would help there too.” | Uses a named deal as proof and then extends the same skill to an internal context, showing range instead of a single win. |
| Engineering | “Your code reviews on the payments service catch issues early enough that QA rarely finds anything major downstream. Documenting the reasoning behind the bigger architecture calls would help the two engineers who joined last month ramp up faster.” | Connects a technical habit to a measurable downstream effect (fewer QA catches) and a specific audience (new engineers) for the growth ask. |
| Customer support | “You de-escalate frustrated customers by acknowledging the issue before jumping to a fix, which shows up in the lower reopen rate on your tickets. Flagging recurring complaint themes to product weekly, instead of case by case, would help us fix root causes instead of symptoms.” | Ties the strength to a measurable metric (reopen rate) and gives a concrete cadence (weekly) for the improvement, not just “escalate more.” |
| Leadership | “You explain the reasoning behind decisions, which is part of why the team’s engagement scores held steady through the reorg. Bringing the team into the decision-making conversation itself, not just the announcement, would deepen that trust even further.” | Links the leadership behavior to a measurable result (engagement scores) rather than a general trait, and the growth task is a specific process change. |
Common Mistakes to Avoid With These Examples
The examples above only work if you avoid a handful of patterns that quietly undermine 360 feedback.
| Mistake | What It Looks Like | Better Version | Why It Works |
| Recency bias | “This week’s missed deadline shows a pattern of poor time management.” | “Across this review period, deadlines slipped on two of six deliverables, both in weeks with overlapping priorities.” | Pulls from the full period instead of the most recent event, which is what makes the feedback representative rather than reactive. |
| Generic praise | “Great job this quarter, keep it up.” | “Your handling of the vendor escalation in March kept the contract intact and saved roughly two weeks of renegotiation time.” | Replaces applause with a specific, attributable outcome the person can point to later. |
| Personal language | “You’re disorganized.” | “Project files across the last two launches were split across three different folders, which slowed down handoffs.” | Converts a character judgment into an observable, fixable behavior. |
| Emotional venting | “It was frustrating dealing with the missed handoff again.” | “The handoff on the client contract was missed for the second time this quarter, and a shared checklist might close that gap.” | Waits past the emotional reaction and reframes the comment around the behavior and a workable fix. |
Turn These Examples Into Feedback People Actually Use
Good 360 feedback doesn’t come from better software alone; it comes from better language and specific, balanced examples that are easy to adapt to the person in front of you.
Use the ones above as your starting point, then make them your own with real context from your team.
If you’re ready to move this whole process out of scattered forms and spreadsheets, PeopleGoal 360 Feedback Software gives you the workflows, anonymity controls, and reporting to make these examples count. Try it out and see how much time you get back in your next review cycle.
Frequently Asked Questions
How many 360 feedback examples should I include in one review?
There's no fixed number, but I'd rather see three to five well-developed, specific comments than ten generic ones. Depth beats volume here, especially if the recipient is expected to build a development plan from the results.
Can I use AI to help write 360 feedback examples?
Yes, and many teams already do this to get past the blank page. Use AI to draft a first pass, then edit in the specific project, behavior, or outcome only you would know. Never submit an AI draft without personalizing it, or the feedback loses the specificity that makes it useful.
How often should I refresh my example bank?
Revisit it every review cycle. Competencies stay fairly constant, but the specific behaviors and projects behind each example should always reflect the most recent period, not last year's examples recycled forward.
Do these examples work for remote teams?
Yes, with one adjustment. Add a competency around communication style and responsiveness in asynchronous or digital settings, since that's one of the most common gaps remote teams flag in 360 reviews.
Should self-evaluation examples sound different from peer examples?
Yes. Self-evaluations should lean on outcomes and data to avoid sounding falsely modest or overly self-promotional, while peer examples can lean more on day-to-day observed behavior.
What's the ideal length for a single written feedback example?
Two to three sentences per comment. Long enough to include the behavior and its impact, short enough that the recipient doesn't lose the point.
Ready to 3x Your Teams' Performance?
Use the best performance management software to align goals, track progress, and boost employee engagement.
