Wrong HR Costs More Than No HR

Most growth-stage companies don't have an HR problem. They have a talent architecture problem — and they're trying to solve it with a people operations brief. The HR function runs clean. Handbooks get built. Engagement scores tick up. And the business quietly loses execution speed for months before anyone names what's actually broken.

Ben Horowitz argued in 2014 that growth-stage companies need HR earlier than most founders think. He was right. But the harder question isn't whether to bring HR in — it's what you ask HR to build. Most companies answer that by accident. This episode breaks down why the brief matters and gives you four concrete plays to fix it before the function gets built around the wrong mandate.

What You'll Learn

• The difference between a people operations mandate and a talent architecture mandate — and why conflating them is the root of most HR failures.
• Why the chaos of no HR is visible and acute, but the cost of wrong HR is invisible and chronic.
• How the HR brief gets written by the loudest problem in the room instead of the business strategy — and how that shapes everything the function becomes.
• Why talent density and role clarity matter more at 30 people than at 3,000 — and what happens when the talent architecture question is answered by default.
• Four plays to establish mandate clarity before HR starts building: name your pivotal roles, write the mandate first, separate the disciplines, and have the conversation now.

Key Quotes

"The chaos of no HR is visible and acute. The cost of wrong HR is invisible and chronic."

"The decision to bring in HR is not the hard decision. The hard decision is what you ask HR to build."

"The mandate determines the model. What HR is asked to produce determines what it builds."

Sources for Statistics Cited

No statistics cited in this episode.

SEO Summary

Meta Description:

Most HR failures trace back to the wrong mandate. Jackson Lynch breaks down why growth-stage companies need talent architecture, not just people ops.

Keywords:

CHRO strategy, talent architecture, HR mandate, growth-stage HR, people operations, talent density, HR alignment, CEO CHRO alignment, human capital strategy, talent function design

Transcript

I think you already know this, but most growth-stage companies don't have an HR problem. They have a talent architecture problem that they're trying to solve — sometimes with their very first HR hire. And by the time they figure out the difference, they're already cleaning up what that confusion has built.

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 we're going to be talking about something that Ben Horowitz from Andreessen Horowitz got, I think, half right when he wrote it back in 2014 — and that the field has been quietly getting wrong ever since.

Now, the argument was simple, if you're familiar with it. Growth-stage companies need HR, and they need it earlier than most founders think. And the resistance to bringing HR in — which usually centered around compliance and culture — is misplaced. So, as you would imagine, I agree with all of that. But here's what I think the framing left out. The question that actually determines what the talent function becomes is simple: what are we building this thing to do?

Most companies answer that question before anyone ever shows up. And they probably answer it by accident. And if you've ever been that person who walked into a talent mess — that company that looked great on the outside, fine, everything's fine — then you know exactly what I'm describing. The HR function was running, the people operations were clean, and the business was quietly losing execution speed because no one had ever defined what roles actually drove incremental performance, who owned what decisions, and where the talent density needed to be concentrated.

And for those people who have lived through that, it's what we're going to be talking about today. And by the end, you'll probably have a sharper lens through which you can figure out what to actually ask HR to build, whether you're running a 10-person team or a 10,000-person organization. I think the lessons will still apply.

Now, before we get into today's program, I want to say thank you. A shout out is going this week to Katie from Greece. I want to say thank you for being a part of this Talent Sherpa community. And for everyone who is tuning in, whether you're in Bangladesh or in Cupertino, California, I really wanted you to know that I appreciate you being here. This community keeps growing, and that is because of you.

And I also want to talk about something before we dive in — something I just got done building. I call it the Mandate Protocol, and I built it because every HR leader in my coaching practice keeps asking for the same thing. Give me a structured way to sit down with my CEO or their business leader and get aligned on what the HR function is actually supposed to do. Not the feel-good version, not the one that's on the walls, not the stuff that was in the job profile that the search firm put together — the real one. Connectivity, decision rights, measurement, how HR interfaces with the business, where we actually own something, and how to know whether it's working.

And I built this initially for first-time CHROs, but it applies to any HR leader who's building — or at least trying to build — a real mandate rather than inheriting a vague one. It's $297 for now. And if you go through the whole thing and decide within 14 days that it's not adding sufficient value, just let me know. I'll refund everything. No questions asked. The risk is on me. You can find everything at mytalentsherpa.com/mandate-protocol.

Okay, let's get into it. Here is a scene that plays out much more often than it should. A company is somewhere between 20 and 200 people. It's growing really, really fast. And the founding team has been holding things together, making talent decisions on instinct. They're running people operations out of whoever has bandwidth that week.

