Stop Implementing Projects. Start Building Capabilities.

HR spends a lot of time talking about projects.

We're implementing a new HRIS.

We're launching a talent marketplace.

We're redesigning performance management.

We're introducing AI.

We're rolling out a new skills framework.

Projects matter. They move organizations forward. But I've started to wonder if we sometimes become so focused on delivering the project that we forget to ask what should remain after the project is over.

Because projects end.

Capabilities stay.

That's an important distinction.

When an HRIS implementation finishes, what did the organization actually gain? Was the outcome simply a new platform, or did it become better at managing workforce data? Did managers make better decisions? Did employees have a better experience? Did HR become easier to scale?

Technology can support those outcomes, but it doesn't create them on its own.

The same applies to AI.

Many organizations describe AI as another initiative on the roadmap, alongside system implementations and process redesign. I see it differently. AI isn't a capability. It's something that strengthens capabilities that already exist. If workforce planning is weak, AI won't suddenly make it strategic. If job architecture is inconsistent, AI won't create clarity. If governance is unclear, AI will simply operate within that uncertainty.

That's why I think HR should spend less time discussing implementations and more time discussing capabilities.

What capabilities does the organization need to execute its strategy?

Can we plan our workforce with confidence?

Can we move talent internally?

Can managers make consistent decisions?

Can employees understand how careers develop?

Can leaders trust the data they're using?

Can HR adapt as the business changes?

Those are capabilities.

Technology, processes, governance, data, and operating models all contribute to them, but none of them should become the objective.

I've worked on projects involving HR technology, People Operations, analytics, workforce planning, and process transformation. Looking back, the projects that created the most lasting value all had something in common. They improved how the organization operated long after the implementation was complete. People stopped talking about the system because they started experiencing the capability.

To me, that's what success looks like.

It's also why capability building is becoming more important than ever. Technology is evolving quickly, and organizations will continue replacing platforms, introducing AI, and redesigning processes. Those changes will keep happening. The capabilities underneath them, however, become part of how the organization works.

Perhaps that's the shift HR needs to make.

Instead of asking, "What should we implement next?"

We should ask, "What capability are we trying to build?"

The answer might still involve new technology.

But the technology should never be the strategy.

It should simply be one of the ways we strengthen the capabilities the business depends on.