Written to Fail. Posted Anyway.

Most CHRO searches fail before the first candidate is interviewed — not because organizations hire badly, but because the role definition was wrong before anyone walked in the room. The job description isn't neutral. It's a mandate signal. And when it reads like a senior HR generalist profile with "strategic partner" buried in paragraph three, that's exactly what gets hired.

Jackson Lynch and Scott Morris, founder of Propulsion AI and former CHRO, walk through the four faulty assumptions keeping organizations locked in the same loop — and introduce the Mandate Design Framework: three shifts that have to happen before a single bullet point gets written.

What You'll Learn

• Your JD is a mandate signal — and most signal the wrong mandate before the search ever starts
• The 4 faulty assumptions keeping CEOs in the CHRO hiring loop, including why "they'll earn their way to business altitude" is the most dangerous
• How to build a constraint map before writing a single job requirement
• The exact translation from HR deliverable to business outcome — with real examples from the episode
• Why mandate alignment is the hardest shift — and worth more than all the candidate interviews combined
• What sitting CHROs should ask their CEO right now — and how to push the answer past HR language
• How to use your CFO as an unintentional JD auditor before the post goes live

Key Quotes

• "The job description makes the decision before anybody was hired. That's where you need to start."
• "Personnel decisions are visible. The job architecture is invisible. The document that created the constraint was filed away and forgotten months ago."
• "The misalignment is architectural. It's not personal."
• "The search doesn't start when you engage the search firm. That's just when the billing starts."

Sources for Statistics Cited

• "Fewer than 20% of CHROs viewed as key contributors to business strategy" — Source not verified (attributed to AIHR executive survey)
• "CHRO turnover ~a third above its six-year average" — HR Executive / Russell Reynolds 
• "~20% of new CHROs serving under two years in role" — Fortune, May 2025 
• "~50% higher CHRO turnover vs. rest of C-suite" — Directionally supported; Fortune, March 2025 — Jackson remembered 9% versus 6% but it was versus 7%,

Keywords: CHRO job description, CHRO mandate design, CHRO search failure, CEO talent strategy, human capital architecture, CHRO turnover, mandate alignment, CHRO hiring mistakes, constraint mapping, CHRO altitude

Transcript

Scott Morris 0:00 I think you've got to ensure that there's explicit alignment about the mandate before the first candidate gets interviewed. So if you're a CEO and you're listening to this, you need to get your board and your executive team aligned on three things: what the person owns in terms of the business problems, what they influence without owning, and what success looks like in the language of the business — not the language that HR uses.

Jackson Lynch 0:30 Hey there, senior leader, and welcome to the Talent Sherpa Podcast. This is where senior leaders come to rethink how human capital really works. I'm your host, Jackson Lynch, and today I am joined by my friend, my co-host, Scott Morris. He is a CHRO with the scar tissue to prove it, the unconfirmed finalist in a jargon-free HR writing contest that he claims to have won with "decisive stakeholder alignment." And he's also the founder of Propulsion AI.

Now, hey Scott — we've been circling a topic for a while that I keep coming back to. Organizations hire the wrong CHRO. And not because the candidates are wrong, but because the role definition was wrong before anyone was ever interviewed. And the root of that problem is a job description that's built for the wrong job. I've looked at more CHRO job descriptions than I can count, especially recently, and most of them read like a senior HR generalist's profile with the phrase "strategic partner" dropped in somewhere — usually around paragraph three.

Scott Morris 1:30 I'm excited to have this conversation with you, Jackson. But hey, I'm going to do something different here. Before we dive into this subject, I want everybody to know that your CHRO Ascent Academy is kicking off in early May — the newest cohort. The first cohort that you put through gave you rave reviews. That's launched two new classes. One of them is for sitting CHROs, and one of them is similar material but for leaders that are one step away from the CHRO role. Both are likely to sell out quickly, everybody. So check the agenda, check the pricing, check the timeline. You can find it all at mytalentsherpa.com.

Jackson Lynch 2:10 Hey, thanks, Scott. And let's dive in. Every CHRO search eventually arrives at the same question: are we looking for the right person? And that feels exactly like the right question to ask. But here's what we're going to dig into today: the role definition has to come before the talent decision. Because if the role is defined incorrectly, then the wrong person gets hired almost every time — even when the individual they select is genuinely excellent.

