360 feedback examples are structured phrases — organized by competency and reviewer relationship — that help employees give specific, actionable input during performance review cycles. Effective examples name an observable behavior, describe its impact on the team or output, and include a clear continuation or change request. Vague praise produces no behavioral change.
In this guide
- What Are Good 360 Feedback Examples for Peers?
- What Are 360 Feedback Sample Questions That Produce Useful Answers?
- What Makes 360 Feedback Actionable Rather Than Just Descriptive?
- How Do 360 Feedback Examples Connect to OKR Performance Reviews?
- What Are the Best 360 Feedback Examples by Reviewer Relationship?
- Why Do Most 360 Feedback Programs Fail — and What Actually Fixes Them?
- Frequently asked questions
What Are Good 360 Feedback Examples for Peers?
Strong peer 360 feedback names a specific behavior and its impact on team outcomes — not a vague trait like “great communicator.” When reviewers default to what they remember most vividly, the result is recency-biased generalities that tell the recipient nothing actionable.
Strong peer feedback follows a simple discipline: behavior + context + impact. Name what the person did, when it happened, and what it changed.
❌ Weak
“Maya is a great collaborator and always willing to help the team.”
✅ Strong
“Maya flagged a dependency conflict between the product and engineering timelines three weeks before our Q2 launch. She called a sync the same day, got both leads aligned, and we shipped on time. Without that call, we would have hit a two-week delay.”
The difference is not effort — it’s specificity. The strong example gives Maya something to replicate. It gives her manager something to evaluate. And it gives the organization a data point it can actually use.
Peer Feedback Examples by Competency
| Competency | Example Feedback Phrase |
|---|---|
| Communication | “Consistently summarized meeting decisions in writing within 24 hours — reduced follow-up emails by roughly half across our sprint cycles.” |
| Reliability | “Every deliverable this quarter arrived on or before the stated date. When scope changed, proactively updated stakeholders before being asked.” |
| Problem-solving | “When our data pipeline broke two days before the board review, came in early, isolated the issue, and had a fix deployed before the presentation. No escalation needed.” |
| Collaboration | “Actively includes quieter team members in planning discussions — specifically asked three people by name for input during our Q1 roadmap session.” |
| Accountability | “When the campaign underperformed, presented a root-cause analysis unprompted in the next team meeting — with a revised approach, not just an explanation.” |
| Initiative | “Identified a gap in our onboarding documentation, drafted a replacement template, and had it reviewed before it was even assigned as a task.” |
| Growth area | “Tends to work to completion before sharing work in progress — earlier visibility would help the team course-correct faster on longer projects.” |
“Feedback that cannot be acted on is not feedback — it’s an opinion filed and forgotten.”
What Are 360 Feedback Sample Questions That Produce Useful Answers?
The quality of 360 feedback is determined upstream — by the questions reviewers are asked. Most feedback forms default to rating scales: 1 to 5, agree to disagree. Ratings produce data that’s easy to aggregate and almost impossible to act on. A score of 3.8 on “communication effectiveness” tells a manager nothing about what to develop.
Effective 360 feedback questions force the reviewer to recall a specific situation. They use the structure: situation → behavior → outcome.
360 Feedback Sample Questions: Manager Reviewing Direct Report
- “Describe a situation where this person took ownership of a problem without being asked. What did they do and what was the result?”
- “Where does this person’s contribution to team performance stand out most clearly?”
- “What one behavior, if changed, would most improve this person’s effectiveness in the next quarter?”
- “How does this person respond when a project is off track? Give a specific example.”
- “What skill or behavior would you most want this person to develop in the next six months?”
360 Feedback Sample Questions: Peer Reviewing Peer
- “Describe a time when working with this person made your own work easier or better. What specifically did they do?”
- “When collaboration has been difficult, what was the pattern? What could change?”
- “What is this person’s strongest contribution to how the team operates?”
360 Feedback Sample Questions: Direct Report Reviewing Manager
- “Describe a situation where your manager’s feedback helped you improve or course-correct.”
- “What does your manager do well when the team is under pressure?”
- “What is one thing your manager could change that would make you more effective in your role?”
Why open questions outperform rating scales
Open-ended prompts force reviewers to recall specific situations rather than assign a number — and that specificity is what separates a review that changes behavior from one that gets filed away. Ratings tell you the score. Behavioral answers tell you what to coach.
What Makes 360 Feedback Actionable Rather Than Just Descriptive?
360 feedback becomes actionable when it names a specific behavior, connects it to a visible outcome, and includes a forward instruction — continue X or change Y to Z. Most feedback satisfies one of these three conditions. Almost none satisfies all three, which is why the needle on performance does not move.
Feedback becomes actionable when it meets three conditions simultaneously:
- It names a specific behavior — not a trait or a personality attribute
- It connects that behavior to a visible outcome — something the recipient can verify happened
- It includes a forward instruction — continue doing X, or change Y to Z
Most feedback satisfies one of these three. Almost none satisfies all three. The result is feedback that feels complete to the giver and useless to the receiver.
The Semantic Triple Format for Feedback
Every effective feedback statement follows a semantic triple: [Subject] + [active verb] + [concrete outcome].
| Feedback Type | Weak Version | Semantic Triple Version |
|---|---|---|
| Positive | “Great communicator.” | “Rewrote the weekly status update format — meeting time dropped from 60 to 35 minutes within two weeks.” |
| Developmental | “Should be more proactive.” | “When the Jira backlog changes, notify dependent teams same-day — delays in Q1 cost engineering two sprint days.” |
| Managerial | “Good at giving feedback.” | “After the campaign miss, delivered individual debriefs to each team member within 48 hours — retention of two at-risk contributors followed.” |
“Feedback is the distance between what someone did and what they now know to do differently. Vague feedback closes none of that gap.”
How Do 360 Feedback Examples Connect to OKR Performance Reviews?
This is where most performance systems break down structurally. 360 feedback and OKR reviews live in different systems, run on different cadences, and are read by different people. A manager receives a 360 report in February and OKR scores in March. Neither document references the other. The employee is evaluated twice for the same quarter using disconnected data.
The cost of this disconnection is measurable: only 2 in 10 employees strongly agree that their performance is managed in a way that motivates them to do outstanding work (Gallup, 2024). The cause is not bad managers — it is systems that isolate behavioral feedback from goal outcomes.
When 360 feedback is connected to OKR progress data, three things change:
- Feedback becomes contextualized. “Proactive communication” means something different when paired with a 0.9 OKR score versus a 0.4 score. The same behavior has different weight in different execution contexts.
- Managers review both layers simultaneously. They see how the person executed and how their colleagues experienced the execution — in one view.
- Development goals connect to the next quarter’s key results. If feedback identifies a pattern — say, inconsistent stakeholder updates — the manager can build a key result around it for Q3 directly.
Connection between goals and feedback
When managers can see 360 feedback alongside OKR completion data in a single view, development conversations shift from general impression to specific evidence. Feedback tied to goal context produces clearer next actions — because the reviewer and the recipient are looking at the same record of what actually happened.
Connect 360 Feedback to OKR Completion Data — In One Platform
What Are the Best 360 Feedback Examples by Reviewer Relationship?
Manager to Direct Report — Positive Feedback Examples
“Delivered the product brief three days early, giving the engineering team enough time to catch a scope issue before sprint planning. That buffer saved an estimated week of rework.”
“When the client escalated in Q3, took ownership of the response without prompting — drafted the reply, coordinated with legal, and had it approved within four hours. The relationship was preserved.”
“Consistently links daily task updates to the relevant key result in our OKR tool — the rest of the team now follows the same practice. Check-in quality across the pod improved measurably.”
Manager to Direct Report — Developmental Feedback Examples
“When scope changes, communicate impact to the timeline within 24 hours rather than absorbing it silently. Two instances this quarter where the delay surfaced in the retrospective rather than at the moment of decision.”
“Peer feedback from three team members notes that meeting contributions are strong in one-on-one settings but quieter in group discussions. Experiment with preparing one structured point to share in the next three team reviews.”
Direct Report to Manager — Feedback Examples
“After the Q1 campaign shortfall, you ran a structured retrospective and shared findings with the whole team — not just leadership. That transparency built trust and helped the team course-correct fast.”
“More visibility into how team-level OKR scores feed into the department score would help me understand where my work matters most. Even a monthly view would make goal-setting feel less abstract.”
Peer to Peer — Feedback Examples
“When the data pipeline broke mid-sprint, you diagnosed the issue, posted an update in the team channel within the hour, and had a workaround deployed before stand-up. No escalation required.”
“Great instinct for when to involve other teams early. In the infrastructure migration, you pulled in security two sprints earlier than planned — that avoided a 3-week review gate at the end.”
Why Do Most 360 Feedback Programs Fail — and What Actually Fixes Them?
360 feedback programs do not fail because employees refuse to be honest. They fail because the system around the feedback was not designed for action.
Three structural failures repeat across organizations of every size:
1. Annual cadence disconnected from real work. When feedback covers twelve months, reviewers cannot recall specific events reliably. Recency bias takes over — the last two months crowd out the first ten. The result is a review that reflects the most recent quarter’s performance with a twelve-month label attached. Organizations running quarterly feedback cycles tied to OKR review rhythms produce more accurate, more specific input — because reviewers are asked about work that just happened.
2. Feedback without a follow-up owner. A review completed is not a development intervention. Someone must read it, discuss it, and attach a specific next action. In most organizations, that step is optional. When review output is connected to the next quarter’s key results — and a manager owns that connection — development becomes a structural outcome, not an optional conversation.
3. Questions that produce ratings instead of insight. A 4.2 on “strategic thinking” is a label, not a signal. It cannot be developed. Open behavioral questions — the kind that force the reviewer to recall a situation — produce data a manager can actually use. The shift from rating scales to behavioral prompts is the single highest-impact change most organizations can make to 360 quality without changing anything else.
“A performance review disconnected from goal data is archaeology — you’re studying what happened, not shaping what comes next.”
The right continuous performance management tools connect review cycles to OKR cadences — so managers spend time on interpretation and development, not data assembly. Explore OKR examples by department to see how goal data maps to individual performance contexts across functions.
See Profit.co in Action
Frequently Asked Questions
Strong peer feedback names a specific behavior and its impact: “You consistently flag blockers before they escalate, which kept the Q2 launch on track.” Avoid vague praise like “great team player” — it gives the recipient nothing to replicate.
Effective 360 feedback questions use a behavior + impact format: “Describe a situation where this person’s communication helped or hindered the team.” Closed-scale questions alone produce ratings without context — open prompts produce insight.
Actionable feedback follows the Subject-Verb-Outcome format: it names who did what and what changed as a result. It includes a specific continuation or change request, so the recipient knows exactly what to do differently next quarter.
Focus on observable collaboration behaviors, not technical outputs. Comment on how they communicated priorities, responded to requests, or handled cross-functional conflict — areas visible from your vantage point regardless of their domain expertise.
Most high-performing organizations run 360 feedback once per half-year or tied to quarterly OKR reviews. Annual cycles produce feedback reviewers struggle to recall accurately. Quarterly touchpoints connected to goal progress yield more specific, credible input.
