360-Degree Feedback: Process & Template (2026)

360-Degree Feedback: Process, Questions & Template (2026)

360-degree feedback is one of the most powerful — and most misused — tools in performance management. Done well, it gives an employee a rounded, multi-perspective picture of how they show up at work: how their manager, peers, direct reports, and sometimes internal customers experience their behaviour and impact. Done badly, it becomes an anonymous popularity contest that bruises egos, fuels office politics, and gets quietly abandoned after one painful cycle. The difference lies almost entirely in design and intent.

This 2026 guide is a practical playbook for HR managers, founders, and people leaders who want to run 360-degree feedback that genuinely develops people. We'll define what 360 feedback is and isn't, explain when to use it (and when not to), walk through designing the questionnaire, choosing raters, running the cycle, and — most importantly — turning results into real growth. You'll also find sample competencies and questions, a process template, and an FAQ covering the issues that trip teams up most.

What is 360-degree feedback?

360-degree feedback — also called multi-rater feedback — is a process in which an employee receives structured feedback from multiple people around them, not just their direct manager. The "360" refers to feedback coming from all directions:

• Downward from the manager (the traditional source).
• Upward from direct reports, for people who manage others.
• Lateral from peers and colleagues who work alongside them.
• Self assessment, where the employee rates themselves on the same dimensions.
• Sometimes outward-in from internal customers or cross-functional partners.

The output is a consolidated view of how an individual's behaviours and competencies are perceived across these relationships, usually compared against their own self-perception. The gap between how someone sees themselves and how others experience them is often the single most valuable insight the process produces.

Crucially, 360-degree feedback is fundamentally a development tool. Its purpose is to raise self-awareness and guide growth, not to calculate a rating or decide a salary. The moment a 360 is wired directly into pay or promotion, the honesty that makes it valuable tends to evaporate, and the politics begin.

What 360 feedback is not

Clearing up misconceptions early prevents most program failures:

• It's not a performance appraisal. Appraisals assess results against goals and feed pay decisions; a 360 assesses behaviours and competencies to guide development. They can complement each other, but they are different instruments.
• It's not a substitute for managing. A 360 doesn't replace a manager's ongoing feedback, one-on-ones, or difficult conversations. It supplements them.
• It's not a weapon. It should never be used to build a case against someone or to deliver anonymous criticism that no one will own.
• It's not a once-and-done verdict. A single 360 is a snapshot. Its value compounds when it's part of an ongoing development rhythm.

When everyone understands these boundaries, participants engage honestly and recipients receive the feedback as a gift rather than an ambush.

When to use 360-degree feedback (and when not to)

360 feedback shines in specific situations:

• Leadership and manager development, where how someone leads matters as much as what they deliver.
• High-potential development, to give rising talent a clear, rounded view of their strengths and blind spots.
• Team and behavioural development, where collaboration, communication, and influence are central to the role.
• Coaching support, giving a coach concrete, multi-source data to work with.

It's a poor fit — or needs great care — in other cases:

• For pay or promotion decisions, where it distorts incentives and invites gaming.
• In a low-trust environment, where feedback will be used to settle scores rather than to help.
• For very new employees, who haven't worked with raters long enough for meaningful input.
• When leaders won't act on it, since a 360 that leads to nothing breeds cynicism faster than no 360 at all.

A useful test: if you can't honestly say the primary purpose is the recipient's development and that the organisation will support follow-up, hold off until you can.

Designing the 360 questionnaire

The questionnaire is the engine of the process. A good one is built around clearly defined competencies and behaviours that matter for the role and the organisation's values, with a mix of rating-scale and open-text questions.

Choose the competencies

Start by selecting a focused set of competencies — typically five to eight — rather than an exhaustive list. Common, broadly applicable competencies include:

• Communication: clarity, listening, and openness.
• Collaboration and teamwork: how well the person works across people and teams.
• Leadership and people development: for those who manage or influence others.
• Accountability and reliability: following through and owning outcomes.
• Adaptability: handling change and ambiguity.
• Problem-solving and decision-making: judgement and initiative.
• Emotional intelligence: self-awareness and managing relationships.
• Alignment with company values: living the behaviours the organisation prizes.

