…such as the customer experience of fixing broken IT systems.
The service industry evolved long ago, around the time when innovative services began targeting top-tier clients willing to pay premium prices—think airlines, banking, and hotels. In those sectors, delighting customers by delivering an outstanding experience was a legitimate strategy: it helped grow the market, improve loyalty, and outperform the competition.
In the 1990s, service logic started to be adopted inside organizations, particularly in IT management best practices. This is when the concept of the “internal customer” was introduced—without much critical thought. Was the purpose of the internal IT department really to deliver a great experience, sell more services, or increase loyalty?
Practices like customer satisfaction surveys, experience analysis, and NPS were adopted. XLAs and EX metrics were introduced, all based on the flawed assumption that pleasing the ‘customer’ is the primary goal of internal IT.
Consider two companies:
A/ IT follows best practices, measures CSAT after every interaction, and runs a well-staffed service desk that promptly resolves every ticket. They constantly strive to improve metrics like Mean Time to Restore Service (MTRS), and their cost per incident is below the industry benchmark. Their volume of tickets is around 1 ticket per user per month.
They are proud of how good their IT support is.
B/ IT is focused primarily on creating frictionless IT. They work to eliminate technical debt and don’t measure CSAT, except for a brief annual survey on collaboration experience. Their MTRS is inconsistent because every outage triggers deep analysis and long-term fixes. They receive about 1 ticket per user every 3 months—three times fewer than Company A. Their resolution costs are higher than average.
From a support perspective, IT is mostly invisible. Their service desk is small, they allow multiple points of contact, and they know some minor issues never become tickets.
Which IT department is better? Which one contributes more to business outcomes?
This simplified scenario highlights the problem of positioning IT as a customer- and experience-centric function. In the 1990s, this mindset had merit—technology was often unreliable, and much of IT’s energy was spent fixing broken hardware or software. But today, we live in a different era: frictionless IT, automation, and the elimination of routine or algorithmic tasks are the true goals of IT.
Yet many consultants haven’t noticed this shift. They still operate within a world that no longer exists.
Metrics should move away from reactive processes (like service desks, incidents, and requests) and toward more meaningful indicators such as resilience, automation, and the absence of bad outcomes.
And please—stop calling your colleagues “customers.” They’re not, and never were.
As Ennius said: “The good is mostly in the absence of bad.”
Metrics that measure the ‚absence of bad‘ are the right focus for modern IT management—such as overall IT quality, collaboration quality, innovation index, and productivity indicators.