HR designs the succession process, but managers make the actual calls. When a talent review asks whether someone is ready for a bigger role, the answer comes from the person who has watched them work all year, not from HR. That's an important job, and most managers walk into the meeting with nothing more than an impression and a slide with a name on it.
Evidence, not opinions
The single habit that separates a useful talent review from a wasted one: come with evidence, not adjectives. "Strong," "impressive," and "ready with support" are opinions, and opinions don't survive a follow-up question. "Ran the Q3 forecast independently after two quarters of shadowing" is evidence, and evidence answers the follow-up before anyone has to ask it.
If your honest prep for a direct report's assessment is a general sense of how they're doing, that's the sign to slow down before the meeting, not during it.
Gather it before the meeting, not during
Evidence gathered on the spot is memory dressed up as data. Before a talent review, go through each direct report you'll be discussing and write down two or three specific, dated examples per rating: a project they owned, a decision they made under pressure, a gap that showed up somewhere real. This takes less time than it sounds like, mostly because you already know the examples, you just haven't written them down yet.
The people who struggle most in these meetings aren't the ones with weak direct reports. They're the ones who show up having only thought about their team in general terms, and then have to invent specifics under pressure while three other leaders watch.
Separate performance from potential per person
These are different questions, and conflating them is the most common mistake in the room. Performance is: is this person doing the current job well? Potential is: could this person do a meaningfully bigger job, and what's the actual evidence for that, not just the fact that they're good at the one they have now.
A strong performer with no interest in ambiguity or people management isn't automatically high-potential, and rating them that way sets up a promotion that makes them miserable and leaves their old role suddenly vacant. Answer both questions honestly and separately for every person you're discussing.
Know how to defend a placement when it's challenged
Someone will ask why you rated a person the way you did, sometimes in the meeting and sometimes months later when that person gets passed over for a role. Every score change in SuccessionStack requires a reason before it saves, which exists for exactly this moment: if you can't state the reason in one sentence backed by something specific, the rating probably isn't ready to make yet.
A placement that has an answer is a placement everyone can trust, including the person it's about. A placement without one is the reason talent reviews get a reputation as political theater instead of a real process.
Why a scored record protects you, not just the process
The audit trail isn't there to check up on managers. It's there to protect them. A rating you can explain, with a reason logged at the time you made it, is a rating that still holds up a year later when you've moved teams, changed your mind about someone, or genuinely forgotten the specifics. Without that record, every past call becomes something you have to defend from memory, and memory is a worse witness than you'd like to think.
Bring evidence, separate the two questions, and write down the reason while it's still fresh. That's most of what a good talent review actually requires from the person running it.
FAQ
What should a manager bring to a talent review?
Dated, specific evidence for each direct report being discussed, not general impressions. Two or three concrete examples per person, covering both current performance and any signal about potential for a bigger role, is enough to hold up under questioning.
How much prep does a talent review actually take?
For a small team, usually less than an hour: 10 to 15 minutes per person to write down the specific examples you already know but haven't recorded. Most of the time isn't spent finding evidence, it's spent turning a vague impression into a specific one.
What happens if a manager's placement gets challenged?
A challenged placement needs a one-sentence answer backed by a real example: what the person did, when, and why it supports the rating. If that sentence doesn't exist, the honest response is to revisit the rating rather than defend it on reputation alone.