Working With the Service Desk

The service desk holds the richest data and the best informed people. A DEX programme that arrives as an auditor gets neither.

The friction described in “Working With the Service Desk” becomes easier to prioritise when the team can separate active work from waiting and repeated handling. An organisation evaluating this supporting guide can record time against the affected workflow and compare the effort before and after a change, while ticket and device records remain the evidence of the technical event itself.

For an independent benchmark, compare this approach with Atlassian IT service management resources; the useful test is whether the evidence remains proportionate, accessible and understandable to the people whose work is being measured.

What they have

Years of ticket detail.

A precise sense of what is broken and what people complain about.

Direct contact with the affected population.

And the ability to validate or demolish any finding in an afternoon.

The way to start

Ask what they would fix if somebody would let them.

An hour with three experienced agents produces a better problem list than a quarter of analysis, and it establishes the programme as something that might help rather than something that measures them.

The mistake that ends it

Arriving with figures that imply the desk is not doing its job.

Ticket volume, repeat contacts and reopen rates all look like service desk performance measures and will be read that way.

Frame them explicitly as measures of the estate, and say so first, before showing anything.

Where the interests align

Both want fewer tickets.

The desk wants them deflected or automated; the programme wants the cause removed.

Cause removal is better for the desk too, and saying that early is the basis of the alliance.

The monthly session

The practical mechanism: once a month, the top recurring causes go from the desk to whoever owns them.

The programme provides the sizing and the routing; the desk provides the material.

An hour, and it is the main engine of a working programme.

What to give back

Tell them what was fixed because they reported it.

Share the data you build, including the segments they cannot see.

And credit them publicly, because the alternative is a programme that takes their findings and reports them upward as its own, which is noticed immediately.

The automation tension

Deflection targets can conflict with cause removal: a self-service article for the top ticket type reduces volume and leaves the cause.

Both are legitimate. Agree which is being pursued for which categories, rather than letting the two efforts work past each other.

What to avoid

Going around them to their users.

Publishing ticket figures without context.

And treating the desk as a data source rather than as a participant, which is the posture that produces technically correct and politically dead programmes.

What to check

Have you asked the agents what they would fix?

Is there a monthly route from the desk to cause owners?

Have you told them what was fixed because of them?

And do your ticket measures read as estate measures or as performance measures?

The point

The service desk holds the richest data and the best-informed people.

Arrive asking what they would fix, not showing figures that read as their performance.

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.