Scott Morris 2:38 And you know what? Here's what I think makes this interesting: a lot of organizations approach the CHRO search through a competency frame. What kind of expertise does this person need? What kind of functions do they have to run? What transformation experience are they going to bring from their past? Those are all reasonable questions if you're staffing a senior HR team. But I think you and I both think they're the wrong questions if you're trying to put an enterprise operator into the role.

Jackson Lynch 3:10 That's 1,000% true. And I was talking to a CEO recently who had gone through two CHROs in three years. Different backgrounds, same result — neither person was operating at the business enterprise level. He asked me to take a look at it. When I did, the job description they used was basically the same in both searches. It felt like an HR VP document with a CHRO label and a little equity on top. It had 17 bullet points. 12 of those were about managing the function — or around business partnership without really defining what that is. And I think there was one about driving culture. Nothing in that document connected to the business outcomes that the CEO actually needed from the role.

Scott Morris 3:55 The Academy to Innovate HR's executive survey puts the number pretty plainly: fewer than 20% of CHROs are viewed by their CEO as key contributors to the business strategy. That's a real problem. And the number surprises people when they hear it, but it shouldn't. Because if the job description describes an HR function manager, that's exactly what you're going to attract, and it's exactly what you're going to hire. The mandate signal was wrong before the search ever started.

Jackson Lynch 4:25 Yeah, I think that's right. And think about what the document actually communicates. It tells every candidate reading it what the organization believes the job is for. It tells the person who gets hired what success looks like from their very first week. And if the signal says "manage the HR function and be a good partner to the business" — whatever that means — it's not a mandate for somebody who's supposed to be in the room when capital allocation decisions are being made.

Scott Morris 4:53 I like that our audience is growing in terms of the number of CEOs who are listening. And I use this comparison when I talk to CEOs about it: imagine writing a COO job description the way we write a CHRO job description. That COO job description would say things like "manage operations," "ensure process efficiency," and "be a strategic partner to the CEO." Few leaders would accept that framing for a chief operating officer role. We would say immediately that it misses the mandate entirely. The CHRO has the same problem, but we've been accepting it for decades.

Jackson Lynch 5:32 And the job descriptions that actually produce business-level CHROs read more like what you were describing — what real COO job descriptions look like. They anchor on business priorities in the next 24 months and they define the CHRO's accountability as clearing the human capital constraints between here and there. I tend to measure those in terms of revenue per head, leadership bench strength, execution reliability, speed of talent decision-making under pressure.

And think about it this way: when Patty McCord was building the people function at Netflix — and if you're listening and you don't know what they did, go look that up, because that is basically where we want all human capital to be headed — they never asked, "How do we run great HR?" What they did ask was, "What kind of people do we need to build the company that we're building?" That's a very different question. And every decision about the HR function flowed from that.

Scott Morris 6:28 So what we're really naming today is a mandate design problem. Before you ever pick up the phone to call a search firm — especially if you're using a search firm — you've already made a decision about what you think the job is all about. For most organizations, that decision gets made by pulling up the last job description, changing a few words, and posting it. And I don't just say that because of the kind of work we're trying to do at Propulsion AI — I think that's just about how everybody does it right now.

Jackson Lynch 6:59 It is. Which is why I think most people need to be reaching out to you for help, because you can help them get through that. But before we turn this into a Scott Morris commercial — and let's be honest, every time you're around, it's a Scott Morris commercial — let's call out some of the faulty assumptions that keep leaders locked in the patterns we just talked about.

The first one that I hear consistently is: "We know what we need. We need someone who can run HR at a high level and also, if they have extra time, operate at the business level." So, Scott — how many times have you heard that one sentence?

Scott Morris 7:35 You know the answer to that — more than I can count. And here's what the sentence is actually doing: it treats those two things as a single competency set, the same skill profile built up the same way over a career. But running an HR function at a high level and operating as a business operator are built through fundamentally different career trajectories. I realized that firsthand when I was not only Chief People Officer, but Chief of Staff to the CEO and had deep board involvement. I recognized the difference that was required as a result of that dual role. One of those is built through deep functional expertise. The other is built through direct accountability for business outcomes.

