HR Is Automating Backwards
Scroll through HR feeds this month and you’ll find the same post on repeat. Someone automated resume screening. Someone stood up an onboarding bot. Someone shipped a scheduling assistant and cut ticket volume by forty percent. Same caption energy every time, look what I built.
I’ve built a few of these myself. Lately I’ve started asking a question that kills the mood a little.
Built toward what?
That’s the reversal. We used to start with the goal and work backward to the small moves that got us there. Now most of HR starts with the small move and hopes a goal shows up later.
It won’t. Not on its own.
Where it actually breaks
The individual wins are real. A better screening tool screens better. A scheduling bot fixes scheduling. Nobody is disputing that the parts work.
The problem shows up in the seams. Right now, in a typical HR org:
Many disconnected systems are running side by side, each solving its own slice of the employee lifecycle.
More than two-thirds of companies say those systems still don’t talk to each other.
The employee becomes the integration layer, logging into four places to do what should have taken one.
That’s not a legacy IT problem left over from 2015. That’s what happens when every team solves its own process in isolation, one AI tool at a time, with no shared picture of the experience underneath it. Each tool becomes an island. Somebody still has to build the bridge. Right now, that somebody is the employee.
The counter I’d make if I were you
Vision-first AI programs don’t have a clean track record either. Analysts expect more than 4 in 10 current agentic AI projects to get shelved within two years, buried under cost, complexity, and promises nobody could keep.
Fair. Point taken.
But that’s not the same failure. Those projects didn’t collapse because someone had a destination in mind. They collapsed because they tried to map every stop on the route before the train left the station.
Starting with the goal doesn’t require that. It requires one sentence, what experience are you building toward, before you pick the next tool. Not a five-year architecture diagram. A destination. Everything after that is sequencing, not prophecy.
Before your next AI tool, answer this
Whether it’s a chatbot, a screening model, or an assistant that drafts your offer letters, someone on your team should be able to answer this without stalling:
What job is this doing inside the whole employee experience, not just inside this one process?
If the honest answer is a shrug, or “it saves time,” that’s not a goal. That’s activity dressed up as strategy.
You don’t need the whole architecture mapped before you start. You need to know where you’re walking before you decide which shoes to buy.
So the real question isn’t whether you’re using AI in HR. Almost everyone is now. It’s whether you could draw a straight line from the last tool you adopted to an actual destination, or whether you just liked the momentum.