Talent Acquisition Is Not a Function. It’s an Operating System.
Why hiring failures are usually design failures
This week, I want to talk about Talent Acquisition.
Partly because it’s one of the most misunderstood parts of an organization.
And partly because I’ve just had a recent departure on my own team that forced me to zoom out and look at the function again, not emotionally, but systemically.
For founders and entrepreneurs right now, hiring is often treated like a grocery run: we realize we’re hungry, we grab what looks good on the shelf, and we hope it tastes good when we get home.
We’re entering a moment where labour supply constraints, skills volatility, and AI-driven operating model shifts are all colliding. And the result is simple: people strategy is now directly limiting speed, execution, and resilience.
Most organizations feel this, they just don’t always name it. TA is the operating system that governs speed. Get it wrong and you don’t just lose money, you lose Signal Integrity. You introduce noise into a system that was finally starting to hum.
Hiring isn’t the problem. The system is.
When people talk about TA, they usually mean hiring.
Posting roles. Screening CVs. Interviewing. Closing.
But that’s like calling a nervous system a reflex.
In practice, Talent Acquisition functions as an operating system that coordinates:
what roles exist and why
how work is prioritized
how capabilities enter (or exit) the organization
how fast teams can move without breaking
For founders, this system quietly governs everything else: product delivery, customer acquisition, compliance, even cash efficiency.
When TA works, growth flows.
When it doesn’t, founders become the bottlenecks (or the firefighters).
Culture fit, founder intuition, and the myth of “hire fast, fire faster”
I recently watched an interview with Steven Bartlett where he talked about how deeply involved he is in headhunting and assessing culture fit. He’s very open about spending significant personal time on hiring.
On the surface, that seems to contradict the idea that founders shouldn’t be in the weeds.
That reinforces something many founders already intuitively know: culture fit matters. A lot.
So does personality. So does learning agility.
But without clear role architecture, decision rights, and success definitions, “culture fit” quickly becomes hard to scale and to delegate safely.
AI won’t fix a broken hiring system
At the same time, the recruiting world is rushing toward AI.
Every ATS now (and trust me, I’ve worked with quite a few of them) seems to come with AI embedded. Screening, matching, ranking, shortlisting. Faster pipelines. Cleaner dashboards.
Josh Bersin has written extensively about this shift, especially the move to skill-based and capability-centered hiring models. I agree with the direction. He also points out that AI is only as good as the system, and the data, it sits inside.
If roles are poorly designed, if success criteria are vague, if historical hiring decisions were biased or inconsistent, AI doesn’t remove those issues. It accelerates them.
This is why claims of bias-free recruiting are a bit complicated.
AI doesn’t replace judgment. It amplifies whatever judgment already exists.
Which brings us back to the question: what should be automated, and what must stay human-led?
Before you hire anyone, zoom out
In my experience, most hiring problems don’t start in the interview.
They start much earlier.
Before the process even begins, founders need to step back and ask:
Are our jobs actually well designed?
Does everyone understand what success looks like in this role?
Are we hiring for a static role, or for a capability the system currently lacks?
Is this a skills-based team, or a project/capability-based one?
Is the individual aligned with the team’s goals, and is the team aligned with the company’s direction?
These questions sound obvious. In reality, especially in scale-ups, they’re often skipped in the rush to “just get someone in.”
That’s when friction creeps in..
Talent Acquisition as a closed-loop system
When you strip it back, founder-friendly TA looks less like a pipeline and more like a loop:
Inputs → Decisions → Outcomes → Feedback → Iteration
Inputs are things like strategy, runway, risk tolerance, customer roadmap.
Decisions include role design, assessment methods, compensation, onboarding.
Outcomes show up as time-to-fill, quality of hire, early attrition, productivity ramp.
Feedback comes from candidate drop-off, manager calibration, performance data.
Most organizations measure the outcomes. Very few learn from the feedback.
When growth slows or restructuring hits
In my view, restructuring is also a TA problem (just in disguise).
The real question becomes:
How do we secure the capabilities needed for the next plan, quickly and credibly, while reducing capabilities we can no longer afford?
That’s not about hiring more efficiently.
It’s about thinking in capabilities, not roles.
Sometimes the right move is to hire.
Sometimes it’s to redeploy.
Sometimes it’s to automate.
Sometimes it’s to stop doing the work altogether.
But those decisions only make sense when the system is clear.
So what actually helps
Again (and I feel like I keep saying this), there is no magic solution that applies in every case. But patterns emerge.
Strong TA systems tend to:
design roles as responses to constraints, not as generic job descriptions
hire for outcomes, not just experience
standardize selection where it improves decision quality
use AI to reduce noise, not replace judgment
and treat onboarding and early tenure as part of hiring, not an afterthought
Most importantly, they’re honest about what the system can and cannot carry.
Talent Acquisition isn’t about finding better people.
It’s about building a system that lets the right people do good work without becoming the bottleneck themselves.
For founders, it’s one of the most strategic design decisions they will ever make.