All tracks / Foundations of Agentic HR / The portal nobody visits: why HR tech has an adoption problem

The portal nobody visits: why HR tech has an adoption problem

Billions invested in HR technology that employees and managers avoid. The adoption crisis is architectural, not a training problem.

7 min read Foundations of Agentic HR

The adoption ceiling nobody talks about

Here is a number that should concern every CHRO: most enterprises see 20-40% active usage of their HCM portals for anything beyond mandatory transactions like submitting PTO or viewing pay stubs.

That means the majority of the workforce intelligence sitting in your HR systems goes unused. Not because the data is bad. Not because the features do not exist. Because nobody opens the application.

A manager who needs to check succession readiness for her team does not open the HCM. It takes 6 clicks to get there, she cannot remember her password, and the last time she tried, the interface was confusing. So she does what every manager does – she makes the decision based on gut feel and moves on.

The architectural root cause

The portal model forces people out of their workflow. Employees live in Teams and Slack 8 hours a day. They visit the HR portal once a month, if that. This is not a training problem. It is a physics problem.

HR teams have responded by layering chatbots on top of portals. But a chatbot that answers “how many PTO days do I have?” is fundamentally different from an agent that notices a retention risk and proactively assembles an intervention plan. The architectural constraint remains.

Compare the daily active usage of Microsoft Teams (300M+ users spending hours per day) with the monthly active usage of any HCM portal. The gap is not closing. It is widening.

The real cost of non-adoption

The cost is not license waste – though that is real. The cost is the decisions that never happen because managers do not open the system.

  • Succession gaps go unnoticed until someone resigns
  • Retention risks go unaddressed because the signals are in a dashboard nobody checks
  • Career development conversations happen annually at best, because the tools that should support them are buried in a portal
  • Internal mobility fails because employees cannot find opportunities they do not know exist

Every one of these represents a workforce decision that was either made poorly or not made at all. And every one of them has a measurable cost to the business.

What this means for the category

The adoption problem is not going to be solved by better UX on the portal. Workday and SAP have invested heavily in modernizing their interfaces, and the adoption numbers have not meaningfully changed. The constraint is the model itself.

The shift that matters is from portal-based delivery to flow-of-work delivery. Instead of asking employees and managers to come to the HR system, the intelligence comes to them – in the tools they already use, at the moment they need it, with the context to be useful.

This is what agents enable. Not a chatbot bolted onto a portal, but an intelligent system that lives where your people work and acts on their behalf.

Key insight

The adoption problem is not a UX problem. It is a delivery model problem. No amount of redesigning the portal fixes the fundamental friction of pulling people out of their flow of work.

Key terms

System of Record
Software that stores and manages data (e.g., your HCM). It holds information but does not reason about it.
Flow of Work
The tools and environments where employees spend their day - Teams, Slack, email. Not the HR portal.
Portal Architecture
A design model where users must navigate to a dedicated application to access functionality. The opposite of flow-of-work delivery.
The bottom line

The adoption problem is a delivery model problem, and it requires a delivery model shift. Agents that live in Teams and Slack solve this by meeting people where they already work - not asking them to visit another portal.