Services Webinars Product Blogs Contact

Your AI Tools Are Sitting Inside a 2010 Org Chart

We are all at stage one, and that is exactly where we should be. The shift that matters is not a tool you buy. It is a lens you adopt.

Once you accept that the talent function was accumulated rather than designed, a strange thing happens to the way you read the last two years. Almost every company has responded to the arrival of AI in the same way, and it is not the way the headlines suggest. Budgets opened. Tools were bought. Access was granted. Recruiters got copilots, sourcing got an engine, scheduling got an agent, screening got an assistant. On a slide, this looks like transformation. In the building, something quieter has happened. A new engine has been dropped into an old chassis, and the chassis has not moved an inch.

This is worth naming plainly, because it is the single most common position in talent acquisition right now. The tools are genuinely new. The structure they have been plugged into is not. Every clever piece of AI has been handed to the role that already owned that task. The sourcing tool goes to the sourcer. The scheduling agent goes to the coordinator. The screening assistant goes to the recruiter. The dashboard goes to the analyst. Each task gets a little faster, and the org chart does not move, because nobody designed it to. We have automated the work without revisiting the shape of the team that does it.

That is stage one. And here is the part that matters more than anything else in this piece. Almost everyone is at stage one, and being there is not a failure.

Stage one is the right place to be, not a sign you are behind

There is a lot of noise at the moment designed to make TA leaders feel late. The webinar that implies your competitors have already rebuilt everything. The vendor deck that suggests you are one purchase away from being left behind. Most of it is theatre.

The honest reality is that the overwhelming majority of talent functions, including the sophisticated ones, are doing exactly what you are doing. They have bought capability and laid it over the existing model, and they have not yet stepped back to ask what the existence of that capability actually changes.

This is not a weakness. It is how adoption works. You cannot redesign a function from the ground up while it is running at full load, with requisitions landing every day and hiring managers waiting on offers. The first thing any organisation does with a powerful new tool is use it to do the current job faster. That is sensible. It builds confidence, it produces some early wins, and it teaches the team what the tools can and cannot do.

Stage one is the on-ramp, and everyone joins the road there.

So if you are looking at your function and seeing AI tools bolted onto a structure that would be perfectly recognisable to a recruiter from 2010, you are not behind. You are exactly where the curve begins. The mistake is not being at stage one. The mistake is assuming stage one is the destination.

The trap is quiet, and it is comfortable

Here is how functions get stuck. The tools arrive, the work speeds up, and the early efficiency feels like progress, because it is. Time to schedule drops. Sourcing output rises. Reporting that used to take a day takes an hour. Leadership sees the numbers move and concludes the transformation is underway. The budget is spent, the boxes are ticked, and the organisation settles into a more efficient version of the model it already had.

And then it stops. Not because anyone decided to stop, but because nobody framed stage one as a stage. It got framed as the answer. The function is now running an accumulated structure, designed for a set of constraints that have already collapsed, slightly faster than before. This is the comfortable trap, and it is the one most companies will fall into. They will spend the next few years optimising tasks inside a shape that no longer needs to exist in that form, and they will call it modernisation.

The reason this happens is subtle but important. Adopting a tool and rethinking a model are two completely different activities, and the first one disguises the second. A tool changes a task. Only a new lens changes a structure. You can hand AI to every role in the function and leave the fundamental design entirely untouched, because the tools slot neatly into the existing boxes. Nothing about buying technology forces you to ask whether the boxes themselves still make sense.

The change that actually matters is a change in the question

The fundamental shift underneath all of this is not that recruiters now have a copilot. It is that the constraints which built the function in the first place have weakened or disappeared. Access to people is no longer scarce. Reach is no longer bounded by geography. The operational labour that justified entire layers of the team can increasingly be carried by infrastructure rather than headcount. Those are not small tooling upgrades. They are the removal of the very problems the accumulated structure was assembled to solve.

When the problems change, the right response is not to do the old work faster. It is to ask whether it is still the right work, arranged in the right way. That is the move stage one does not make and the later stages depend on. Stage one optimises the tasks inside the inherited model. Everything beyond it begins to redesign the model itself, around what the tools and the access now make possible. The bridge between the two is not a budget line or a procurement decision. It is a shift in how you think about the function at all.

This is why the first-principles lens matters so much. Looking at TA through an inherited lens, you see a set of roles to make more efficient. Looking at it through a first-principles lens, you see a set of outcomes to achieve and you ask, with no loyalty to the current structure, what arrangement of people, infrastructure and external capability would actually deliver them today. Same function, completely different question. The tools are the same in both views. What changes is whether you are improving the answer you inherited or designing a better one.

A stage evolution, not a leap off a cliff

None of this means tearing down your team on Monday morning, and it is important to say that clearly, because the rhetoric around AI tends to swing between complacency and panic with very little in between. This is a stage evolution. It has steps, each one reachable from the one before, and there is no version of this where a functioning talent organisation reinvents itself overnight. That is not how operating models change, and anyone selling you that urgency is selling you something.

What separates the companies that will move along this curve from the ones that will stall at stage one is not money, and it is not tooling, because at this point everyone has roughly the same access to both. The difference is recognition. The companies that move are the ones that look honestly at their newly accelerated, fundamentally unchanged function and recognise that the efficiency, welcome as it is, is not the transformation. The transformation is the redesign that the new conditions now permit, and the willingness to approach the whole function from first principles rather than inheritance.

So treat stage one as what it is. A real and necessary beginning, a place where almost everyone is standing right now, and a place worth being. Just do not mistake it for the finish. The work of stage one is to adopt. The work of everything that follows is to design, and design starts with a question rather than a purchase. What would talent acquisition look like if you built it for the world as it actually is, rather than the world it grew up in?

That is the lens. In the pieces that follow, we want to put it on properly, and look at what comes into focus.