And at some point, something tips. Maybe it's a bad hire that sits too long. Maybe it's two strong people in roles that were never clearly separated — stepping on each other's decisions every single week. Maybe it's that CEO who starts getting feedback that things are fracturing, and the answer that surfaces is: we need someone to help us think through how all this works.

So HR comes in, and nine times out of ten, they arrive with a brief that was written by the problem itself. The brief is: help us with compliance, help us with process, get the job descriptions clean, build out onboarding, establish some process around performance. Help us hold the culture together as we scale. That's a people operations brief. It's not a talent architecture brief.

And the company builds exactly what they asked for: a clean, well-run people operations function. Handbooks, survey cycles, and an engagement score that ticks upward to the right year over year. And what gets left behind is the talent system itself. A clear view on what roles drive performance outcomes, a model for where talent density needs to be concentrated, a framework for who owns what decisions and what breaks down at the handoff points.

So Ben Horowitz made the case in 2014 that growth-stage companies need HR because things fracture around culture, around people decisions, around the rise of process and compliance. And he was not wrong at all about the fracture. The symptoms he described — they're real and they show up consistently.

But the larger fracture — the one that I've spent a significant part of my career cleaning up — is not about those things. It's structural. It's about alignment, it's about decision rights, it's about pivotal roles and whether exceptional talent is sitting in them today. And if not, what do we do about it?

And the difference is: those things don't break loudly. They break quietly, softly. They whisper over time. And by the time you feel it, the organization has been losing execution speed for months, sometimes longer. And the people operations function was running the entire time. Everyone got paid, no compliance issues, engagement scores probably fine. And underneath all that, the structural problem was compounding without anyone noticing or naming it. And that's the pattern. And it starts earlier than most leaders realize.

So the first trap is, I think, the compliance approach. When a growing company finally decides to bring in HR, the impulse that drives the decision is almost always reactive. Something probably went wrong. Someone filed a complaint. The performance process is inconsistent, the culture is feeling less cohesive than it used to. And the natural response is to build a function that addresses those things. And I get it. It does address them. It usually works. That's not the problem.

The problem is that a people operations approach gets handed to HR before anyone is asked what the talent function needs to produce for the business. The HR leader in that scenario executes well against the brief they were given. It's a functional one. I think it's probably the wrong one. Or at least it's incomplete.

And here's where it normally breaks down. Most leaders don't recognize that early-stage HR was the wrong kind of HR until things start to visibly fracture. By then, the organizational behaviors are already embedded. The decision-making patterns are already in place. Roles are defined in terms of activities rather than outcomes — I guarantee that's there. And the talent density question has probably never been explicitly asked, which means it was answered by default and usually answered wrong, based on however the founder was feeling that day — and maybe even loyalty.

I've worked in organizations that had genuinely strong HR teams with real executional gaps the function could not touch because it was never given the mandate to touch them. The function was solving the right problems for the brief being held. And in the next couple of podcasts, we're going to talk about what to do in those cases. But if you have the brief that you have, it's just unlikely to include the things that matter most.

And here's where I think that makes it particularly sharp at small companies. When you're 30 or 40 people, every single seat is a pivotal seat. There is no redundancy, there's no depth, there's no bench to absorb a weak fit in a critical role. Someone in the wrong seat at that size doesn't cost you a percentage point of output. It costs you everything that function was supposed to produce. And in a small company, that function is not a department — it's usually one person.

The talent portfolio question — which roles drive the most value, where the talent density needs to be concentrated, where a single weak link creates outsized structural risk to be addressed — that question is not more important at scale, although it's really important there. I think it's most important when you are small and every decision compounds directly into results. So here's the shift.

The second one is about mandate itself. And mandate is where almost every HR failure I've ever seen traces back to. It's usually not capability or commitment or even leadership. It's the absence of a clear and explicit answer to the question: what does this talent function exist to do?

When HR is built to manage people ops, it optimizes people ops. When it's built to produce execution speed through better talent decisions and role clarity, it optimizes for that. When the system is built, it responds to the mandate it was handed. And growth-stage companies have never written the brief around the mandate. They write the first one, usually implicitly: I'm bringing in HR to address an immediate pain. And the function gets shaped by that pain. And the pain's real. But the business need never really gets asked outside of that pain.

So Horowitz was solving for the chaos of having no people infrastructure at all. That's a real problem. But I think we've all learned something in the years after that conversation. The chaos of no HR is visible and acute. The cost of wrong HR is invisible and chronic. And chronic costs are the ones that erode the business before anyone formally identifies and names them.

Wrong HR here means HR handed a people operations mandate when the company needed a talent architecture mandate. That HR leader is likely doing exactly what they were asked to go do. The mandate's the problem.

