Plan and run a 360 assessment
Follow up on 360 feedback development
Keep the development conversation going after the report is delivered. Review what people have tried, what others have noticed, and what needs to change next.
Agree on the first check-in when you write the plan
Choose a review date that gives the subject time to practice in their actual work. Name who will review the plan with them and what they should bring to the conversation.
Keep the review focused: What did you try? What happened? What feedback did you receive? What will you keep doing or adjust?
If progress has stalled, check whether the goal is clear, the practice opportunities exist, and the agreed support is available. Adjust the plan to fit the work instead of simply adding more activities.
Ask for feedback on the behavior being practiced
With the subject’s agreement, invite relevant colleagues to comment on specific changes. “Have task handoffs been clearer?” is easier to answer than “Am I a better leader?”
Thank people for contributing and explain, where appropriate, what the subject is working on. Keep individual reports and confidential responses within the reporting arrangements agreed for the project.
Use observations and work examples alongside the subject’s reflection. Completing an action plan is useful, but it is the practice and its effect that matter.
Repeat the assessment for a useful reason
A repeat 360 can help explore progress after people have had enough time and opportunity to change their behavior. Choose the interval to fit the development goals and working context; an annual assessment is not necessary for every program.
If you want to compare results, use compatible questions and scales. Consider changes in the subject’s role, responsibilities, and evaluator groups when interpreting differences.
A change in scores is one piece of evidence. It does not, on its own, establish that the development work caused the change.
Review the program as well as individual plans
Ask whether people received their reports, had useful conversations, and could access the promised development support. Review workload, communications, and any practical obstacles before the next project.
Completion rates help you understand participation. They are not proof of development impact. Look for useful examples of behavior change and lessons that will improve the next assessment.
Before you move on
- Development check-ins are scheduled and supported.
- Progress is reviewed through concrete observations.
- Any repeat assessment has a clear purpose and comparable content.
Useful resources
Need help with the platform?
Panoramic Feedback provides the software, platform training, and optional project administration. Your consultant or internal team leads interpretation, coaching, and development planning.
