How to Plan a Leadership 360 Program Around Your Talent Reviews

A common timing mistake with a program is launching when the rollout is ready rather than when the results are needed. If the reports are meant to inform a talent review, a promotion round or the start of a development program, that date is your anchor, and everything else gets scheduled backward from it.

For a cohort run in three waves, a workable plan starts about eleven weeks out. The plan below has no slack in it, so if rater approvals tend to run slow in your organization, start a week earlier.

Each wave runs the standard 14-day cycle, with reports the day after it closes. Spacing the waves a week apart keeps every debrief inside a four-week window.

The point of a pilot is to test your process, because the sample reports already show you the output. Run one full cycle with a small group and watch where it snags, including whether raters understand the invitation, how long approving rater lists actually takes, whether managers know what to do with the reports, and which questions land in HR's inbox. Give the pilot the same rater note and manager briefing the cohort will get, so it tests the process the cohort will actually go through.

Pick 10 to 15 leaders from different parts of the business, and include a manager or two who is skeptical of 360s, because their questions are the ones the rest of the cohort will ask. If your whole group is close to that size, the pilot is your first wave. Hold the pilot debriefs before you finalize the waves, since the debriefs show you how much preparation managers need.

Launching every leader on the same day sounds efficient, but it puts all the work into the same two weeks. Every rater list needs approval at once, and anyone nominated by several leaders gets several invitations in the same few days. A cohort small enough for one person to approve in a day or two can run as a single wave, and the rest of this page still applies. For a larger group, waves spread the load, and a few rules make them work.

• Size each wave by your approval capacity. Every rater list deserves a real review, not a rubber stamp (How to Choose the Right Raters covers what to look for). If one person approves the lists, a wave should hold no more than they can review properly in a day or two.
• Watch for shared raters. Peers in the same function often turn up on several lists. When the same names keep appearing, spread those leaders across different waves so no one is asked about four colleagues in one week.
• Keep each wave on the same schedule. Give every leader in a wave the same start, the same end date and one reminder at day 7, with no extensions. A wave that runs long lands its reports on top of the next wave's, and the last wave has no room to run long at all.
• Put the leaders who matter most to the decision in the early waves, so their reports get the most time for debrief and review.

An invitation from a platform nobody has heard of is easy to ignore. A short note from a senior leader before the first wave launches gives raters a reason to open it, and it only needs to cover four things:

1. 1.Why the organization is doing this, and what the results will be used for.
2. 2.What raters will be asked to do. Peers and direct reports have a conversation of about five minutes for each leader who nominated them, with no login.
3. 3.How their input is handled. Peer and direct report input is synthesized into themes, and no comment is attributed to an individual. Managers are the exception, since each leader has only one, so tell managers separately that their input will be recognizable as theirs and that their conversation runs about ten minutes.
4. 4.When invitations will arrive, and that some people will get more than one.

In a cohort rollout the manager carries most of the follow-through, and many managers have never debriefed a 360. Brief them as a group before the first wave launches. An hour should cover what the two reports contain, who receives which (the Assessment Report goes to HR and the manager, the Development Report to the leader), and how to run a debrief that starts with what the leader does well and ends with one specific thing to work on.

Ask managers to hold each debrief within a week of the report arriving, and to fold it into a one-on-one they already have instead of scheduling something new, because a debrief attached to an existing meeting is harder to postpone.

Once the last wave closes, you have a consistent read on a whole group of leaders taken over the same few weeks, which a single 360 can't give you. Use the final week before the review to look across the Assessment Reports for three things.

• Where leaders sit on the What and the How. Performers, Drivers, Facilitators and At Risk leaders each call for a different conversation in the review, and Using the What and the How in Promotion Decisions walks through each one.
• Themes that recur. When the same theme shows up across many reports, it's a candidate for group learning rather than one coaching plan after another.
• Gaps between expectation and evidence. A leader everyone assumed was ready who lands as a Driver deserves a closer look before the review, so it isn't a surprise during it.

The data informs the review, and the decisions stay with the people in the room. What changes is that every leader is discussed from the same kind of evidence, gathered the same way over the same few weeks.

If your reviews come once a year, the cycle that feeds that review is the whole plan. A second full cycle, or a targeted cycle between reviews, is something to add once the first has run. A rollout that happens once tells you where your leaders stood in one season, and running it again is what shows you who has moved.

If you do add cycles, two kinds work together.

• Full cycles cover the whole leadership population. They feed the decisions that compare leaders with each other, like talent reviews and succession planning, and twice a year is a workable rhythm for them.
• Targeted cycles cover the leaders with something specific to track, such as people new in role (once their team has worked with them long enough to say something useful), leaders working on a development plan, promotion candidates, and anyone whose last result raised a question. They run between full cycles. Tell the organization about the rhythm up front, so a targeted cycle reads as routine rather than as a sign that someone is in trouble.

For an organization with talent reviews in July and December, a year with both kinds could look like this.

HR reads those cycles together by putting each leader's reports side by side, and a single low cycle is context to weigh rather than a verdict (Using the What and the How in Promotion Decisions covers why one cycle should never be treated as definitive). Whatever rhythm you choose, put the next cycle's date on the calendar before the current one wraps up, while the effort is still fresh.