Tailor the list to the role level. A 360 for a senior leader should weight strategic and people-leadership competencies; one for an individual contributor should focus on collaboration, communication, and craft.

Write behaviour-based questions

The best 360 questions describe observable behaviours, not vague traits. "This person communicates expectations clearly and checks for understanding" is far more useful than "This person is a good communicator." Behavioural framing makes ratings more reliable and feedback more actionable.

Use a consistent rating scale — for example, a five-point scale from "rarely" to "consistently," ideally with a "not observed / can't assess" option so raters don't guess about behaviours they haven't seen. Keep the questionnaire short enough to complete thoughtfully; fatigue produces careless ratings.

Include open-text questions

Numbers tell you where to look; words tell you why. Always include a few open-ended questions, such as:

• What should this person keep doing because it's working well?
• What should this person start doing to be more effective?
• What should this person stop doing or do less of?
• What is one strength you'd want them to leverage more?
• What is one development area that, if improved, would have the biggest impact?

This "start / stop / keep" structure is simple, memorable, and produces specific, constructive comments.

Sample 360 questions by competency

To make this concrete, here are illustrative rating-scale items you can adapt:

Communication - Communicates ideas and expectations clearly. - Listens actively and seeks to understand others' views. - Shares information openly and in a timely way.

Collaboration - Works effectively across teams and functions. - Offers help and shares credit generously. - Handles disagreements constructively.

Leadership / people development (for managers) - Sets a clear direction and priorities for the team. - Gives regular, useful feedback to team members. - Supports the growth and development of others.

Accountability - Follows through on commitments. - Takes ownership of mistakes and learns from them. - Delivers quality work reliably.

Adaptability - Responds constructively to change. - Stays effective under pressure or ambiguity. - Seeks out and acts on new information.

Pair each cluster with one open-text prompt so raters can explain their ratings in their own words.

Choosing raters

Who provides feedback shapes its credibility. A few principles keep rater selection fair and useful:

• Include a balanced mix. For a manager being assessed, that means their own manager, a sample of peers, and several direct reports, plus the self-assessment.
• Choose people with real working knowledge. Raters should have worked closely enough with the recipient to comment meaningfully.
• Use enough raters per category to protect confidentiality. For peers and direct reports, aggregate responses and only report a category's results when there are enough respondents (commonly a minimum threshold like three) so individuals can't be identified.
• Involve the recipient and manager in selection, with a check. Letting the recipient nominate some raters increases buy-in, but HR or the manager should ensure the list isn't stacked with only friendly voices.
• Keep rater loads reasonable. People asked to complete dozens of 360s in a cycle rush them. Spread the load.

The aim is a representative, credible panel — not the largest possible one.

Confidentiality and anonymity

Anonymity is the lever that unlocks honesty, but it must be handled thoughtfully. The standard approach is that peer and direct-report feedback is aggregated and anonymised, while the manager's feedback is typically attributable (since the recipient knows who their manager is). To make anonymity real and safe:

• Report grouped categories only above a minimum respondent threshold.
• Aggregate scores and present themes from comments rather than raw, attributable quotes that could identify a rater.
• Set ground rules that comments must be constructive and behaviour-focused, and consider light moderation of open text to remove anything personal or abusive.
• Be transparent about how anonymity works so raters trust it and recipients don't try to guess who said what.

Anonymity is for candour, not for cowardice. The framing should always be "honest, constructive, and owned in spirit," even when individual ratings are aggregated.

Running the 360 cycle: step by step

A disciplined process keeps the experience fair and the data clean.