Jackson Lynch 8:20 Neither of us are saying that person can't exist — someone doing both — because they absolutely can, and they do. I think I might be an example of that. But when your framing going into the search is a job description that leads with HR expertise, you end up filtering for the wrong starting point from the very beginning. You look for depth in the functional lane and hope that the business acumen shows up as a byproduct.

And I'll give you a real-life example. I'm in a search process right now. I got a note from a search person earlier today who said, "Hey, would you please describe to me the relationship that you have with the General Counsel?" That just told me something about that job and how they see that job. Because for most of us, that's a very important partnership and you need to define the lenses through which you look at it — you need to look at the decision rights associated with it. But if that is what they're leading with from the candidate side, that tells you something really important.

Scott Morris 9:27 Yeah. And I think when you frame the job in those terms, you naturally — and regrettably — screen out some very genuinely capable candidates. People who have built real business operator instincts but have come through very unconventional paths. They look different on paper. The job description has already eliminated them before anybody reads their résumé.

Jackson Lynch 9:51 Now the second assumption is one that Scott and I have both been guilty of. I shouldn't speak for you — I've been guilty of it. And that's the idea that the job description's job is done when it attracts the candidates. Write it to get the résumés, get the candidates, post it, move on to the interviews, and we'll do the right stuff in the interviews.

Scott Morris 10:10 Yeah. So here's how I feel about that. People write job descriptions and then try to use the job description as the posting, rather than letting the document do what it's actually supposed to do — create clarity for the individual when you put them in the role — and letting the marketing copy, the posting, do the work of attracting the candidates.

I've seen job descriptions that were almost entirely optimized for attracting applicants. And a document designed for attracting applicants is a different artifact than a document designed to define a mandate. That's why I feel so strongly you've got to treat them as two different documents. The first one lists activities. The second one lists business constraints that the role is accountable for clearing. And those two documents produce a completely different interview conversation.

Jackson Lynch 10:57 And when a document is a marketing piece, you interview for capability in the abstract. When it's a mandate document, you're interviewing for fit against very specific business problems that need to be solved in a specific time horizon. The difference in signal quality you get from candidates is substantial.

Scott Morris 11:19 Many CEOs believe that a CHRO who comes in strong on the HR side will eventually translate that expertise into business impact — that they'll somehow learn the language, earn their way into the strategic conversation. Given enough context, given enough time, they'll get there. And I'm not sure that's true.

Jackson Lynch 11:42 Yeah, look, I understand that logic. The problem, however, is the data. CHRO turnover has been running about a third above its six-year average. Close to 20% of new CHROs are now serving under two years in role. We've shared some stats a little while back that showed we are running about 50% higher in CHRO turnover relative to the balance of the C-suite. You don't have to agree on any specific data point, but they're all pointing to the same thing. And if the development plan assumes they're going to earn their way into business altitude during their tenure, you've got to be very frank about the fact that that runway might not be there for them.

Scott Morris 12:22 Let's be clear about something else too: the CHRO who comes in with deep HR expertise but limited business context — they're not doing anything wrong. And we're not being critical of that. They're delivering exactly what the mandate asked them to deliver. The job description told them what the job was, and they are doing that job. The misalignment is architectural. It's not personal.

Jackson Lynch 12:47 Yeah, I think that reframe matters a lot, Scott. Because the reflex when a CHRO is not operating at the business level is to look at the person. The harder question is whether the mandate ever created accountability for operating that way. The job description — and I don't mean to keep harping on this — but the job description usually makes the decision before anybody was hired. So that's where you need to start.

Scott Morris 13:11 You're right to harp on it. But let me push us forward to the fourth assumption. And I think this one is probably the most damaging: the belief that a new CHRO can and should reshape the mandate after they arrive — that somehow a strong operator will come in and redefine the role through their own performance, and the organization is going to bend around their attitude. That's the belief.

