Why Individual Scores Are a Mistake

Most platforms can produce a score per user. Several present it prominently. It is the single feature most likely to end a programme.

The measurement in “Why Individual Scores Are a Mistake” should connect system evidence with the time required to complete real work, without turning one metric into a judgement about a person. Teams considering the complete guide can compare workload and project time at an appropriate group level, but should interpret the pattern alongside surveys, walkthroughs and the people doing the task.

For an independent benchmark, compare this approach with ICO employment information guidance; the useful test is whether the evidence remains proportionate, accessible and understandable to the people whose work is being measured.

What the score actually measures

The person's device: its age, specification, configuration and location.

The applications their role requires.

The network they connect from.

None of which they chose. A low score describes an allocation decision made by the organisation.

How it will be read

As describing the person.

This is not a risk, it is what happens. A list of named people with numbers beside them is read as a ranking of people, whatever the column header says.

And once one manager has used it that way, the programme is a monitoring system in everybody's mind.

The specific harms

People with older hardware, in worse offices, or in roles using heavy software score worse through no action of their own.

Disabled colleagues using assistive technology frequently score worse, because the measures were not designed around them — its own note covers this.

Remote workers on domestic connections score worse than office workers.

Each of those is a fairness problem dressed as a measurement.

What to do instead

Score cohorts: device model, site, application set, role type.

That is where the actionable finding is anyway: the fix is to a cohort, not to a person.

Finding the worst-affected individuals to help them is legitimate — but the output of that is a job ticket for a device swap, not a scoreboard.

The helping case, done properly

You do want to find the hundred people having the worst time.

Do it as an operational list that goes to whoever fixes things, not as a report that goes to managers.

Different audience, different retention, different access.

And say so in the programme's stated purpose, so the distinction is on record before anybody asks.

Turning it off

If your platform has individual views, consider disabling them rather than relying on access control.

A feature that exists will eventually be requested by somebody senior enough to get it.

Removing the capability is a stronger position than policing its use, and it is a configuration decision available at deployment.

What to say when asked

"The score measures the equipment and the environment, not the person. We report cohorts, and we use the individual list to send engineers rather than to send reports."

Said once, early, it holds. Said after a manager has already seen a ranking, it does not.

What to check

Does your platform produce per-user scores, and are they visible to anybody?

Could they be disabled?

Is the distinction between an operational list and a management report written anywhere?

And has any manager ever seen a ranking of their people?

The point

A per-person score describes equipment and circumstances the person did not choose, and will be read as describing the person.

That is not a risk; it is what happens.

Underlying all of this

Everything in this collection reduces to four habits: find the friction cheaply before buying anything, fix what needs no budget first, report the worst tenth rather than the average, and keep the data about systems rather than about people. None requires a better platform, and a programme doing all four changes more than one twice its size.

The recurring pattern

The recurring pattern across every section here is the same: the measurable is mistaken for the important. Device health stands in for experience, ticket categories for causes, a composite score for a finding. Each substitution is convenient, each produces confident decisions on thin ground, and each is corrected by going and looking at the thing itself.