Common Failures, Listed

At the start

Buying before knowing the question. Signal: a platform in search of a use. Fix: read a hundred tickets and walk one process, now.

The question in “Common Failures, Listed” is easier to answer when teams combine system evidence with the time and hand-offs involved in completing the work. An organisation evaluating the official explanation 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.

No owner with allocated time. Signal: DEX is somebody's fifth priority. Fix: half a role, or do not start.

Deployed without telling people. Signal: the first they knew was an agent appearing. Fix: not available retrospectively.

In the measurement

Telemetry only. Signal: nothing in the data happens outside a device. Fix: one survey question and the ticket free text.

Composite score as the headline. Signal: reports lead with a number out of ten. Fix: name the two components driving it.

Averages without tails. Signal: a single figure per measure. Fix: median and worst tenth, always.

No baseline. Signal: the first month's data was treated as findings. Fix: six weeks before concluding anything.

In the use

Individual or team views. Signal: a manager has seen a ranking. Fix: disable the capability, not just the access.

Nothing fixed. Signal: a dashboard, reported monthly, unchanged. Fix: pick the highest time-cost, lowest-effort item and do it this month.

No before figure. Signal: improvements claimed, not demonstrated. Fix: measure first, change one thing.

Around the edges

Vendor value calculator in the business case. Signal: a number with four optimistic assumptions. Fix: state time saved and let finance supply the rate.

Stalled at the technical tier. Signal: a year of progress, then nothing. Fix: widen the mandate, deepen technically, or embed and close.

The pattern

Seven of the twelve are fixed in under a month.

Three are prevented only before deployment: the question, the owner, and telling people.

And two — deploying without telling people, and a manager seeing a ranking — are not really recoverable, because both are about trust rather than data.

The order to fix them

If you do one thing: read a hundred tickets.

If two: report median and worst tenth.

If three: fix something and measure it.

Those three cost about a week between them and address most of the twelve.

What to check

Which of the twelve do you have?

Are any of them the two that cannot be undone?

Which is cheapest to fix?

And has anything from your last review actually changed?

The point

Two of the twelve failures are not recoverable: deploying without telling people, and a manager seeing a ranking of their team..

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.