Jackson Lynch 13:39 Yeah, in theory a strong operator can absolutely expand the mandate over time. And in fact, I'm working on something right now that I'm going to make available for purchase that will help a CHRO and a CEO come together on that. More details to come — if it's done by the time this posts, it'll be in the show notes.

But here's the practical reality: the CHRO who's walking in on day one is walking into a running system. There are already fires. There are already deliverables that were handed off during the transition. The HR function has expectations about what the new leader is going to do. And that kind of lock-in is very real and very powerful.

Scott Morris 14:22 Yeah. Reshaping a mandate from inside a running system is exponentially harder than designing the mandate before the search begins. A CHRO who spends the first 18 months working to redefine the role is spending 18 months not delivering the outcomes that the business needed from them — the ones written into that job description. That's a cost. And it shows up long before the performance review makes it visible.

Jackson Lynch 14:48 Yeah, which is exactly why this work belongs before the post goes live — not during onboarding, not after the hire. And not in the interview process. No, certainly not in the interview process.

But before we move on to what to do about it, I do want to make sure we name the mechanism that keeps this thing from self-correcting. We talked about this last week, and I think you said something that reframed it for me. The problem isn't the job description per se — it's where organizations start when they decide what a CHRO role is for. Can you talk us through that?

Scott Morris 15:30 Well, here's the loop as I see it. An organization needs a new CHRO. They do what everybody does: pull the last job description, update it to reflect current language. Maybe the CEO has some words that are really important to them. Maybe they add something about AI or transformation. Then they post it. And the document leads with HR domain expertise because it's never been changed — because the last version didn't change it either. The search yields primarily HR professionals. And then they hire the strongest of that candidate pool.

Jackson Lynch 16:06 Yeah. So taking this forward: the person comes in, delivers against the mandate they were given — which is running the HR function and being a partner. So that's what they do. And 12 to 18 months later, the CEO looks up and says, "This person is a great functional leader, but they are not operating at the altitude that I need."

Scott Morris 16:25 And the instinct is to run another search — not to change the document — and the loop starts all over again. Personnel decisions are visible. The CHRO is not working out — that's legible. The job architecture is invisible. The document that created the constraint is filed away and forgotten months ago.

Jackson Lynch 16:50 So in my advisory practice, I've spent years coaching CHROs on how to expand their influence and operate at a business altitude without ever pointing to the job description as the root cause. And it's one of those things where you go on in life and you realize — oh my God, I'm part of the problem. Because I was treating the symptom, because the symptom was right in front of me. I was treating it as a talent problem.

We did a pod a few weeks back where 94% of issues are process and system issues, and 6% is talent — and I was doing it the opposite way. The design failure was invisible to me too.

Scott Morris 17:30 Well, and CEOs are smart people, and it's invisible to them too. The system doesn't self-correct because the CEO who approved the job description and the CEO who is frustrated with the CHRO 18 months later have never connected those two events. They're separated by a search process, an onboarding, a full quarter of business performance, and a year of accumulated impressions. The document is long gone from working memory.

Jackson Lynch 17:58 And that gap is exactly where the architectural failure lives. If someone's leaving and they have an exit interview, it's going to surface that we need a different profile. And usually that pendulum swings in the opposite direction. But the design failure that produced that outcome never actually gets named.

Scott Morris 18:13 Okay. So you and I are practical guys. What breaks the loop?

Jackson Lynch 18:19 Well — I hate to give this to our bosses — but the CEO has to. Or someone with the access and the credibility to sit with the CEO before the search goes live. Maybe that's someone on the board. And they ask: before we post this, what's the problem this person is being hired to solve? Not what HR activities do we need covered — those are not the same thing. What business constraints need to be cleared in the next 24 months? What kind of person can actually clear them? Someone has to have that conversation. And it's probably at the CEO and board level.

Scott Morris 18:55 I like that. Let's shift and reframe this problem. How do we move from writing an HR job description to designing a business mandate? I want to give this a frame we can make more concrete. Let's call it the Mandate Design Framework. There are three specific shifts you make before the document ever gets written.

Jackson Lynch 19:23 Yeah, and I don't think any of these are technically complicated. They don't require a new process or a new tool — although I'm going to sell one. They require a CEO to start from a different place than most CHRO searches start from.

