The feedback process for a leadership 360 review gathers structured observations from a manager, peers, direct reports, and other people who work closely with the leader. Its purpose is development: identify repeatable strengths, clarify the leader’s impact, and choose a small number of behaviors to improve.
Keep the process confidential and behavior-based. Raters should describe what they observed, the effect it had, and what the leader could do differently—not assign personality labels or speculate about motives.
How the feedback process works
Set the purpose and select raters
Start by defining the decision the review should support. For example, the goal may be to improve delegation, build trust during change, or prepare a manager for a larger role. Share the purpose, timeline, confidentiality rules, and how results will be used before asking anyone to participate.
Choose a balanced group of roughly six to twelve raters, depending on the leader’s role and team size:
- Manager: offers context on priorities, results, and role expectations.
- Peers: describe collaboration, influence, and cross-functional impact.
- Direct reports: reveal how the leader’s behavior affects the team’s work and experience.
- Partners or customers: add evidence about communication and external impact.
- Self-rating: shows where the leader’s view matches or differs from others’ views.
Let raters opt out if they cannot provide informed feedback. Use anonymous reporting for small groups when possible, and do not promise anonymity if a group is too small to protect it.
Collect, synthesize, and debrief
Use a consistent rating scale and a short set of open questions. Combine scores with written comments, separating results by rater group only when the group is large enough to protect confidentiality. Look for patterns across sources rather than treating one dramatic comment as a finding.
A trained manager, coach, or facilitator should lead the debrief. Begin with strengths, then examine gaps between self-perception and others’ experience. Ask the leader what feels accurate, surprising, or worth investigating; the debrief should create ownership, not defensiveness.
Plan follow-up
End the review with one to three development priorities. Record the target behavior, the situations where it matters, the action the leader will take, and how progress will be observed. Schedule check-ins at 30, 60, and 90 days rather than treating the report as a one-time event.
360 review questions for strengths, impact, and growth
Good questions ask about observable actions and their effects. Avoid prompts such as “Is this person inspiring?” Replace them with questions that help raters recall specific situations.
Strengths and impact
- What does this leader do that helps the team perform well?
- Which leadership behavior should this person continue or do more often?
- Describe a recent situation in which this leader improved a decision, relationship, or result.
- How does this leader create clarity about priorities, roles, or decisions?
- When does this leader communicate especially well, and what makes the approach effective?
Growth and next steps
- What behavior could this leader change to improve team effectiveness?
- Describe a situation in which the leader’s approach created confusion, delay, or rework.
- What should this leader do more, do less, or do differently?
- How does the leader respond when challenged, and what would make that response more effective?
- What is one practical action this leader could take in the next 30 days?
Ask raters to include the situation, behavior, and impact: “During the project handoff, the priorities changed twice without explanation, so the team repeated work.” This format produces usable evidence instead of a vague judgment.
360 feedback examples that people can use
Positive feedback
Specific praise connects a behavior to its effect. Useful examples include:
- “You summarize competing views before making a decision. That helps the group move forward without dismissing concerns.”
- “In the last two planning meetings, you clarified the owner and deadline for each action. The team left with fewer follow-up questions.”
- “You gave me room to solve the client issue, then checked in without taking over. I felt trusted and still had support.”
Developmental feedback
Developmental comments should describe the change needed without attacking character:
- “In cross-team meetings, you often answer before others finish. Pausing and inviting the speaker to complete the point could improve participation and decision quality.”
- “You provide strong direction during urgent work, but the reason behind the priority is sometimes unclear. Explaining the trade-off may help the team make better decisions independently.”
- “When a proposal is challenged, your replies become brief and fast. Asking one clarifying question before responding could make disagreement feel more productive.”
Turn feedback themes into a development plan
Find themes, not outliers
Group comments by behavior, such as delegation, listening, strategic communication, or follow-through. A theme is stronger when it appears in several comments, comes from more than one rater group, or matches a meaningful difference between self and other ratings.
Do not call an isolated comment consensus. Check its context and wording, and discuss it with the facilitator or leader. A single comment may identify a useful situation to explore, but it should not automatically become a development priority.
Set measures and follow up
Convert each priority into an action plan with four parts:
- Behavior: “Delegate decision ownership instead of keeping final approval.”
- Practice: “At each weekly meeting, assign the outcome, decision rights, and deadline.”
- Measure: “Ask two team members monthly whether ownership and expectations are clear.”
- Review date: “Revisit progress with the manager after 30 and 90 days.”
Repeat selected questions in later check-ins or run a shorter pulse review. Progress is credible when people can point to a visible behavior change and a better result, not merely a higher score.