Before You Launch a 360 Assessment for Leaders: Key Considerations

Over the past few weeks, I’ve held conversations about 360s with peers, coaching affinity groups, and vendors. This 3-part series is a distillation of themes from those discussions. Please let me know what you’d add from your experience!

Part 1: Get Clear on the WHY (Before the WHAT and the HOW)

When talent leaders are asked to “run a 360,” the impulse might be jump straight into the tactical weeds. How many leaders? When would we launch? Which tool? What’s the budget? I get it. Conducting a 360 is a multi-step process that should be planned and executed well, so these details matter. Before you go beast mode in Excel, I'd recommend taking a pause. Gather context. Ensure there’s a shared understanding of why this matters, why now, and what will happen when the feedback arrives.

Clarity around the purpose of the 360, organizational readiness, and other system-level considerations will inform every downstream decision, including tool selection, communication, confidentiality, and development planning.

Here are seven areas of inquiry to pursue to build a shared understanding:

1)    Why a 360?

What do we aim to learn? How will the feedback be used? Is this for development purposes only, or will the data feed into performance and/or succession? What do we hope to observe afterwards (e.g., hard conversations happening earlier, higher engagement scores, increased collaboration)? And can we connect the dots between those outcomes and what leaders will learn and do with 360 feedback?

2)    Are we ready for a 360 project?

How confident are we that people can share candid feedback without hesitation? What signals have we sent — through words and actions — that candor about leadership is welcome? When someone offers tough feedback, how does leadership typically respond? What have we learned from past feedback efforts? What strengths can we build on from prior development initiatives? A 360 project will amplify the culture that already exists.

3)    What leadership framework are we anchoring to?

Feedback needs a shared language, so whether you’re using an internal leadership competency model or an external framework, a 360 should serve to align with or complement your agreed-upon success factors. If it doesn’t, raters may disengage and leaders may dismiss the results.

4)    Who will help the leaders process the feedback?

The real value of a 360 comes in the meaning-making and insight generation with a skilled, certified debriefer. Leaders need structured coaching conversations that explore patterns, strengths, blind spots, and impact. And they need time to reflect and prioritize their top areas for development.

5)    How will the 360 connect to action?

What’s expected in terms of an actionable development plan? This is where many 360 projects stall. If we want leaders to lead differently after becoming aware of a gap between how they intend to show up and the actual impact they’re having, that’s behavior change. And behavior change requires visible experimentation. Without a clear bridge to action, the risk is that leaders view a 360 as an event rather than as a catalyst for change.

6)    What’s the role of the Manager?

Will Managers have input on the raters selected to contribute feedback on their direct reports? Will Managers help shape the leaders' development goals? Unclear expectations of the Manager’s role in a 360 can create tension in the system. Having roles clearly defined early in the process helps set the stage for a smooth implementation. Moreover, when employees perceive their manager as supportive and invested in them, they are more likely to internalize feedback.

7)    How will we use system-level insights?

Will we only use individual, leader-level data, or will we aggregate the feedback to identify broader themes? Aggregated 360 data can reveal organizational patterns, like low cross-functional collaboration. Cohort-level data can identify common development themes, such as “visioning” or “strategic thinking,” to inform the design of learning. If you’re going to aggregate the 360 data, make sure there is organizational support to act on what it reveals.

Those are the seven topics I recommend exploring with executive stakeholders before moving on to tool selection and logistics. I’d love to hear what considerations you’d add to this list, or additional lessons you've learned in the “precontemplation” and “contemplation” stages of 360s.

Next week, I’ll share key considerations for selecting and deploying a 360 tool. Part 3 will then focus on debrief and development planning best practices. Until then, be well!