Scott Morris 19:36 And it's one of the reasons I'm really thankful that our audience of CEOs is growing, because this is a place where their leadership really makes a difference.

Here's Shift One: moving from competency profile to constraint map. The traditional approach asks what competencies a great CHRO needs. And you get a list: change management experience, executive presence, cross-functional partnership, HR domain depth. Those things are real, but they're inputs. The constraint map asks a different question: what are the two or three human capital constraints that are most directly threatening our business priorities over the next 24 months? It's a completely different question. Is it a leadership bench that is unable to carry you into the next phase of growth? Is there a talent density problem in the roles that are going to be most influential over operating margin? Is it execution reliability — and is that low because accountability and decision rights are unclear? That's where the conversation has to start.

Jackson Lynch 20:43 Yeah, and you've watched the constraint map conversation change the entire shape of a search or an incumbency review — because the constraint map produces a different job. If the primary constraint is bench strength, you need a CHRO who can build and run a talent development system that produces enterprise leaders. That is a specific capability. It's not the same person you might need if your constraint is building a scalable talent acquisition infrastructure to support rapid geographic expansion.

Scott Morris 21:13 And when you build the job description from the constraint map, candidates understand exactly what the problems are that they're being brought in to solve. Not "be a strategic partner" — which can have any number of different meanings — but the actual problems that are really impacting business performance, the consequences of not solving those problems, and what success looks like when those problems are solved. That changes, to a certain degree, who raises their hand for the job to begin with.

Jackson Lynch 21:42 Amen. So let's move on to Shift Two: from HR deliverables to business outcomes. In my experience, most CHRO job descriptions are written in HR language — usually by the search firm. I don't know if the CEO actually ever reads it. If so, it's just to make sure nothing stupid is in there that doesn't fit.

So you see things like: reduce attrition, improve engagement scores, modernize the HRIS, get the trains running on time, build out a learning and development capacity in the business. Those are all really good activities. They're probably necessary. But they're not sufficient as a mandate.

The reframe anchors the role to what the business produces. So think about it this way: "reduce voluntary attrition" becomes "improve revenue per head by addressing the tenure cliff in the first-year cohort." Or "modernize the HRIS" becomes "increase the speed of talent decision-making so that business leaders have real-time data to act in the moment versus waiting a quarter."

Scott Morris 22:43 You're right about that. And the difference in those two framings shows up in every conversation you're going to have with every candidate. One framing invites someone to come manage a function. The other invites someone to come solve a business problem. Maybe they solve it the way you're thinking about it, maybe they solve it a different way — but the focus is definitely different. And the talent pool that responds to those is not necessarily the same.

Jackson Lynch 23:09 Yeah. And I'll be a little sardonic on this — word of the day. We don't write the COO job description to say "improve operational satisfaction scores." We write it to say "reduce per-unit cost by this amount at this scale over this time horizon without compromising product quality or safety." That's a business outcome. The CHRO mandate should make the same translation, in the same language, with the same specificity.

Scott Morris 23:36 All right. Shift Three: moving from role definition to mandate alignment. I think this is the hardest shift because the document is the output — it's not the work. The real work is the conversation and the thinking that has to happen before anybody puts pen to paper and writes a word.

Most organizations draft the CHRO job description in a small group. The CEO probably doesn't write it — the CEO does review it, the board might look at it. But the mandate — what this person is going to own, what they're going to influence, what authority they're going to have, what success looks like at 12 months or at 24 months — that alignment rarely happens explicitly before the search starts.

Jackson Lynch 24:24 Yeah. And so you go through that whole process, the new CHRO arrives on day one, and they quickly discover that the CEO has one picture of the role, the board has a different picture, and the executive team has a third. You're chasing ghosts. The job description said "strategic partner" but didn't say to whom, or why, or where, with what actual authority. And every stakeholder has a rational claim on their time and attention — all of them grounded in something the document implied. So what do you do?

Scott Morris 24:53 Well, I think you've got to ensure that there's explicit alignment about the mandate before the first candidate gets interviewed. So if you're a CEO and you're listening to this, you need to get your board and your executive team aligned on three things: what the person owns in terms of the business problems, what they influence without owning, and what success looks like in the language of the business — not the language that HR uses.

