What I've learned

A ticket can close and trust can still be lost.

A service desk can hit every SLA and still leave customers feeling unheard. The gap between resolved and felt resolved is where improvement work should actually start.

Connect with Clare
Follow the thread to see where the work starts, what changes, and how the evidence becomes useful.

How service improves, in four stages:

01 Notice02 Connect03 Change04 Prove

What I've learned

Tickets move, but ownership is often still unclear. Customers get updates that don't answer the question they actually asked. Teams can see what's broken, but the evidence is scattered across systems no one reads together.

Common mistakes

Measuring activity instead of experience — ticket volume, response time, resolution time — without ever asking whether the customer felt looked after. Volume and speed can both look healthy while trust quietly erodes.

Practical approaches

Combine how people feel with how much time they believe they lost, then look at the reasons behind that experience: escalation patterns, handover quality, knowledge gaps, and where communication breaks down. A better service desk is easier for customers to trust and easier for teams to run — usually at the same time.

See the evidence behind this thinking
Try the calculator

See what recurring IT issues are really costing you.

Enter monthly tickets and average resolution time for each issue type to see a ranked breakdown — useful evidence for prioritising the IT roadmap.

Open the IT lost time calculator
Selected Briefings

Read the thinking behind the work.

Explore every Briefing ↗
Connect with Clare

Continue the service conversation.

For senior leadership opportunities, transformation programmes, industry collaboration, and conversations about improving service.

hi@clarelangley.com