What is 360 feedback?
360 feedback is a process in which a person receives structured feedback from several people who observe their work. These may include a manager, peers, direct reports, project colleagues or clients, alongside the person's self-assessment. The aim is to understand strengths and development needs from more than one perspective.
Ratings and comments contribute different information. Ratings can show a pattern; comments can describe the situations behind it. Neither becomes a development plan automatically. The recipient needs time to interpret the evidence, choose a useful action and review progress.
This guide explains how to run the process, write helpful questions and turn a report into practical development. It also covers the limits of anonymity and how to interpret disagreements without treating every gap as a personal failing.
When is a 360 useful?
A 360 can help when someone's work affects people in different ways and no single observer sees the whole picture. A project leader might be effective with senior sponsors but leave delivery teams uncertain about changing priorities. Equally, feedback from several groups may confirm a strength worth using more deliberately.
It is less useful when raters have little opportunity to observe the person, when the purpose is unclear or when nobody will support follow-through. Collecting more perspectives does not remove bias, settle factual disputes or establish an objective ranking of employees.
Explain whether the exercise is developmental and how its results will be used. CCL's implementation guidance places emphasis on clear outcomes, trust and confidentiality. The people invited should understand the process before they contribute.
A practical seven-step process
1. Agree the purpose and the development question
Start with the work the person needs to do well. For example: “How can I make changing project priorities clearer to the teams affected?” That gives the feedback a practical direction. Avoid collecting a very broad assessment simply because a template contains many competencies.
State who receives the report and who supports the debrief. If there are any uses beyond development, explain them before collection. The participant should not discover later that material presented as confidential coaching input has become a wider performance ranking.
2. Choose relevant raters
Invite people who have enough recent experience of the work to answer meaningfully. Include varied perspectives where they are relevant, rather than only the recipient's closest allies or the most senior people available.
Decide how nominations are reviewed, how groups are defined and what happens if someone declines. A manager may be identifiable by role, while peer and direct-report responses may require group reporting. An “insufficient opportunity to observe” option helps avoid forced judgments.
3. Select clear behaviors and questions
Ask about observable behavior. “Explains the reason when priorities change” is easier to interpret than “Is an excellent communicator.” Keep the question focused on one idea, use a relevant reference period and explain the response scale.
If using a formal instrument, follow its guidance and licensing requirements. Editing a validated scale can change what it measures. A custom practical questionnaire may be useful, but it should not be described as validated merely because it uses familiar competencies.
4. Explain confidentiality and collect the feedback
Tell raters how their responses will be handled, including comments, exports and administrator access. State the reporting rules, reminder process and expected time commitment. Choose accessible collection and suitable language support.
Keep the recipient, rater relationship and assessment cycle correctly associated. Where reporting must be confidential, access to those relationships needs particular care. Anonymous or grouped feedback should not unexpectedly become a named follow-up list.
5. Review the report before the debrief
Check missing responses, scale interpretation, group composition and calculation rules. Review comments for context and identifying details. A qualified reviewer should examine proposed themes, especially when software or AI helped prepare them.
The report should distinguish an observed pattern from an interpretation. “Peers rated the behavior more favorably” is a finding. “The person ignores their direct reports” is a much stronger conclusion that the ratings alone do not establish.
6. Choose a small, practical development action
Discuss strengths as well as concerns. Explore what the person recognizes, what surprises them and what further context is needed. Avoid spending the debrief trying to guess who wrote a comment.
Select an action that fits the work, with a way to practice it and receive feedback. One well-supported change is more useful than a long list of vague commitments. The recipient should understand why the action matters and what support is available.
7. Review the action and decide what comes next
Set a review point that allows a real opportunity to practice. Ask whether the behavior changed, where it was useful and what remains difficult. A short check-in may be appropriate; repeating the entire assessment immediately may add burden without new information.
If comparing later cycles, disclose changes in raters, role, questions and context. A higher score with a different rater group is not automatically proof of individual development.
Questions that invite useful feedback
Scroll horizontally to see all columns →
| Purpose | Example question | Why it helps |
|---|---|---|
| Clarify priorities | How consistently does this person explain the reason when work priorities change? | Focuses on a behavior colleagues can observe |
| Invite contribution | How consistently does this person make space for relevant views before deciding? | Explores a specific part of decision-making |
| Recognize a strength | What does this person do that helps you work effectively? Give an example if appropriate. | Connects a strength to its practical effect |
| Identify a change | What one change would make working with this person more effective? | Invites a focused suggestion |
| Provide context | In which situations is this behavior most helpful or difficult? | Avoids assuming the behavior is identical everywhere |
Adapt the language to the role and test it before launch. Tell contributors not to include unnecessary sensitive details or identify other people. A detailed example can help interpretation, but can also make its author recognizable.
A worked example: from feedback to practice
In this fictional example, Alex leads cross-team projects. Peer feedback generally describes clear decisions during planned meetings. Feedback from people doing the day-to-day work raises uncertainty when priorities change between meetings.
The reviewer sees a difference between situations, rather than immediately labeling Alex a poor communicator. The next question is whether decisions are explained consistently outside scheduled meetings. Alex recognizes that urgent changes are sometimes passed through short messages with little context.
Scroll horizontally to see all columns →
| Part | Development plan |
|---|---|
| Behavior to practice | When changing a priority, explain what changed, why and who is affected |
| Opportunity | The next four weekly planning cycles and any significant midweek changes |
| Support | A colleague reviews the clarity of the first two updates |
| Check | Ask whether the update makes the next action clear; note recurring questions |
| Review | Discuss what worked after four cycles and adjust the approach |
The goal is an observable practice, not simply “improve communication.” A later conversation can examine whether people understand changed priorities more easily. It should also consider workload, competing instructions and other factors outside Alex's control.
This example illustrates a development process, not a measured outcome. It does not imply that every difference between rater groups has one explanation or that a particular action will always work.
How to interpret scores and disagreement
Read the scale and group definitions first. A low number on one scale may mean something different on another. Check whether the report combines groups equally or weights every individual response equally; these choices can produce different overall scores.
Look for patterns across related behaviors, supporting comments and the situations raters observe. Agreement can confirm a strength or a shared concern. Disagreement can reveal context, different expectations or incomplete observation. Neither is automatically more valuable than the other.
Do not treat an isolated comment as a universal truth, but do not dismiss it simply because it is isolated. Its significance depends on content and context. Serious issues may need an appropriate separate process rather than being handled solely as a coaching theme.
Avoid converting every theme into a percentage. A small group of comments is not necessarily representative, and one comment can cover several ideas. Explain how themes were developed and where interpretation remains uncertain.
Protect confidentiality without overpromising
Grouping responses does not guarantee anonymity. A unique event, writing style or small reporting group can reveal a contributor. Filtering, exports and comparison between cycles can create additional identification risks.
Set reporting rules appropriate to the instrument and organization. Test whether those rules apply to text, summaries and downloads as well as charts. Be clear about any identified feedback, such as a sole manager's perspective.
AI-generated summaries also require review. A summary may repeat a recognizable incident or infer more than the source supports. Give each role access only to the evidence it is entitled to see, and avoid using an assistant to guess authorship.
Connect collection to analysis and follow-through
A repeatable process needs more than a form. Maintain question versions, rater-group definitions, calculation rules and access decisions. Local teams can use additional role-specific questions, while a limited shared core supports appropriate comparison.
Sopact's relevant role is helping a team manage collection, analysis and governance around recurring evidence. Validate the specific 360 controls before use, including recipient-rater relationships, confidentiality and any development-plan integration. Human review remains essential to interpreting sensitive feedback.
If selecting a platform, use the 360 feedback software buying guide. For planning a wider listening process, explore the employee experience solution. Keep the 360's developmental purpose clear within that broader program.
Frequently asked questions
Who participates in 360 feedback?
The recipient usually completes a self-assessment and receives feedback from relevant observers such as a manager, peers, direct reports or project colleagues. Choose raters based on meaningful observation of the work.
Is 360 feedback the same as a performance review?
Not necessarily. A 360 often supports development through several perspectives, while a performance review may serve broader appraisal decisions. Explain the purpose and permitted uses before collecting feedback.
Are comments more important than scores?
Both can help. Scores show patterns and comments add context. Their value depends on the instrument, source quality and interpretation, not a rule that one format is always superior.
Should the recipient try to identify who wrote a comment?
No. Focus on the behavior and context while respecting the process's confidentiality commitments. Questions about data handling should go through the responsible administrator or facilitator.
How often should a 360 be repeated?
Choose a cadence that allows meaningful practice and fits the instrument and program. Short development check-ins can happen between full assessments. Repeated measurement without an opportunity to act adds little value.
What should happen after the report?
Hold a thoughtful debrief, select a practical development action, arrange support and set a review point. The report is evidence for that conversation, not the end of the process.
Choose your next step
King Center
Related practice: using program feedback to support learning. This story does not demonstrate a 360 assessment or rater confidentiality controls.
Read the customer story →