Kathleen Hogan's mandate at Microsoft is worth referencing here. Her remit was explicitly tied to culture transformation as the mechanism for executing a specific business strategy — the cloud pivot. Her mandate treated culture as an operating lever. The business outcome already had a name.

Jackson Lynch 25:41 Yeah. And that conversation — the explicit mandate alignment before the search goes live — is often the most valuable output of the entire process. And here's why: it forces a leadership team to surface disagreements about what the role is for that have probably existed and rarely been named out loud. And that surfacing up front — that clarity — is worth more than most of the candidate evaluation work that follows.

Scott Morris 26:08 Yeah. So I think the question for leaders listening to this is: before the next search goes live, have you built the constraint map? Have you translated the job description into business outcomes? And have you explicitly aligned the mandate across every stakeholder who's going to work with the person you're hiring?

We've been talking about this in terms of CHROs, but the process really applies across the board. If the answer to any of those questions — about alignment, about business outcomes, about the constraint map — is no, then the design work is not done. And the search should not start yet.

Jackson Lynch 26:44 Yeah. To your point, we have CEOs who listen to the show. We also have a lot of search professionals. And you've got to have a clear answer to what business problem the person is being hired to solve before you start doing anything.

So the question is: what can we do this upcoming week? I'll take the first one. Count the bullet points that anchor to managing the function versus the bullet points that anchor to business outcomes. I don't know what the right number is, but just for fun — if more than half of the document is about managing the function, you have a mandate design problem and you need to pause. You're in the wrong place. You can't start there.

Scott Morris 27:28 Number two: the constraint map. Build the constraint map before you write a single word of any job description — not just the CHRO. What are the two or three human capital constraints that are most directly threatening your business objectives over the next 24 months? Write those at the top of the document. And every other requirement should trace back to one of those.

Jackson Lynch 28:01 Yeah. And then the third is to rewrite your success metrics in business language. Don't write things like "build a high-performing HR team." The good news is they're talking about team development as a management deliverable — which is great. But I don't know what "high-performing" always means. If leadership bench strength is the constraint, the metric should be the percentage of pivotal roles with a credible internal successor within 18 months. You've got to get much more specific. You've got to make it measurable in the same terms you'd define success for any of your other high-level operators.

Scott Morris 28:40 I'll put a fourth one in there: you've got to align on the mandate before you start briefing the search firm. Hopefully you're bringing them into that conversation rather than just handing it to them at the end — but it's got to be internally driven. Get the CEO, the board, the executive team aligned around what the person owns, what they influence, what success looks like at 12 and 24 months. Document it. And that document becomes your actual search brief.

Jackson Lynch 29:09 Now, we've spent most of this episode talking to CEOs and boards going through changes, and there are a bunch of CHROs saying, "Hey, what about me?" So let me give one for them. If you're currently sitting in a seat, you should have that mandate clarity conversation with your CEO now — not at the next performance review, not when it's too late. Ask directly: in terms of business performance, what does great look like for this role over the next 24 months? And get to a specific answer, measured in business outcomes. Because if you can't, that's actually really important information about where the mandate stands and your place relative to it.

Scott Morris 29:50 I'm going to throw a friendly amendment on that one, Jackson. Because a lot of us — and it's certainly been the case with me — I've asked that question before. I've tried to drive that conversation as a sitting CHRO, and I was surprised by what I got back. I got more language about HR problems, more language about HR programs. Don't let the conversation end there. Push it back into what we've been talking about — business outcomes.

Now, you went to a sitting CHRO — I'm going to go to a high-potential member of that CHRO's leadership team within the HR function. Give them an assignment: rewrite your current CHRO job description in business outcome language. What they produce is going to tell you something about their altitude — where they sit on the spectrum from functional expert to business operator. And you need to know that, because we shouldn't just be thinking about the rest of the business. We should also be thinking about our own teams and how we're going to build that altitude thinking into them.

