Home/Insights/Measuring adoption
Is the system working? Measuring adoption after go-live
By Zené Olivier / Alexandra Wagener · Zanani People Solutions, Cape Town
5 min read

Logins tell you people opened the door. They do not tell you if the work was more efficient.
To measure HR system adoption, track whether people use the system for the tasks it was designed for, whether the quality of the work outcomes have improved, and whether the old ways have stopped. Add a few data-quality checks and a short employee pulse, then report the trend to leaders every month in plain words. A post-implementation review, a few months after go-live, tests the system against the goals in your business case.
In our view, adoption is the real finish line. Go-live is the start of the measuring, not the end of the project.
Why logins are not enough
McKinsey's research on AI adoption makes a point that fits HR systems too. Many organisations measure log-ins and licences. What they do not measure is whether the work has improved. A stronger approach links adoption to how the work performs: cycle time, quality, decision speed, and risk (McKinsey, How to close the agentic adoption gap).
Someone can log in and still do the actual work elsewhere. So measure the work quality in the system.
What to measure
Start with the goals in your business case. Each goal gets one or two measures. If a measure does not link to a goal, drop it.
Use: are people using it for the right tasks?
- Share of leave requests submitted in the system.
- Share of approvals done in the system by managers.
- Share of employees who viewed their payslip online.
- Active users each month, by site, and department.
Work: are the work outcomes better?
- How long a leave request takes, from request to approval.
- How long onboarding takes, from offer to first payslip.
- Payroll corrections each month.
Quality: can we trust the data?
- Employee records with all required fields complete, including EE fields.
- Support queries, and the most common topics.
Old ways: have they stopped?
- Paper forms still received.
- Side spreadsheets still used for tasks the system should handle.
- Additional workarounds have developed since go live.
People: how does it feel?
AIHR suggests short pulse surveys at key moments. For example, a month after launching a new leave portal, ask how easy it is to submit a request and where people get stuck (AIHR, 7 HR digital transformation challenges).
Break it down by group
An overall number can hide problems. Head office may be fine while a regional site is not.
Split your measures by site, department, role or shift. Look closely at frontline teams and employees without work email. They often need different support.
Watch for slipping back
Adoption is not a straight line. AIHR warns that without ongoing attention, adoption stalls and people slowly fall back on workarounds, like spreadsheets outside the new system. McKinsey adds that when trust breaks down, people slide back, and leaders should go back a step rather than push harder.
So keep measuring after the first good month.
"Systems don't change organisations. People do." Zanani People Solutions
The post-implementation review
A few months after go-live, run a review. It answers one question: is the system doing what we bought it to do?
- Goals. Compare results with the goals in your business case.
- Tasks. Test key tasks from start to end, with real users. Leave, onboarding, payroll changes.
- Data. Check a sample of records for errors.
- Reports. Do leaders trust the reports? Do they use them?
- Setup. Do approvals and rules still fit how you work?
- People. What do employees and managers say? Where do they get stuck?
- Compliance. Can your EE and skills reports come from the system, not last-minute spreadsheets?
End with a short list of fixes, each with an owner and a due date.
Report to leaders in plain words
Leaders want three answers:
- Is it working?
- Where is it not working?
- What are we doing about it?
Keep the report brief and show the trend, not only this month. Name the next actions and who owns them.
Employee data is personal information under POPIA. Report trends and totals, not names, unless there is a clear need.
An example
Picture an HR lead at a retail chain, three months after go-live. Logins looked great. Leaders were happy.
Then she counted paper leave forms. Eight stores still sent them every week. She found the stores had one thing in common: managers had missed training. A session for those key managers, and a date when paper forms would stop, closed the gap within two months.
Try this on Monday
Count one "old way". Pick paper leave forms, side spreadsheets or emailed approvals. Count how many came in last week, by site. That number is your first adoption baseline, and it shows where to look first.
How Zanani helps
Zanani is an HR technology adoption partner and HR advisory. We help leaders see whether the system is being used as intended, and what to do next. Here is what that looks like for you:
- The right measures. Linked to the goals you bought the system for.
- A clear picture. Where adoption is strong, and where it is not.
- Reports leaders read. Brief, to the point, plain words, clear actions and accountability.
- Gaps closed. Training, communication, and process fixes where they are needed.
We work directly with organisations, and we also work with HR technology providers. Every organisation is different, so let's talk about how we do it.
FAQ
How do you measure HR software adoption?
Track task-based use, whether the work is better, data quality and whether old ways have stopped. Add a short employee pulse survey and report the trend monthly.
Are logins a good measure of adoption?
Not on their own. People can log in and still do the actual work on paper or in spreadsheets.
How do you test whether an HR system is working after implementation?
Run a post-implementation review a few months after go-live. Compare results with your business case, test key tasks end to end, check data and reports, and ask users.
How often should we report adoption?
Monthly works for most teams. Weekly can help in the first weeks after go-live.
What if we have no data yet?
Start now. Your first month becomes your baseline.
Need to show leaders the system is working? Email info@zanani.co.za or see what we do. We would love to talk.
FAQ: How do we support your digital journey?
