Lesson 18 of 20
Overview
Claire Monroe: Welcome back to The Science of Leading. I’m Claire Monroe, here with Edwin Carrington. Today we’re talking directly to the people who live and breathe performance cycles… HR, People Ops, talent folks. Why do leadership reviews so often feel unfair, inconsistent, or just… exhausting?
Edwin Carrington: Because most of them are built on narrative rather than structure. You give managers a blank box that says “Write feedback,” and you get novels, or you get three sentences, depending on the manager’s style. Same leader, very different story. That’s where fairness starts to break down.
Claire Monroe: Yeah, I’ve seen that. One leader gets a glowing page because their manager loves to write. Another gets two vague lines: “Good year. Keep it up.” And comp decisions are made off that.
Edwin Carrington: Exactly. Unstructured reviews turn into personality contests. Who tells the better story, who has the more persuasive manager. A structured leadership evaluation forces everyone to answer the same questions: What was this leader’s scope? What did they deliver? How did they lead?
Claire Monroe: Let’s sit on that “what” versus “how.” Why is it so important to review both outcomes and behaviors?
Edwin Carrington: Because results alone don’t tell you if the leadership is sustainable. You can hit every target and quietly burn out your team, drive away top performers, or create a culture of fear. On paper, the numbers look great. Underneath, you’re building a future turnover problem.
Edwin Carrington: On the flip side, you might have someone who’s beloved and supportive, but they’re not delivering the outcomes the business needs. Strong “how,” weak “what.” A good review has to hold both truths at once.
Claire Monroe: So HR’s trying to protect against… what? I’m thinking bias, vague language, that “what happened last month” effect.
Edwin Carrington: You’ve named the big ones. Vague language: “great leader,” “rough year,” “not strategic.” None of those can be acted on. Bias: how likable someone is, how similar they are to the reviewer. And recency bias, where the last project overshadows eleven good months before it.
Edwin Carrington: Then there’s inconsistent standards. One department calls someone “top talent” for the same performance another department labels “average.” HR can’t build a fair promotion or succession system on that.
Claire Monroe: So the fix isn’t “tell managers to be objective.” It’s give them a better template?
Edwin Carrington: Right. You design the process so it demands evidence. A structured leadership template asks: What was this person actually responsible for? What results did the team produce? Which leadership behaviors did you see? Give examples. That’s how you clean up the inputs so your compensation and promotion decisions are defensible.
Claire Monroe: And you can even layer in structured data on top of that. Things like behavior fit reports or science-based assessments from tools like OAD, so you’re not relying only on the manager’s memory and mood.
Edwin Carrington: Yes. When you have consistent, validated data alongside a good template, the review stops being, “How do I feel about Claire this year?” and becomes, “Here’s what Claire did, how she did it, and how that lines up with the role and the evidence we have.”
Claire Monroe: Okay, so if I’m in HR and I buy into that, my next question is, “What does that structured template actually look like?” Let’s unpack that next.
Claire Monroe: Alright, Edwin, let’s walk through a plug-and-play leadership review template. If HR wants managers to stop writing messy essays, what are the core sections they should standardize?
Edwin Carrington: I’d build it in five big blocks. First: role context. Second: outcomes and impact. Third: competencies. Fourth: values and culture. Fifth: the development plan and summary.
Claire Monroe: Let’s start with role context. What should be captured there?
Edwin Carrington: Role title, team or function, number of direct reports, major stakeholders, any budget or geographic scope, and the top priorities for the year. Plus one important piece: what changed. Did they take on a new team, new region, new product line? Without that, people get judged on last year’s job, not this year’s reality.
Claire Monroe: So you anchor expectations before you judge performance.
Edwin Carrington: Exactly. Then you move to outcomes and impact. That’s the “what.” Three to five concrete results: key projects delivered, metrics moved, major milestones. And you connect it to team performance: quality, speed, customer impact, maybe signals like retention if relevant.
Claire Monroe: Can you give an example of a weak comment there versus a stronger one?
Edwin Carrington: Weak would be, “Did a good job leading the product launch.” Stronger: “Led the Q3 product launch on schedule, which improved time-to-market by two weeks and reduced post-launch defects by 15 percent.” Same event, but the second one tells you what actually happened.
Claire Monroe: And then competencies is the “how” section?
Edwin Carrington: Yes. You pick the core leadership skills you care about: communication, decision making, emotional intelligence, delegation and time management, strategic thinking. For each, you ask: what did they do well, what needs to improve, and what’s one example.
Claire Monroe: This is where HR struggles, right? Turning “soft skills” into something observable.
Edwin Carrington: Right, so you translate them into behaviors. Take communication. Weak comment: “Strong communicator.” Better: “Explains complex roadmap changes in plain language during team meetings, which reduced rework on the Q2 release.”
Edwin Carrington: For a gap, instead of “needs better communication,” you write, “When priorities changed in April, updates were high-level and didn’t clarify owners or deadlines, which caused missed handoffs with Support.”
Claire Monroe: You’re always pairing behavior, impact, and context.
Edwin Carrington: Exactly. You can do the same with decision making: “Makes timely decisions in ambiguous situations and explains trade-offs,” or, for a gap, “Delays decisions when information is incomplete, which slowed the pricing rollout in June.”
Claire Monroe: Where do options like technical skills or change leadership fit in?
Edwin Carrington: Those become optional competency add-ons based on scope. If it’s a hands-on engineering manager, you add “technical depth” or “system design.” If they’re running a transformation, you add “change leadership.” Same structure: what they did well, what to improve, with examples.
Claire Monroe: And values and culture?
Edwin Carrington: That’s your protection against “results at any cost.” You ask: How does this leader contribute to a healthy environment? Do people feel safe raising issues? Where does their style create friction? Again, examples. “Creates space in team meetings for quieter members to weigh in,” or, “Avoids direct conflict, so issues resurface between Marketing and Sales.”
Claire Monroe: Then you end with a development plan and an overall summary.
Edwin Carrington: Yes. One to three development goals, why they matter, what “good” looks like, concrete actions, and a milestone date. For example: “Improve delegation so more decisions are made at team lead level. Good looks like weekly priorities set with clear owners; by 90 days, at least five recurring decisions are handled without escalation.”
Edwin Carrington: If you’ve got structured behavioral data from something like OAD, this is where you align it: “Given your tendency to hold decisions close under stress, we’ll practice pushing ownership down with clear guardrails.” It makes the plan much more tailored.
Claire Monroe: And the beauty for HR is: same sections, same prompts, across every manager. Different content, but a common spine.
Claire Monroe: Okay, so say HR has this template ready. The anxiety I hear is, “How do we roll this out without overwhelming everyone?” Can we walk through a simple annual checklist?
Edwin Carrington: Absolutely. Step one is data prep. HR pulls goals, key metrics, any engagement or retention data, and relevant stakeholder feedback. If you’re using a structured assessment like OAD, you have those reports handy too, so leaders aren’t guessing about strengths and blind spots.
Claire Monroe: Then you ask leaders for self-reviews, right?
Edwin Carrington: Yes. You give them the same structure: wins, where they fell short and why, what they learned, and what support they need. That way, the manager isn’t breaking news in the meeting; they’re building on the leader’s own reflection.
Claire Monroe: What about the meeting itself? How do you keep it focused?
Edwin Carrington: Simple agenda. First, confirm the scope for the period. Second, walk through outcomes and impact. Third, discuss two or three key competencies with examples. Fourth, agree on the development plan and milestones. Fifth, summarize decisions: any comp, scope, and the follow-up dates.
Claire Monroe: Then HR’s job is to make sure it doesn’t die in the system afterward.
Edwin Carrington: Exactly. Within a couple of days, the manager documents the review, finalizes the development goals, and schedules follow-ups. That’s where your 30/60/90-day structure comes in.
Claire Monroe: Can you give a concrete 30/60/90 example?
Edwin Carrington: Sure. Let’s say the focus is decision speed. At 30 days, you check: have we defined which decisions can be made at the team level and started setting decision deadlines? At 60 days, you look for evidence: “Three roadmap decisions were made on time with documented trade-offs.” At 90 days, you decide: has behavior changed enough to close the gap, or do we adjust the plan?
Claire Monroe: You also mentioned calibration and bias mitigation. How does HR make standards consistent across departments?
Edwin Carrington: You run calibration sessions. Managers come in with draft reviews and, crucially, two or three examples per major rating. HR moderates: “If you’re calling this ‘outstanding communication,’ what are the observable behaviors? How does that compare to others?” You challenge vague labels like “not leadership material” until they’re translated into concrete behaviors.
Claire Monroe: So the rule is: no ratings without receipts.
Edwin Carrington: Exactly. And bias mitigation is baked into the structure: common competencies, shared language, examples required. Where you have something like OAD, you’re also counterbalancing gut feel with consistent, science-based data on traits that affect leadership style. That helps when executives push back with, “But I just don’t see them as a leader.”
Claire Monroe: I can hear HR leaders asking, “How do I keep executives on board and not drown them in process?”
Edwin Carrington: You frame it in business terms. This isn’t extra paperwork; it’s risk management. Structured leadership reviews reduce promotion mistakes, make pay decisions defensible, and give you a clear bench for succession planning. You’re protecting the company and the leaders.
Claire Monroe: And you’re turning reviews into real development, not just a yearly post-mortem.
Edwin Carrington: Exactly. When you tie the review to 30/60/90-day milestones, you can track progress, spot who’s growing into larger roles, and who might struggle with more scope. Over time, that shapes your succession plan: who’s ready now, who’s ready next, and what each person needs.
Claire Monroe: Alright, let’s land this. If you’re listening and you’re in HR or People Ops, the move is: standardize the template, insist on behavior-plus-impact comments, run real calibration, and turn every review into a concrete development plan.
Edwin Carrington: And don’t rely only on narrative. If you want leadership reviews and development plans that are consistent, evidence-based, and defensible, add structured behavioral data into the mix.
Claire Monroe: That’s where a tool like OAD comes in. If you wanna see what that looks like in practice, go test OAD for free at OAD.ai. It gives you science-based insights into leadership traits and fit, so your templates, your calibration, and your development plans have a stronger foundation than gut feel.
Edwin Carrington: It’s a simple step that can dramatically improve the quality of your decisions about leaders.
Claire Monroe: Edwin, thanks as always for the perspective.
Edwin Carrington: Always a pleasure, Claire.
Claire Monroe: And thanks to all of you for listening to The Science of Leading. Go tighten up those leadership reviews, and we’ll see you next time.