How to Turn 360 Feedback Into a Development Plan
A 360 report is only useful if something changes afterwards. Most people read their results, feel motivated for a week, and then go back to old habits because the report never became a plan. This guide shows how to pick one or two goals from your feedback, write them as behaviours other people can notice, and follow them for 90 days. It includes a template you can copy and three worked examples.
Why most 360 results are never used
The usual reasons are simple: too many goals at once, goals written as traits ("be more strategic") instead of behaviours, and no date to check progress. A good development plan fixes all three. It is short, it names what you will do differently in specific situations, and it says when you will ask for feedback again.
Write the plan within two weeks of receiving the report, while the comments are still fresh.
Step 1: choose one or two goals, not five
- Start with the biggest gap between how you rated yourself and how others rated you. Gaps are where your view of yourself is least accurate, so they usually matter most.
- Prefer a theme that several reviewer groups mention (for example both peers and direct reports), not one comment from one person.
- Ask which change would help your current role or next step the most. A small improvement in something you do every day beats a big plan for something rare.
- Keep one strength in the plan too. Using a strength more deliberately is often the fastest visible progress.
Step 2: write each goal as a behaviour
Turn the theme into something you will do in a specific situation, so that colleagues can notice it. Instead of "improve communication", write "after every team meeting, send a three-line summary with decisions, owners and dates". Instead of "delegate more", write "each Monday, hand one task I would normally do myself to a team member, and agree what done looks like".
Add how you will know it is working: a sign you can observe, such as fewer follow-up questions, or a teammate leading a meeting you used to run.
Development plan template
Copy and fill in
Goal (from my 360): [theme, e.g. listening in meetings] What the feedback said: [the rating gap or two or three comments, in your own words] What I will do differently: [behaviour + situation] How others will notice: [observable sign] Support I need: [manager, coach, course, a peer to practise with] Check-in dates: [30 days] [60 days] [90 days] Who I will ask for quick feedback: [two or three names] Strength I will use more: [one strength from the report and where to use it]
Three worked examples
New manager: delegation
Feedback: rated own delegation 4/5; direct reports gave 2.6/5. Comments: "takes tasks back when deadlines get close". Behaviour: when I hand over a task, agree the result and the deadline, then ask for an update halfway instead of taking it back. Sign: team members finish the tasks they started; fewer late evenings for me. Check-in: ask two team members in one-to-ones after 30 and 60 days; repeat the 360 after six months.
Senior engineer: communication with non-engineers
Feedback: peers outside engineering rated clarity 2.8/5; engineering peers 4.2/5. Comment: "great solutions, hard to follow the explanation". Behaviour: start every update for non-engineers with the decision needed and the impact, then the detail; one diagram instead of a long message. Sign: product and sales colleagues ask fewer follow-up questions. Check-in: ask the product manager for a quick rating after the next two releases.
Team lead: listening in meetings
Feedback: "jumps in with the answer" appeared in four comments; self-rating on listening was the highest of all. Behaviour: in team meetings, ask at least two people for their view before giving mine; summarise what I heard before deciding. Sign: quieter team members speak more; decisions are questioned less afterwards. Check-in: ask a peer to watch one meeting a month and give a two-line note.
A 90-day rhythm that works
- Week 1: share the goal with your manager (and coach, if you have one) and with two or three colleagues who see you in the situations that matter.
- Every week: note one moment where you tried the new behaviour and what happened. Two lines are enough.
- Day 30 and day 60: ask your chosen colleagues one question: "What have you noticed since we last talked?"
- Day 90: decide whether to keep, adjust or replace the goal.
- Six to twelve months: repeat the 360 with the same questions, so you can see what changed.
For managers, HR and coaches
Let the person choose the goal. Plans people pick themselves are the ones they follow. Your role is to help them turn a theme into a behaviour, find practice opportunities in real work, and keep the check-in dates.
Keep the report itself private unless the person decides to share it, and talk about the plan, not about who said what.
How to read a 360 report · Areas for improvement: examples · 360 feedback for coaches
Where AI360Feedback helps
The AI360Feedback report compares your self-rating with each reviewer's view, highlights the largest gaps and the themes in the comments, and suggests practical next steps for the areas that need work. The AI suggests; you decide which goal to pick. Coaches and HR teams can use AI360Feedback PRO to run 360s for several people from one dashboard, with results by reviewer group, and run the same questionnaire again later to see progress.
Frequently asked questions
How many goals should a development plan have after a 360?
One or two. More than that spreads attention too thin, and colleagues will not notice any single change.
How long should a 360 development plan last?
Plan in 90-day cycles with check-ins at 30 and 60 days, and repeat the 360 after six to twelve months to measure progress.
Should I share my development plan?
Share the goal, not necessarily the report. Telling your manager and two or three colleagues what you are working on makes it easier for them to notice and give quick feedback.
What if I disagree with my 360 feedback?
Treat it as information about how you are seen, not a verdict. Ask one or two trusted colleagues for an example before deciding whether to make it a goal.
Start with a clear picture
A good plan needs good feedback. Rate yourself, invite colleagues to answer anonymously, and get an AI report that shows where your view and theirs differ. Free for individuals.
Start my free 360Related
- How to Ask Colleagues for Feedback (With Templates)
- 360 Feedback for Coaches
- AI-Powered 360 Feedback: How It Works and How to Choose a Tool
- Best 360 Feedback Tools in 2026
- How to Write a Self-Evaluation (with Examples by Role)
- 360 Feedback for Small Businesses
- How to Read a 360 Feedback Report
- The Big Five Personality Traits at Work
- Areas for Improvement in a Performance Review (with Examples)
- How to Write a Year-End Performance Review for Your Team
- Upward Feedback: How to Ask Your Team About Your Management
- 360 feedback questions by role
- 360 feedback comment examples