Product update
Comparing succession candidates side by side
A talent review that reads candidates one at a time is comparing them from memory. What changed in the latest release — and what to check before your next session.
By the CLEAR Talent team8 min read
Key takeaways
- A succession decision is comparative by definition. Read one candidate at a time and the comparison happens in someone’s memory.
- Decide what evidence the comparison shows before the session rather than during it — evidence settings make that an explicit, once-only choice.
- Portfolio weights now count only active KPIs, so a retired metric no longer holds a share of someone’s score.
- Resigned staff are excluded from departments, so coverage, completion and bench-strength numbers are calculated over the people actually there.
Succession conversations are almost always sequential. One candidate’s profile is opened, discussed and closed; then the next one. By the fourth name, the room is no longer comparing four people — it is comparing the fourth against a fading recollection of the first.
That is a tooling problem as much as a facilitation one, and it is what the latest CLEAR Talent release addresses. Candidates for a role can now be compared side by side against the same evidence, with settings that decide what that evidence is. Two smaller changes in the same release matter for the same reason: KPI portfolio weights now count only active KPIs, and people who have resigned no longer appear in department views. All three are live.
Why succession decisions get made from memory
A talent review has a structure that works against it. Profiles are long, the agenda is full, and the natural way to get through eight candidates is one at a time. But a succession decision is comparative by definition. The question is never “is this person good?” — it is “who, of these people, is closest to ready for this role, and what would close the distance for the others?”
Answered sequentially, that question gets answered from memory. The evidence behind the first candidate has scrolled past by the time the third is discussed, and what survives is an impression rather than a record. Impressions are shaped by who presented most confidently, who was discussed most recently, and who happened to have a strong quarter in the period everyone remembers.
The second failure is subtler: candidates arrive carrying different evidence. One nomination comes with competency ratings and multi-rater input behind it; another comes with a manager’s narrative and little else. The room then treats the thinner case as the weaker candidate, when what it actually reflects is uneven preparation.
Compare like with like
A comparison only means something if every candidate is described in the same terms. Four things are worth insisting on for each name on the list.
- Readiness against the target role
- Not general strength, but competency-based readiness mapped to the specific role being planned for. Someone can be an exceptional performer today and still sit two capabilities short of the job in question.
- Trajectory, not last cycle
- A single rating is a snapshot of a period that may have been unusually kind or unusually hard. The historical trend tells you the direction of travel, which is what a two-year readiness judgement actually rests on.
- Multi-rater input on leadership
- Most succession roles are people roles, and the people best placed to judge that are not only the candidate’s manager. 360° leadership scores bring peer and report perspectives into the same frame as everything else.
- Mobility and aspiration
- A declared willingness to relocate, to lead, or to step up. Someone unwilling to take the role is not a successor however ready the competency data makes them look — and that is a question worth asking before the plan is written rather than after.
The point is not that every organisation needs exactly these four. It is that whatever the four are, they should be the same four for everybody in the pool.
What is new: side-by-side candidate comparison
The release adds a succession candidate comparison — the people identified for the same role placed next to each other and described by the same evidence, in one view. It draws on data already in the system: the competency ratings, 360° feedback and performance scores the review cycle produces, rather than a separate succession dataset assembled for the occasion.
That last part is the difference worth naming. Most succession comparisons are built by hand, in a deck, in the week before the meeting. The deck describes a moment that has already passed by the time it is presented, and it is only as accurate as the person who assembled it. A comparison drawn from the live record is current, and it can be reopened when somebody challenges a conclusion three months later.
A follow-up change in the same release tightened the evidence the comparison carries for each candidate, so the view shows the material a readiness judgement was made from — not only the judgement itself. That matters most for the candidate whose case is being questioned, which is usually the candidate whose case is worth questioning.
A comparison assembled by hand describes the moment it was assembled. A comparison drawn from the record describes now.
Evidence settings: deciding what the room sees
The comparison ships with settings that govern which evidence it shows. That sounds like a preference and is really a policy.
Some of what a platform holds about a candidate is appropriate for a line manager and wrong for a nomination committee — verbatim multi-rater comments are the obvious example, and a declared aspiration to move out of the function is another. Whatever you decide, it has to be the same decision for everyone, because an evidence set that varies candidate by candidate reintroduces precisely the inconsistency the comparison exists to remove.
Settle it once, as configuration, and the same fields appear for every candidate in every session. Settle it in the meeting and you are negotiating the rules of the comparison while the comparison is under way.
It is also worth writing down why you chose what you chose. “We show readiness, trajectory and mobility; we do not show free-text feedback” is a defensible position. Being unable to explain why one candidate’s file looked fuller than another’s is not.
KPI portfolios, and weights that count only what is live
The same release refines KPI portfolios — the set of KPIs a person carries, held together in one place — and corrects how those portfolios are weighted.
Weighting is where KPI scoring quietly goes wrong. A portfolio is a set of measures with shares that are meant to add up to a whole, and mid-cycle those sets move: a target is withdrawn, a metric is replaced by a better one, the activity being measured stops existing. If the calculation keeps counting a KPI that is no longer active, everything else in the portfolio is being scored against a denominator that includes something nobody is working towards.
Portfolio weights now count only active KPIs. In practice that means a retired metric no longer holds a share of someone’s score, and the weights a person sees are the weights being applied to them.
It is a small fix with an outsized effect on trust. A scoring model people cannot reproduce by hand is a scoring model they will not defend to their teams — and weighting arithmetic that still includes something dormant is exactly the discrepancy a manager finds during a review conversation rather than before it.
Leavers should leave the department view
Every derived number in a performance system is calculated over a population. Goal completion by department, review coverage, rating distribution, how many successors a critical role has — all of it depends on who the system believes is in the department.
Resignations break that quietly. Someone gives notice, their record stays where it was, and from that point the department is being measured against a headcount that includes a person on their way out. Completion rates read low. Coverage reads worse than it is. And in a talent review, a pool can end up containing somebody who has already resigned, which is the kind of error that costs a meeting its credibility the moment anyone spots it.
The people register now excludes resigned staff from departments, so a department view shows the people who are currently in it.
What to check before your next talent review
None of this is heavy work, but it is better done in the ten minutes before the session than in the first ten minutes of it.
Agree the evidence set
Open the evidence settings and decide what the comparison shows for every candidate. Do it in advance: a field added halfway through a session applies to the names discussed after it and not to the ones already closed.
Check that a pool is a pool
A comparison of one candidate is not a comparison. Where a critical role has a single name against it, that is the finding — surface it as a gap rather than presenting it as a plan.
Review the KPI portfolios of anyone in the pool
Confirm which measures are still active and that the weights read the way you expect. Performance evidence carries more weight in a succession discussion than in a review, because it is being used to predict rather than to describe.
Confirm the department rosters
Check that departments show the people currently in them before drawing conclusions about coverage or bench strength from those numbers.
Name who owns the decision
The comparison narrows the question; it does not answer it. Say who holds the final call on each role before the discussion opens, exactly as you would before a calibration session.
A side-by-side view will not tell you who should get the job. What it removes is the part of that decision that was being made by memory, by advocacy, and by whichever candidate happened to be discussed last — which was the part nobody could have defended afterwards anyway.