Stop Implementing HR Technology. Start Building HR Capabilities.

One of the first questions organizations ask when they want to modernize HR is, "What technology do we need?"

It's a logical place to start, but I don't think it's the right one.

After working on HR technology implementations across organizations of very different sizes, I've noticed that the success of a project rarely depends on the platform itself. Most modern HR solutions are capable of supporting recruiting, performance, learning, compensation, workforce planning, or employee experience. The bigger question is whether the organization is clear about the capability it's trying to build.

Technology is a means, not the outcome.

That distinction sounds obvious, yet it's surprisingly easy to lose sight of once a project begins. Conversations quickly shift toward features, integrations, configuration, timelines, and vendors. Before long, the implementation itself becomes the objective. Success is measured by whether the system went live rather than whether the organization actually works differently because of it.

I've seen this happen more than once. A new HRIS is implemented, but managers continue maintaining their own spreadsheets. A skills platform is launched, but nobody has agreed on a common skills language. AI is introduced into recruiting, yet recruiters continue following the same process because nothing around the technology has changed.

The implementation was successful.

The capability wasn't.

That's why I think HR should spend less time asking, "Which platform should we buy?" and more time asking, "What are we trying to become better at?"

If the goal is workforce planning, technology alone won't create that capability. Organizations also need reliable workforce data, consistent job architecture, collaboration between HR and Finance, clear planning processes, and leaders who know how to use workforce scenarios to make decisions.

If the goal is internal mobility, the challenge isn't simply implementing a talent marketplace. Employees need confidence that roles are described consistently, managers need to support internal movement, career paths need to be visible, and skills need to be defined in a way that allows opportunities to be matched fairly.

The same pattern appears across almost every HR initiative.

Technology supports the capability.

It doesn't create it.

This is one of the reasons some organizations seem to move faster every time a new technology appears. They're not necessarily better at implementations. They've spent years building the operational foundations underneath: standardized processes, governance, trusted data, clear ownership, and common definitions. When a new platform arrives, it strengthens capabilities that already exist.

Other organizations expect technology to solve fragmentation that has accumulated over time. Processes vary across business units, ownership is unclear, data definitions are inconsistent, and managers work around the system instead of with it. Those challenges don't disappear after implementation. They simply move into a newer interface.

I think AI is making this even more apparent.

Many organizations are looking for AI to transform HR, but AI depends on the same capabilities that HR has always relied on. If data isn't reliable, processes aren't consistent, or governance is weak, AI doesn't solve those problems. It operates within them.

Perhaps that's why the organizations seeing the greatest value from AI are often the same organizations that invested in operational excellence long before AI became part of the conversation.

Looking back, I don't think the most valuable work I've been involved in was implementing technology. It was helping organizations build capabilities that continued creating value long after the implementation was complete. Sometimes technology played a central role. Sometimes it barely changed. The lasting impact came from improving how work was designed, how decisions were made, and how different parts of HR operated together.

Technology will continue to evolve. The capabilities we build around it will determine whether those investments create lasting value or become the next system employees learn to work around.