360-Degree Feedback: Turn Results Into a Practice Plan

360-degree feedback gathers perspectives from people who work with an employee, alongside the employee’s own view. Its value depends on what happens after the report: selecting a useful behavior, practicing it in real work and checking whether colleagues experience a difference.

Updated October 27, 2026.

This guide focuses on the follow-through after a developmental 360. It provides a debrief method, an example action plan and a follow-up question set. A rating is one perspective collected in a particular context, not a diagnosis or an objective measure of someone’s potential.

Before the survey: make the purpose clear

• Explain who will see individual answers, comments and aggregated results.
• Choose questions about observable behavior and include “not enough opportunity to observe.”
• Set reporting rules that protect respondents in small groups. Do not promise anonymity a report cannot provide.
• Explain whether the process is for development and how it relates to other employment decisions.
• Provide a supported debrief and time for practice, rather than ending the program at report delivery.

Use questions people can answer from experience

Agree on a recall period and response scale. Ask for a concrete example where it is safe and appropriate. Do not interpret a difference between self and colleague ratings as dishonesty: observers have different opportunities and contexts.

A debrief that produces one practice decision

1. Check the evidence. How many responses are there, from which groups and over what period? What might be missing?
2. Look for a pattern. Identify recurring observations, including strengths. Avoid building a plan around one isolated comment.
3. Ask for context. Discuss where the behavior matters and what conditions make it difficult.
4. Choose one action. The employee selects a practice they can influence and describes what colleagues would notice.
5. Agree on support. Name a manager or coach who will help with opportunities, feedback and obstacles.

Example: turning “listen more” into a practice plan

Illustrative example, not a customer case study. A team lead’s feedback suggests that colleagues do not always feel heard before a decision. The lead chooses this practice: “Before closing a discussion, summarize the concern I heard and ask whether I understood it.”

The employee does not need to agree with every concern. The aim is accurate understanding before explaining the decision. Use the employee development plan template to record the practice and support.

Check change without turning the process into surveillance

At follow-up, ask about a defined period: “When you raised a concern in the last four weeks, did the lead check their understanding before closing the discussion?” Include a no-opportunity response and an optional example. Ask whether the practice helped, not only whether it occurred.

Report response counts and changes in who responded. A higher score from a different respondent group is not necessarily improvement. A small pulse is useful developmental evidence, not proof that the 360 caused a business result. Avoid ranking employees by scores from small or incomparable groups.

What to do when nothing changes

• No practice opportunity: select a more relevant task or extend the observation period.
• Action too broad: reduce it to one observable step.
• Support missing: address workload, authority or manager behavior.
• Action happens but does not help: examine quality and adapt the practice.
• Feedback is contradictory: investigate contexts rather than averaging away the disagreement.

Use the report as the start of development

GWork’s approach connects growth priorities with small actions and follow-through. If a 360 accompanies a leadership learning program, the free post-training action plan kit helps plan the next practice opportunity. The measurement guide helps distinguish participation, application and outcomes. Discuss supporting a cohort with GWork when you have a defined behavior and a manager-support plan.