We have spent years designing service desks that are efficient, ITIL-compliant, and resource-balanced.
None of that matters to Gen Z.
This generation will not sit in a queue. They will not log a ticket and wait patiently for a callback. They have grown up expecting real-time, self-service, app-native support that just works — because everything else in their life already does.
So why should corporate IT be the exception?
The questions they are actually asking
We are still measuring first-time fix rate while they are wondering why it broke in the first place. We are still offering knowledge articles while they are asking "why can't I just ask a chatbot?"
Or, even better — "why wasn't this prevented entirely?"
And they are right.
If we are honest, a lot of what we call service is just cleaning up yesterday's mess with today's labour. Gen Z expect that mess to be designed out, not handed off. They have been trained by a decade of consumer technology where the system anticipates their need before they have to ask. The Spotify algorithm. The Uber map. The TikTok feed. The Apple do not disturb while driving. None of these wait for a ticket.
This is not a "young people are impatient" argument
I want to be clear about that. The cliché reading of this is that Gen Z are entitled, or that they have shorter attention spans, or that they cannot cope with a queue. That is the wrong reading. They have simply calibrated their expectations to a digital experience that is much, much better than the one most enterprises offer their users.
Older generations adapted to bad enterprise IT because they had to. They came up in an era when enterprise IT was the most advanced computing they encountered. So when something was clunky, they put up with it. When something was slow, they accepted it. When something asked them to translate their problem into a category, they translated.
Gen Z came up the other way around. The most advanced computing they encounter is the consumer technology they grew up with. Enterprise IT is the regression. They are not impatient. They are calibrated. The bar got moved while we were not paying attention.
The challenge for service leaders
We cannot expect new talent to adapt to outdated thinking. We need to reimagine the service experience around their expectations, not our legacy processes.
That is uncomfortable, because it means a lot of the things we are proud of need to be questioned. The portal we spent two years rolling out. The category taxonomy we have refined for a decade. The SLA structure we benchmark against. The first-time-fix metric we celebrate. None of these things matter to a user who measures support against the apps in their pocket.
What matters is — did the system anticipate the need? Did it remove uncertainty? Did it return control? Did it talk to me like a human? Did it close the loop without me having to chase?
If the answer to any of those is no, the service has failed. It does not matter how green the SLA dashboard is.
Why this actually matters
The real risk is not poor satisfaction scores. Bad scores are recoverable. Bad scores are useful. They tell you something is wrong. The real risk is irrelevance.
An IT function that Gen Z routes around is an IT function whose budget gets routed around with it. They will use shadow tools. They will buy SaaS on personal cards and expense it. They will solve their own problems via a generative AI assistant before they have logged a single ticket. The service desk will keep producing the same statistics it always has — a respectable backlog, a healthy first-time fix rate, a satisfied senior leadership — while the actual work happens somewhere else entirely.
That is not a satisfaction problem. That is the slow exit of the function from relevance to the business it was built to serve.
The service desks that will matter in five years are the ones who saw this coming and redesigned around it. Not the ones who optimised the dashboard.