1. Define the purpose and scope. Decide who is being assessed, why, and how results will (and won't) be used. Communicate this clearly — especially that it's developmental.
2. Build or adapt the questionnaire. Select competencies and finalise rating and open-text questions for the role level.
3. Select raters. Assemble a balanced, credible panel for each recipient, respecting confidentiality thresholds.
4. Brief everyone. Tell raters how to give useful, behaviour-based feedback and reassure them about anonymity. Tell recipients what to expect.
5. Collect responses. Open the survey for a defined window, with reminders. Keep it short enough to complete properly.
6. Compile the report. Aggregate ratings, surface gaps between self and others, and theme the comments. Present results clearly and visually.
7. Deliver feedback supportively. Share the report in a structured conversation — ideally with the manager, an HR partner, or a coach — not by silently emailing a PDF.
8. Create a development plan. Translate insights into two or three concrete development goals with actions and support.
9. Follow up. Revisit progress in one-on-ones and consider a lighter re-check later to measure change.

Steps seven through nine are where the value lives. Many programs invest heavily in steps one through six and then drop the ball on the part that actually changes behaviour.

Turning feedback into development

A 360 report is raw material, not a result. The transformation happens in how it's received and acted on.

Deliver it as a conversation. The recipient should walk through the report with a trusted, skilled person who can help them interpret it, manage the emotional response, and separate signal from noise. Dumping a report on someone with no support is the most common way to do harm.

Look for patterns, not single data points. One low rating or one harsh comment is noise; a consistent theme across raters is signal. Encourage recipients to focus on patterns and on the gaps between self-perception and others' views.

Prioritise ruthlessly. Nobody improves on ten things at once. Pick two or three development priorities where change would have the biggest impact, and let the rest go for now.

Build a concrete plan. For each priority, define what "better" looks like, the specific actions to get there, the support needed (coaching, training, a stretch assignment), and how progress will be checked. Vague intentions don't change behaviour; specific commitments do.

Close the loop with raters. Without breaching anonymity, a recipient who tells their team "I heard I can improve X, and here's what I'm working on" turns feedback into visible growth and encourages future candour.

Reading and interpreting a 360 report

A 360 report can feel overwhelming at first glance — pages of numbers and comments. Teaching recipients (and managers) how to read it well is part of the job. A few interpretation principles help.

Start with the self-versus-others gap, often the richest insight. Three patterns recur. A blind spot appears where others rate a behaviour lower than the person rates themselves — these are the areas the person doesn't realise are holding them back, and they deserve the most attention. A hidden strength appears where others rate higher than the self-rating — the person undervalues something they should lean into with more confidence. And aligned views, where self and others broadly agree, confirm an accurate self-image and can be quickly acknowledged.

Next, separate signal from noise. A single outlier rating or one sharp comment is rarely worth agonising over; a theme echoed across several raters and reflected in both scores and comments is the real message. Encourage recipients to resist the natural pull to fixate on the one negative line and overlook the consistent, balanced picture.

Then look at spread, not just averages. If peers' ratings on a competency are tightly clustered, the perception is consistent; if they're widely split, the person may behave very differently with different people or in different situations — itself a useful insight worth exploring.

Finally, read the open-text comments for actions, not verdicts. The "start / stop / keep" answers usually point straight at concrete behaviours to adjust, which is exactly what a development plan needs.

A worked interpretation example

Imagine a team lead whose report shows high self-ratings on communication but noticeably lower peer ratings, with comments like "shares decisions after they're made rather than involving us." That gap is a textbook blind spot: the lead believes they communicate well because they do inform people, but peers experience a lack of involvement in the decision itself. The development action almost writes itself — involve the team earlier, not just announce outcomes. Contrast that with the same lead's accountability scores, where self and others both rate highly and comments praise reliable follow-through. That's an aligned strength to acknowledge and protect, not a development priority. Working through the report this way — gap by gap, theme by theme — converts an intimidating document into two or three clear, motivating commitments.

Training raters to give useful feedback

The quality of a 360 is capped by the quality of the input. A short briefing for raters pays for itself many times over. Encourage them to comment on specific, observable behaviours rather than personality ("In meetings, they tend to interrupt before others finish" beats "they're rude"). Ask them to be balanced, noting both strengths and development areas, since all-positive or all-negative input is less useful. Remind them to write constructively, as if the goal is to help a colleague grow — because it is. And reassure them that aggregated, anonymised feedback is safe to give honestly. When raters understand how to contribute well, the resulting report is sharper, fairer, and far more actionable.

How 360 feedback compares with other methods

It helps to position 360 feedback against neighbouring tools so teams use each for what it does best.

The point isn't that one replaces another — it's that 360 feedback fills a specific gap (how an individual's behaviour is perceived from all sides) that appraisals and surveys don't address well. Used together, with clear boundaries, they give a far richer picture than any single instrument.

Cultural considerations

In many workplaces — and this is worth attending to in hierarchical or relationship-oriented cultures — giving candid upward or peer feedback can feel uncomfortable, and recipients may take feedback personally. A few adjustments help the process land well. Emphasise repeatedly and credibly that the purpose is development, not judgement, so people lower their defences. Protect anonymity rigorously, because the fear of damaging a relationship is the biggest suppressor of honest input. Frame the language around behaviours and growth rather than scoring people. And model it from the top: when senior leaders openly receive their own 360 results and talk about what they're working on, it signals that feedback is safe and normal, which does more to build a feedback culture than any policy statement.

Common 360-degree feedback mistakes

Programs fail in predictable ways. Avoid these:

• Tying it to pay or promotion. This is the cardinal sin; it kills honesty and breeds gaming.
• No follow-up. Collecting feedback and doing nothing is worse than not asking. It teaches people the exercise is theatre.
• Too many raters or too many questions. Survey fatigue produces careless data.
• Weak anonymity. If raters fear identification, they soften or skew their input.
• Delivering reports without support. Unsupported feedback can demoralise rather than develop.
• Using it on the wrong people. New hires, or people in a low-trust setting, aren't good candidates.
• One-and-done. Treating a 360 as a single event rather than part of an ongoing development rhythm wastes most of its potential.
• Ignoring rater quality. A panel stacked with only allies or only critics produces a distorted picture.

Each of these is a design or follow-through failure — and each is preventable.

A simple 360 process template

Here's a lightweight template you can adapt for each cycle:

• Recipient: [name, role, level]
• Purpose: Development (state explicitly)
• Competencies assessed: [5–8 chosen for the role]
• Raters: Manager (1), Peers (3–5), Direct reports (3–5 if applicable), Self (1), Internal customers (optional)
• Questionnaire: [X rating items per competency on a consistent scale + 3–5 open-text questions]
• Confidentiality rule: Categories reported only with ≥3 respondents; comments themed, not quoted verbatim
• Timeline: Brief (week 1) → Collect (weeks 2–3) → Report (week 4) → Feedback conversation (week 5) → Development plan (week 5) → Follow-up (ongoing)
• Outputs: Aggregated report, self-vs-others gap analysis, 2–3 development goals, support plan
• Owner: [HR partner / manager / coach]

Keep it light, repeatable, and focused on the development outcome rather than the paperwork.

Measuring whether the program works

Like any people process, 360 feedback should be evaluated, not just run. A few indicators tell you whether it's delivering. Completion and participation rates show whether people see it as worthwhile or a chore; consistently low completion is a signal that the process is too long, poorly communicated, or distrusted. Quality of feedback — the proportion of comments that are specific and behaviour-based rather than vague or empty — reflects how well raters were briefed. Development-plan follow-through is the real test: are recipients setting concrete goals from their reports, and are those goals showing up and progressing in one-on-ones? Over longer horizons, a re-check on prior development areas in a later cycle reveals whether behaviours actually shifted. And gathering brief participant sentiment ("Was this useful? What would make it better?") helps you refine each round. If the data shows feedback collected but rarely acted on, fix the follow-up before running another cycle — that is almost always where value leaks away.

Building a lasting feedback culture

The deepest payoff from 360 feedback isn't any single report; it's the gradual normalisation of honest, constructive feedback across the organisation. A one-off 360 in a vacuum can feel jarring, but when it sits within a culture of regular one-on-ones, real-time feedback, and visible follow-through, it becomes a natural high point in an ongoing conversation rather than an annual ordeal. Leaders accelerate this by sharing their own development areas openly, by acting visibly on what they hear, and by treating feedback as a routine part of growth rather than a verdict. Over time, the goal is a workplace where people seek feedback because they trust it will help them — at which point the formal 360 is simply a structured, periodic deepening of something the organisation does every day.

How technology supports 360 feedback

Running a 360 manually — emailing surveys, chasing responses, hand-collating ratings, protecting anonymity in a spreadsheet — is slow and error-prone, and it's easy to accidentally break confidentiality. A performance or HR platform with 360 capability removes the drudgery and the risk by:

• Configuring competencies and questionnaires once and reusing them across cycles and role levels.
• Managing rater selection and invitations with confidentiality thresholds built in.
• Collecting responses and sending reminders automatically, with progress visible to HR.
• Aggregating ratings and theming comments into clear, visual reports that protect anonymity.
• Linking results to development plans and goals, so feedback flows into action rather than a forgotten file.

When 360 feedback lives alongside goals, one-on-ones, and reviews in the same system, it stops being a once-a-year scramble and becomes a natural part of how the organisation develops its people.

Frequently asked questions about 360-degree feedback

1. What is the main purpose of 360-degree feedback? Its primary purpose is development — raising an individual's self-awareness by showing how their behaviours and competencies are perceived by people around them (manager, peers, direct reports, and themselves). It is designed to guide growth, not to calculate a rating or decide pay.

2. Should 360 feedback be used for appraisals or pay decisions? Generally no. Tying 360 feedback directly to pay or promotion tends to destroy the honesty that makes it valuable and invites gaming and politics. It works best as a developmental complement to a separate appraisal process that assesses results against goals.

3. How many raters should be involved? Enough to be representative and to protect anonymity, but not so many that the process becomes a burden. A common pattern is the manager, three to five peers, three to five direct reports (for people managers), and a self-assessment. Report grouped categories only when there are enough respondents — often a minimum of three — to keep feedback anonymous.

4. How do you keep 360 feedback anonymous? Aggregate peer and direct-report responses and report a category only above a minimum respondent threshold, present themes rather than attributable quotes, and set ground rules for constructive, behaviour-focused comments. The manager's feedback is usually attributable, since the recipient knows who their manager is.

5. What kinds of questions should a 360 include? A mix of behaviour-based rating items grouped by a focused set of competencies (such as communication, collaboration, accountability, and leadership) on a consistent scale, plus a few open-text questions — typically a "start / stop / keep" structure — so raters can explain their ratings in their own words.

6. How often should 360 feedback be run? There's no fixed rule, but annually or as part of a development or leadership program is common, with lighter follow-up checks to measure progress. The key is that it's part of an ongoing development rhythm rather than a one-off event, and that the organisation can support meaningful follow-up each time.

7. What if someone reacts badly to their 360 results? Strong reactions are normal, which is exactly why results should be delivered in a supportive conversation rather than emailed in isolation. A skilled manager, HR partner, or coach can help the recipient process the emotion, focus on patterns rather than single comments, and turn the feedback into a constructive development plan.

8. Can small companies run 360-degree feedback? Yes, with care. Small teams must pay extra attention to anonymity, since fewer raters make individuals easier to identify — keeping feedback themed and aggregated, and being thoughtful about which roles to assess. A simple, well-communicated process and the right tooling make 360 feedback workable even at small scale.

Conclusion

360-degree feedback, used as it's meant to be — for development, with honest input, strong confidentiality, and committed follow-up — gives people something rare and valuable: a clear, multi-perspective view of how they actually show up at work, and a concrete path to grow. Used carelessly, or wired into pay, it does more harm than good. The design choices you make up front, and the support you wrap around the feedback afterwards, determine which outcome you get.

If you want to run 360 feedback that develops people rather than just generating reports, the right platform makes all the difference. CozyHR lets you configure competencies and questionnaires, manage raters with confidentiality built in, generate clear and anonymous reports, and link the insights to development goals and one-on-ones — so feedback turns into growth, not a forgotten PDF. If you're planning your next performance cycle, it's worth seeing how much smoother CozyHR makes the whole process.

This article is for general guidance only and does not constitute professional HR or legal advice. Adapt 360-degree feedback to your organisation's context and culture, and consult a qualified professional where appropriate.