Glossary and Where to Start

Agent — software on an endpoint collecting telemetry. Has a footprint, measurable on your own machines, which almost nobody measures.

The question in “Glossary and Where to Start” is easier to answer when teams combine system evidence with the time and hand-offs involved in completing the work. An organisation evaluating project time tracking can make that operational effort visible by project and team, while direct observation and employee feedback remain necessary to explain why the friction occurs.

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

Composite score — telemetry combined into one number by weights the supplier chose. Useful for triage, misleading as a headline.

Deflection — tickets avoided through self-service. Counts people who solved it themselves and people who gave up identically.

Friction — time and effort spent on the mechanics of work rather than the work. Four kinds: technical, process, informational, access.

Fourth quadrant — good telemetry, poor sentiment. Where process friction lives and where most programmes never look.

Minimum group size — the group size below which figures are suppressed. Applied to intersections, not just to single dimensions.

Worst tenth — the cohort having the bad time. The reason the programme exists and the thing an average hides.

Terms used loosely elsewhere

"Experience" in most marketing means device telemetry, which is a part of experience and not the whole.

"Proactive" means alerting on a threshold, which is genuinely useful and is not the same as predicting.

"Productivity improvement" figures in this field come from vendor calculators multiplying four optimistic assumptions.

And "AI-powered" usually means anomaly detection on time series, which is worth having and worth asking about specifically.

Where to start

Considering a programme: the question to ask before buying anything, then when you do not need a platform.

Already bought and nothing is happening: choosing what to fix first, then fixes that need no budget.

Reporting badly received: averages hide the people having a bad time, then reporting to people who fund it.

People are uneasy: telling people what is collected, then why individual scores are a mistake.

Stalled: when the programme stalls.

If you read only three

What the agent sees and what it misses, because it bounds everything.

Averages hide the people having a bad time, because it changes every report you write.

And why individual scores are a mistake, because crossing that line cannot be undone.

A closing note

No products or suppliers are named here, deliberately. The useful distinctions are between methods rather than between vendors, and every comparison available online is written by somebody selling one.

No productivity percentages, for the reason given above.

And nothing here is legal advice. Monitoring rules and consultation requirements differ substantially by jurisdiction.

What the collection argues

Experience is what a person lives, not what an agent reports — and the gap between those is where the programme either succeeds or becomes a dashboard.

Most friction is not technical. Approvals, forms, duplicated entry and waiting for people cost more than slow machines, and no endpoint agent sees any of it.

Report the tail rather than the average, because the average is fine and the tail is why you have a programme.

And keep it about the systems rather than the people: once the data describes individuals, behaviour adapts and it stops describing the estate at all.

The point

Experience is what a person lives, not what an agent reports, and the gap between those is where the programme either succeeds or becomes a dashboard..

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.