Services Webinars Blogs Contact

TA Was Never Designed, It Was Accumulated

Why the talent function you inherited is a record of old constraints, and what becomes possible once you notice.

Look closely at the shape of any talent acquisition team and you are not looking at a design. You are looking at an archaeological record. Each layer was laid down in a different decade, to solve a different bottleneck, with the tools available at the time. The sourcer, the coordinator, the recruitment marketer, the TA operations lead, the analytics partner. None of these roles arrived as part of a plan. They accumulated, one solved problem at a time, until the sediment hardened into an org chart that everyone now treats as the natural order of things.

It is worth sitting with that idea, because most conversations about the future of TA skip straight past it. We argue about headcount ratios, about whether to centralise or embed, about which platform to buy next. We rarely ask the prior question. Why does the function look like this at all?

And the honest answer is that it looks like this because of a long sequence of constraints, most of which no longer exist.

A Function Built One Bottleneck at a Time

Go back far enough and recruitment was a local, human, analogue affair. Roles were filled through word of mouth, the notice in the window, the classified column in the local paper, the letter in the post. If you wanted to reach beyond the people you already knew, you needed someone whose whole job was reach.

That is where the agency and the search firm came from. Access to people was genuinely scarce, and scarcity is always met by a market. The headhunter with the Rolodex existed because that Rolodex was the moat. You paid handsomely for it because you could not build it yourself.

Then the job board arrived, and the constraint shifted. Suddenly a vacancy could be broadcast to thousands of people at once. This sounds like pure progress, and in many ways it was, but every new channel of reach creates a new problem of volume.

A flood of applications needs someone to read it, sort it, and respond to it. So the in-house recruiter grew into a more defined role, and underneath that role a new layer formed to manage the sheer administration of it all.

The applicant tracking system was the next sediment layer. Once the volume became unmanageable by inbox alone, companies bought software to hold it, and software needs people to operate it. Coordinators appeared to wrangle the diaries and the interview logistics. TA operations emerged to own the system itself, the workflows, the configuration, the reporting that leadership started to ask for.

None of this was waste. Each role was a rational response to a real difficulty in front of it.

The professional networks of the 2010s changed the constraint again. For the first time, proactive outreach at scale was possible, and so the sourcer split away from the recruiter as a distinct discipline. As competition for talent intensified, employer brand and recruitment marketing became functions in their own right, because attention was now the scarce thing and attention has to be earned. Then analytics matured, dashboards multiplied, and a role appeared to make sense of the numbers.

Step back and the pattern is unmistakable. Reach was hard, so we hired for reach. Volume was hard to manage, so we hired to manage volume. Coordination consumed everyone’s time, so we hired coordinators.

Every channel of communicating with people about work, the classified, the phone call, the email, the job board posting, the network message, demanded a human to operate it, and that human became a role, and that role became a team, and that team became a department.

The talent function is the cumulative answer to a century of questions, asked one at a time, and never once asked together.

This Was Never a Failure of Design; It Was the Absence of It

There is an important point of fairness here, particularly for anyone who has spent a career building these teams. The accumulation was not a mistake. It is what every functional area does.

You grow capability to meet the constraints directly in front of you, because the alternative, pausing to redesign the whole system from scratch while the requisitions keep landing, has never been a real option.

No TA leader was ever handed a blank page and the time to design the function deliberately. They were handed a problem, a budget, and a deadline, and they solved it the way the technology of the moment allowed.

So the shape of your team today is not a verdict on anyone’s judgement. It is a fossil record of solved problems.

Read the org chart carefully and you can date each layer to the constraint it was built to overcome.

The trouble is not that the structure was wrong when it formed. The trouble is that constraints expire, and structures do not expire with them.

The Constraints That Built the Model Have Quietly Collapsed

Three things have changed at once, and together they remove almost every original justification for the accumulated model.

The first is access. The scarcity that built the entire search and sourcing industry has largely evaporated. Most people are now reachable, visible, and addressable in ways that would have seemed impossible to the recruiter of even fifteen years ago.

The Rolodex is no longer a moat, because everyone has one. When access stops being scarce, the roles that existed primarily to provide access have to justify themselves on something else.

The second is reach without borders. The local talent market that shaped local hiring teams has become a global, distributed one. Work itself has detached from geography for a large and growing share of roles.

The assumptions about proximity, about needing people on the ground in a particular city, that quietly underpinned how teams were sized and located, no longer hold the way they did.

The third, and the one reshaping the ground fastest, is that the operational work itself can now be done by infrastructure rather than headcount.

The coordination, the sourcing administration, the screening, the scheduling, the communication management, the reporting, the institutional memory, the tasks that justified entire layers of the function, are increasingly executed by agentic systems rather than people.

Historically these things required teams. Now they increasingly require software that is configured well.

Hold those three together and the implication is uncomfortable.

The constraints that each historical layer was built to overcome have weakened or disappeared, but the layers remain.

We are running organisations designed for problems we no longer have.

The Trap Is Optimisation. The Opportunity Is Design.

The natural reflex, when new tools arrive, is to bolt them onto the existing structure and call it transformation. Buy the AI sourcing tool, hand it to the sourcing team, and carry on.

This feels like progress and produces a little of it, but it is the equivalent of breeding a faster horse. You are improving the efficiency of a model whose entire shape was dictated by constraints that have since lifted.

The accumulated structure becomes the thing you optimise, when it should be the thing you question.

Because here is what is new. For the first time, the talent function has both the reason and the means to be designed rather than inherited.

The reason is that the old constraints no longer hold. The means is a set of tools and a level of access that change what a single well-supported person can do.

Put those together and a question the function has never really been allowed to ask becomes not just possible but necessary.

If you were designing talent acquisition today, from first principles, with this access and these tools, would you build what you currently have?

Almost no one, asked honestly, says yes.

And that gap, between the structure we inherited and the one we would deliberately choose, is the most interesting space in talent right now.

It is not a question of how to make the accumulated model a little leaner. It is a question of what a model designed on purpose, for the world as it actually is, would look like.

That is the question worth sitting with. It is the one we want to take up next.