Every dashboard is green. The lab is cold and the portal is down.
· 3 min read
In brief
When every dashboard is green but users are suffering, the problem is a watermelon that grows from measuring the wrong things in the wrong way. The cure is to measure what researchers, students and staff actually experience, and to act on it.
- University IT and Estates teams know the pattern: tickets close within target and the maintenance calendar is green, while a researcher cannot log in before a grant deadline and a lab sits at fourteen degrees.
- Stop reporting availability as a percentage. Ninety-nine per cent sounds impressive, but a few minutes of downtime during clearing, an exam upload or a funder submission is not a rounding error; report the minutes users feel, at the times that matter.
- Fix the satisfaction survey. A 1 to 5 scale invites a lazy mid-point and averaging produces a bland number; work cited with the University of Surrey showed averaging to be invalid. Use a forced 1 to 4 scale, ask for reasons behind low scores and report the percentage at each score.
- Audit your reports. Sansbury describes a contact centre report thicker than two textbooks that the receiving Finance Director did nothing with; if you suspect nobody reads a report, stop producing it for a month and see who notices.
- Keep users informed. In Sansbury's ferry story, a single announcement would have kept queuing passengers calm; consumers dislike delays but hate not being kept informed far more.
Continue reading on the Exchange
Join or sign in to read the complete article, explore the full knowledge library and record your CPD.
Founder membership is free for life
More from John Sansbury
Available to members.
Related articles
How should the service desk handle a Microsoft 365 outage it cannot fix?
Treat a supplier cloud outage as your own major incident: log it once, tell people early on a channel that still works, update on a rhythm and review your dependency afterwards.

Deploying AI is the easy part: who runs it once it goes live?
Only a third of large enterprises have met the business case for their main AI programme. New research points to a gap in who runs AI after launch, and what leaders can do.
How do I compare help desk tool pricing before rolling it out across several departments?
Compare help desk tools on a full year's cost for your real agents, approvers and requesters in every department, not on the headline monthly price.
Turning 'not helpful' into a fix
'Not helpful' is free, honest feedback, and most of it goes nowhere. Turn that click into a fix.
When the author leaves, who owns the article?
Articles keep being read after their authors move on. Make sure the care for them does not leave too.
Test after every change, or find out from users
Knowledge changes fail quietly. A short, repeatable test after every change finds the problem before your users do.
