Call it the HR tech trap: buy the platform, run the rollout, declare it done, and then wait for a return that never quite shows up. Gartner put a number on this in June 2024. Less than a quarter of HR employees, 24 percent, told Gartner their organisation's HR function is deriving the maximum value from its HR technology. That is not a story about under-investment. Most of these companies have spent real money on real platforms. It is a story about what happens after the invoice is paid.
Most mid-market and enterprise HR functions now run some combination of a core HRIS, a performance module, a learning platform and a handful of point solutions bolted on around the edges. Rarely is the problem that leaders didn't take HR technology seriously enough. The problem is what happened, or didn't happen, in the twelve months after the go live date, when the project team moved on and nobody was left owning the outcome.
Why the HR Tech Trap Persists
The gap Gartner measured is not a technology gap. It is a use gap. Among more than 1,200 employees Gartner surveyed in February 2024, 69 percent reported experiencing at least one barrier when interacting with HR technology in the past twelve months. Believing a tool matters and knowing how to extract value from it are two different competencies, and most organisations only build the first one.
24%: HR employees reporting maximum value: Said their organisation's HR function is deriving the maximum value from its HR technology (Gartner, June 2024).
69%: Hit a technology barrier in the past year: Of more than 1,200 employees surveyed, reported experiencing at least one barrier when interacting with HR technology in the prior 12 months (Gartner, February 2024).
Put those two figures side by side and the shape of the problem gets clear. Roughly seven in ten employees hit friction using the tool. Roughly three in four HR functions fall short of the value they were promised when the tool was bought. Those are not two separate problems. They are the same problem, measured from two different seats in the building.
The conflation happens quietly, and usually with good intentions. A project sponsor reports to the board that the platform is live, on time, on budget. That report is true, and it is also the point where accountability tends to end. Nobody schedules a follow up review to ask whether the tool actually changed how a manager makes a promotion decision, or whether HR is spending less time on manual admin six months later. The project closes. The value question never opens.
Deployment Is Not the Same Job as Value
Somewhere in the buying process, "we deployed the platform" quietly became a stand-in for "we got the return." They are not the same claim. Deployment is a project with a start date and an end date: contracts signed, data migrated, logins issued, a training video watched once. Value is not a project. It is a habit, and habits only form when the tool fits the way people already work, or the way people work is deliberately redesigned to fit the tool. The HR tech trap sits in the assumption that switching the software on finishes the job, not in the software itself. Most rollouts skip the second half entirely and call the first half success.
The barriers behind that 69 percent figure are rarely dramatic. Nobody staged a walkout over a clunky interface. The friction is smaller and more corrosive than that: a manager who cannot find the approval screen without asking someone else, a process that takes four extra clicks compared with the spreadsheet it replaced, a self-service portal employees quietly route around by emailing HR directly anyway. Each barrier on its own looks trivial. Stacked across a whole workforce, over twelve months, on a system that was supposed to remove admin rather than add it, they add up to a platform that technically works and practically doesn't.
- Workflows built around the old process, bolted onto the new system instead of redesigned for it
- Managers and employees trained once at launch, never at the actual moment they need the tool
- No single owner accountable for whether the tool is used well, only for whether it was switched on
- Data and permissions structured for the vendor's default setup, not for how the organisation actually decides
- A shadow process, a spreadsheet, an email thread, that quietly survives because it is still faster than the system
What Closes the Gap: Change Management, Not More Software
The instinctive fix is to buy again: a better module, an add-on, a second platform to patch what the first one didn't solve. That instinct is usually wrong. Gartner's own framing is a value question, not a features question, and value is not a line item you can purchase. It is the product of deliberate change management: naming the specific decision or task the technology is meant to improve, redesigning the workflow around that decision, training people at the point of use rather than at the point of purchase, and holding someone accountable for the outcome rather than the rollout.
- Name the job before you name the tool: Every HR platform is bought to do a specific job: faster approvals, cleaner data, less manual admin. Write that job down before the contract is signed, and use it as the only measure of success after go live, not licence counts.
- Redesign the workflow, don't bolt the tool onto the old one: If the new system just automates the old spreadsheet process step for step, it inherits every inefficiency the spreadsheet had. Rebuild the workflow around what the platform can actually do, rather than around habits it was meant to replace.
- Train at the moment of use, not on launch day: A single onboarding session teaches people how to log in. It does not teach a manager, six weeks later, how to run a difficult conversation through the new performance module. Build training into the actual moments people need it.
- Assign one owner accountable for value, not adoption: Login counts and licence utilisation measure whether the system was switched on. They say nothing about whether it changed a decision. Someone senior needs to own the value outcome specifically, not the deployment milestone.
Signs Your Organisation Is Already Inside the Trap
A few patterns are reliable tells. Usage concentrates in the transactional basics, payroll, leave requests, and drops away everywhere the tool was meant to add strategic value: workforce planning, succession, skills data. Managers keep a personal shadow system, a spreadsheet, a folder of saved emails, because it is faster than trusting the platform's report. HR itself still manually reconciles data before it goes into a board pack, because nobody fully trusts what the system produces unassisted. Not one of these shows up in a licence utilisation report. Each one is the real evidence of a value gap.
If two or three of those patterns sound familiar, technology was never the constraint. The constraint has always been the leadership work needed to make people trust the system enough to actually use it.
Tools Are Not Capability
This is the same trap I've written about in the wider AI adoption conversation. Buying the tool is the easy part of the work; building the capability to use it well is the harder, longer part that most budgets never fund. I set this out directly in The Generic AI Trap, and it is exactly why most digital transformation programmes fail for leadership reasons, not technical ones. HR technology is not a special case. It is the same architecture problem wearing a different department's badge.
The fix does not live inside the HR function alone, and it does not live inside IT either. It lives with the managers who use the tool every day. I've written before about how middle managers make or break adoption in daily operations, and HR technology follows the identical pattern: the platform succeeds or fails in the thousands of small, ordinary decisions a manager makes about whether to use it properly or quietly work around it.
This does not require a bigger technology budget. It requires a smaller number of people, usually one, whose job is explicitly to close the distance between what the platform can do and what the organisation actually does with it. Most organisations have a project sponsor for the buying decision. Very few have anyone genuinely accountable for playing that role during the eighteen months after go live, which is exactly the period Gartner's numbers describe.
- The Deployment Lens: Success is measured by whether the system is live: contracts signed, users provisioned, data migrated, training completed once.
- The Capability Lens: Success is measured by whether the system changed how a decision gets made: faster, better informed, less manual, and used without a workaround.
A platform that nobody has to be persuaded to use is not lucky. It was designed that way, on purpose, by someone who treated the rollout as the start of the work, not the finish line.
The Real Cost of Staying in the Trap
Every quarter an organisation spends inside the HR tech trap is a quarter of licence fees, integration cost and change fatigue paid for a system operating at a fraction of its design. Worse, it teaches the workforce a lesson that is hard to unlearn: that the next platform, and the one after that, will probably go the same way. Scepticism about technology investment compounds across an organisation. The fifth rollout is always a harder sell than the first, and it is HR leadership that inherits that credibility problem, not the vendor who has already moved on to the next account.
That is the real argument for treating adoption as a leadership discipline rather than a vendor selection exercise. The platform becomes a fixed cost the moment the contract is signed. Whether it becomes an asset or a write off is decided afterwards, by how deliberately the organisation manages the change happening around it.
If your organisation is sitting inside its own version of this gap, the fix is rarely a new vendor. It is the leadership work of turning a deployed system into a used one: naming the job, owning the workflow, training at the point of need, and measuring the decision the tool was bought to improve. That is the exact ground CapabilityAI and the Architecture Accelerator programme are built to cover: not more technology, but the capability to run the technology you have already bought.
What to connect before publication
The useful test for the hr tech trap: why adoption doesn't equal value is whether a leader can make a better decision in the work that already exists. Start with one live case, write down the judgement that was used and compare it with the result that followed. Then ask what the team would do when the same pressure appears next month. That question keeps the article close to practice rather than turning it into another list of principles. It also gives a sponsor something concrete to challenge: the owner, the evidence, the trade-off and the point at which the plan should change.
A second check is transfer. If the idea in this article depends on one senior person, a special workshop or a project team standing beside the work, it has not yet become an organisational capability. Try the decision with a new manager or an unfamiliar case. Note what remains clear, what needs coaching and what still relies on personal memory. That small test gives the hr tech trap: why adoption doesn't equal value a boundary. It says what the approach can support now, what must be tested next and which claim should not be made until the evidence is stronger.
Related decisions to test
This topic sits beside three decisions that often get separated in practice. Read measure leadership capability across an organisation; the team collaboration and effectiveness framework; lead organisational transformation successfully. The comparison is useful because it keeps the argument in this article specific: which decision is changing, who owns it and what evidence would show that the change has travelled into everyday work? Use the linked pieces as contrasts, not as a substitute for the judgement required here.