And this matters most at small companies and small scale because the organization can't absorb the cost of misaligned talent the way even a mid-sized organization can — certainly not the way a large organization can. A large company with blurry roles and uneven talent density is going to keep moving. It's slower and noisier than it should be, but it's going to keep moving. A small company with those exact same problems is going to be moving at a fraction of what it should. At 30 people, two or three misdeployed senior contributors can determine whether the year goes well or goes sideways.

And the mandate determines the model. What HR is asked to produce determines what it builds, what it measures, and how it positions itself inside the organization. And most of the time that question gets answered in the first three months — implicitly, under pressure, usually by whoever is loudest about what they need.

Okay, so if you're one of the ones that's in this situation — specifically if you're the one thinking about bringing in HR — here are the four plays I'd like you to think about.

Number one, before you hire HR — or right now, if you already have — answer this question directly and explicitly: what are the five roles in this organization that most directly determine whether we hit our outcomes this year? Five specific seats. These are the people who own the decisions that compound into results. If you can't name them quickly, it's not because they don't exist. It's because the talent architecture question has never been made explicit. So start there. This single exercise, I think, changes what you can ask HR to do and where you concentrate your energy when you think about the team.

Play number two: write the mandate before you build the function. That sounds basic. I get it. It almost never happens. So it must be harder than it appears. Most companies hire an HR leader and then let the mandate emerge from whatever problems are loudest when they get there. And that's a very reliable way to end up with a people operations function when you need a talent system.

The reality is most HR people are going to build what they know, which is why you have such a challenge when people are moving from high-infrastructure roles into low-infrastructure roles. That's where the missteps really start to happen. And it's why the mandate conversation is so important. It's also pretty straightforward: what are the two or three outcomes the talent function is expected to produce for the business in the next 12 to 24 months? Just write those down. Frame them in terms of what the business gets because HR exists. I'd look at execution speed, leadership pipeline health, talent density, and pivotal critical roles — whatever they are for you — write them down, make them explicit, and do it before anyone starts building anything.

Play number three: separate the talent architecture work from the people operations work. And be honest about which one you're actually funding. People ops is a real discipline — it's important. Compliance, onboarding, performance process, employee relations — all that work matters and it requires skill. Diagnosing which roles are creating execution gaps, where the talent density problem lives, and how to structure decision rights to reduce organizational drag — that's a completely different discipline. Separate, with a separate skill profile. Most growing companies collapse both into the first bucket because it's all they're going to be able to fund. Be explicit about that. It's okay. But be explicit about which work you're actually funding, and be honest about what you are choosing not to get as a result.

And then play four: have that mandate conversation with your CEO, your CHRO, your business leader — depending on what seat you're sitting in. But have the conversation now, not after you've been building for a while. And if you're in an HR role and you've never specifically aligned with your CEO on what success looks like, that conversation is way overdue. What the talent function is expected to produce — you need to know. How does it connect to the strategy? Who owns the decisions? How do we measure whether any of these things are working? That's the conversation I structured the Mandate Protocol around, by the way. It's a practical way to get explicit alignment before the function gets built around the wrong brief. It's the foundation that most HR relationships are missing. And the absence of it is usually what I'm cleaning up when a company brings me in.

Now, I know that some of you are sitting there thinking, Jackson, we brought in HR two years ago, and I'm not entirely sure that conversation remains available. Okay, that's probably a fair read. But the absence of a mandate does not resolve itself. It just produces more of what it's already been producing. And to be fair, that conversation is really uncomfortable for about 30 minutes, and then it's not uncomfortable anymore.

If there's one thing I want you to carry out of this episode, it's this: the decision to bring in HR is not the hard decision. The hard decision is what you ask HR to build. And most companies are answering that question by accident.

So thank you for spending some time with me today. I appreciate you being a part of this community of senior leaders who want to rethink how human capital really works.

And if you're thinking about how to apply this in your own situation, I have a couple of resources I'd like to point you to. If role clarity and execution alignment is where you start, you should check out getpropulsion.ai. Their AI teammates are helping leadership teams translate strategy into individual accountability and give every employee a clear line of sight to what actually drives the business. And if you are in private equity, they have an entire team of agentic teammates that can help you pre-deal and post-deal to execute the business thesis. Really good stuff, all done with AI.

And if you're a CHRO stepping into the seat for the first time — or preparing to do that — that's exactly who I built the practice for. Find everything at mytalentsherpa.com. If you'd like to read the Substack, it's at talentsherpa.substack.com. And if you want the mandate conversation structured before you walk in the door, the Mandate Protocol is at mytalentsherpa.com/mandate-protocol. $297. It's a bargain. 14-day full refund if it doesn't deliver. No questions asked.

So until next time, keep raising the bar. Keep asking: what are you actually building this for? And keep on climbing.