Jackson Lynch 30:56 Yeah. Okay, one final one: before the job description is finalized, pick someone who is not the CEO or the HR people to look at it. Maybe the CFO. Not because finance is going to own it — I get that. But a CFO is going to flag every requirement that doesn't have a business translation. They're pre-wired to do that. And if a CFO reads a bullet point and says, "I don't know what that means, I don't know what that produces" — step back and say, "I'm not sure that belongs in the mandate."

And look, I realize asking your CFO to review your CHRO job scorecard is not standard practice. Standard practice has been producing CHROs who are not operating at the business level and who are then replaced at an unbelievably high clip. So let's do something different. Because at some point the cost of that pattern is worth examining honestly.

Okay, senior leaders. Here is your favorite part of the show — the Talent Sherpa's summary. And whereas Scott always says it in prose form, here it is in rhyme form this time: the mandate is everything, the mandate is life. And if you write it right the first time, you will not need to call me twice.

Scott Morris 32:06 No one has ever accused me of being Dr. Seuss. All right, here are three takeaways.

One: the CHRO job description is a mandate signal. It tells every candidate what you believe the job is for, and it tells every new hire what success looks like before they start. If you write it as an HR function management document, you're going to produce an HR function manager.

Number two: the search doesn't start when you engage the search firm — that's just when the billing starts. It starts when you design the mandate. Start with the business constraints, not the HR competency list.

Number three: translate the success metrics into business language, the same way the CFO does. Revenue per head, leadership bench depth, execution reliability. A metric that doesn't translate to a business outcome doesn't belong in the CHRO mandate.

And four: mandate requires explicit agreement from day one. The CEO, the board, the role holder — they all need to agree on what the person owns, what they're going to influence, and what winning looks like. The conversation is the real work. The job description is just the output of it.

Jackson Lynch 33:23 Yeah, I think that's right. And my takeaway from the episode is this: most CHRO mandate failures are designed in before anyone is ever interviewed. The signal is set before the search begins. The misalignment is baked in before day one. And the fix has to happen upstream. You've got to do the mandate design work before the search begins. And that work belongs to the CEO. Because when the mandate is built correctly before anything goes live, you have a completely different conversation with every single candidate. And you're going to be solving for the right problem from the beginning. And if you do that well, you can end up hiring someone who can actually solve it.

So thanks so much for tuning in to the Talent Sherpa Podcast today. This is where senior leaders come to rethink how human capital really works. And I say this every week, but I mean it sincerely — this is so much fun to do with all of you. We've now got people listening on five out of the seven continents, and we came really close to the Arctic Circle. And a quick shoutout to one of our favorite listeners — hello, Laura from Overland Park. Thanks for being a part of the Talent Sherpa community. And we want to thank everyone for listening, whether that's in Edinburgh, Scotland, or in Bellbrook, Ohio. It is great to have you with us.

Scott Morris 34:40 If you enjoyed today's episode, do us a favor and hit the like button right now. Or better yet, subscribe or leave us a review. You can do it on your favorite platform — Apple Podcasts, Spotify, YouTube. We're on all of it. It benefits the community. Take a moment, leave us a quick review. It's free and it's really helpful to us. And you can also share an episode with your CEO — pull them into the conversation and let us help you build that mandate.

Jackson Lynch 35:10 Amen. And look, if you're a CEO or a CHRO or someone on the senior team trying to figure out where to start your AI journey, don't forget to check out Propulsion AI — that's where Scott has built a wonderful organization. You can find them at www.getpropulsion.ai. Scott, tell us a little bit about what you're building there.

Scott Morris 35:30 Well, one of the things we're building: we have a teammate named Athena. She's one of our digital teammates, and she coaches managers on building the kind of outcome clarity into what we call role blueprints that we've been talking about in today's episode. So check us out.

Hey, and don't forget — if you're an early-stage CHRO, if you're new to the role, Jackson has helped an awful lot of people in your same position through personal coaching, through the CHRO Ascent Academy, and through his best-selling Substack. You can find access to all three at www.mytalentsherpa.com.

Jackson Lynch 36:06 And thanks, Scott. And thanks to everyone who's listening. Until next time — keep raising the bar, keep designing the mandate before you post the job, and keep on climbing.