What to Do After Your 360 Review: Turning Feedback Into Growth
By Panoreview Team
Your 360 review results just arrived. Themes, strengths, growth areas, suggested actions — all synthesized from anonymous peer feedback. You read through it, nod at the strengths, wince at a growth area or two, and then… nothing happens.
This is the most common failure mode in 360 feedback. The collection is excellent. The synthesis is clear. But the bridge between insight and behavior change doesn’t get built.
Read It Twice
The first read is emotional. You’ll fixate on the one critical comment and gloss over four positive themes. This is normal. Don’t make decisions during the first read.
The second read — ideally the next day — is analytical. Look for patterns:
- What appears more than once? A theme mentioned by three respondents is a signal. A theme mentioned by one is an observation. Weight your attention accordingly.
- Where do self-ratings and peer ratings diverge? The gap between how you see yourself and how your team sees you is the highest-value signal in any 360 review. A gap doesn’t mean you’re wrong — it means your team’s experience of your behavior differs from your intent.
- What has citations? Themes grounded in specific examples are more actionable than abstract patterns. “Strong mentorship [4 mentions]” with linked excerpts tells you exactly what your team values.
Pick Two Growth Areas, Not Five
The instinct after a 360 review is to fix everything at once. This produces scattered effort and no visible progress.
Pick two growth areas — ideally the ones with the most respondent agreement and the clearest suggested actions. Ignore the rest for now. You’ll address them in the next review cycle.
Two focused goals create more behavior change than five vague intentions.
Write Goals That Are Specific
Weak goal: “Improve delegation.”
Strong goal: “Hand off at least two tasks per sprint to team members with relevant experience. Track handoff outcomes in sprint retros for the next quarter.”
The difference: the strong goal has a specific action (hand off tasks), a measurable quantity (two per sprint), a named audience (team members with relevant experience), and a verification mechanism (sprint retros).
If you can’t measure whether you’ve achieved a goal, it’s an aspiration, not a plan.
Share Selectively
Goals work best when someone else knows about them. The accountability isn’t surveillance — it’s support.
Consider sharing your goals with:
- Your manager. They can create opportunities for the behavior you’re developing. If your goal is delegation, a manager who knows this can proactively assign stretch projects to your direct reports.
- A peer. Someone at your level who can give you informal feedback on whether the change is visible. “I noticed you handed off the API docs to Chris this sprint — that’s exactly what your 360 suggested” is the kind of reinforcement that sustains behavior change.
- Nobody. Some goals are personal. If sharing would create awkwardness, work on them privately and let the next 360 review cycle measure progress.
The key: share goals, not the underlying feedback. Your goals should stand on their own without exposing what your reviewers said.
Track Progress, Not Perfection
A goal status of “in progress” is success. It means you’re working on it. Behavior change takes weeks, not days.
Useful tracking looks like:
- Not Started → you haven’t begun yet. Reassess whether this goal is actually your priority.
- In Progress → you’re actively working on the behavior. Note specific instances where you demonstrated the change.
- Complete → the behavior has become consistent enough that your next 360 reviewers will notice it. Complete doesn’t mean perfect — it means the pattern has shifted.
Add progress notes as you go. “Feb 15: Delegated the API migration to Devon. Resisted the urge to take it back when the first approach didn’t work.” These notes become evidence when you revisit goals before your next review cycle.
When the Feedback Feels Wrong
Sometimes a theme appears that you genuinely disagree with. Three people say your communication needs work, but you believe you communicate clearly and frequently.
Before dismissing it, consider: feedback describes the recipient’s experience, not the sender’s intent. You may communicate frequently — but if the message isn’t landing, the frequency doesn’t help.
The constructive response isn’t to argue with the feedback. It’s to ask: “What would my team need to see for this theme to disappear in the next review cycle?” Then try that, and let the data show whether it worked.