The awkward board question nobody wants
I once sat in a steering committee where the CIO asked a simple question:
“Is the portal better now?”
The room went quiet. IT talked about the release. HR talked about comms. Someone mentioned a new homepage layout. Nobody could answer the question that mattered: did it change behaviour?
That’s the moment most ServiceNow programmes hit the same wall. You do good work, but you can’t prove it. So the budget gets squeezed, priorities shift, and the portal slowly becomes that system people avoid.
A UX scorecard fixes that. Not because it’s fancy, but because it gives leaders something they can trust.
The real pain point leaders talk about online
If you spend ten minutes on Reddit or IT forums, you’ll see the same complaint dressed up in different words:
- We bought ServiceNow but people still email the service desk.
- Search is useless.
- Forms are heavy.
- Nobody uses the portal unless we force them.
This is not a platform problem. It’s an engagement problem. And engagement is measurable.
What a UX scorecard is (in plain English)
A UX scorecard is a short, repeatable way to track whether your Employee Center is getting easier to use over time.
It keeps you honest, also keeps vendors honest and answers questions leaders care about:
- Are people using the portal more?
- Are they completing tasks faster?
- Are tickets dropping because users self-serve?
- Are we creating value, or just changing the wallpaper?
The metrics that matter (and the ones to stop obsessing over)
1) Adoption rate, but the right kind
Logins are not adoption. Real adoption is repeat behaviour. Track:
- Unique users who completed a task
- Repeat users week to week
- Channel shift (less email, less Teams pings, more portal)
2) Time to task
This is where ROI hides. Measure how long it takes to:
- find a policy
- submit a request
- complete a common workflow
Then cut it. Even small reductions multiply across thousands of employees.
3) Deflection rate
If the portal is working, tickets should reduce for basic queries. Track:
- searches that end in “no ticket created”
- knowledge article views before ticket submission
- top reasons users still raise tickets
Deflection is not just cost saving. It’s trust.
4) Search success
Search is your portal’s front door. If it fails, everything fails. Track:
- top search terms with zero results
- click-through rate from results
- time spent searching before users give up
5) Accessibility
WCAG AA is not a nice-to-have. It protects usability for everyone and reduces risk. Track:
- contrast issues
- font sizing
- keyboard navigation
- labels and tags on form fields
If senior leaders want “value for money”, accessibility is part of that value.
How to build a scorecard without making it a bureaucratic monster
1: Keep it to one page
- A scorecard should fit on one slide.
- Pick 6 to 10 measures. That’s it.
2: Set a baseline
- Run the numbers now. Don’t wait for the next release.
- Your baseline becomes your proof.
3: Review monthly, improve quarterly
- Monthly review keeps momentum. Quarterly improvements keep delivery sane.
- This is how you avoid big-bang redesigns that never land.
4: Tie each improvement to a metric
Every backlog item should answer:
- What will this improve, and how will we measure it?
- That’s how you stop wasting effort on things that look impressive but change nothing.
What this does for HR, IT, and Finance
- HR leaders get fewer interruptions, faster employee support, and clearer comms impact.
- IT leaders get fewer low-value tickets and more time for high-impact work.
- Finance leaders get proof. Real numbers tied to usage, efficiency, and reduced cost to serve.
A UX scorecard gives everyone a shared language that is not based on opinion.
The Monochrome point of view (without the brag)
The best Employee Centers don’t win because they look pretty. They win because they change behaviour.
A UX scorecard is how you keep that behaviour change going, release after release, even as teams rotate, vendors change, and new modules arrive.
If you want ServiceNow to become the easiest way to get work done, measurement is the discipline that gets you there.
Want the scorecard template?
This blog is part of our ServiceNow UX Guide, built for leaders who want adoption, deflection, and time-to-task improvements they can prove.
Not in the mood to figure it out alone? Download the full ServiceNow UX Guide and get the complete set of practical tips.
Quick answers for busy leaders
Q: What should a ServiceNow UX scorecard include?
A: Adoption, time to task, deflection, search success, and accessibility are the core. Keep it simple and repeatable.
Q: How often should we review UX metrics?
A: Review monthly, then deliver improvements quarterly. That balance keeps progress steady without creating chaos.