A few years ago, IT departments were really good at one thing: counting tickets. Resolution time, ticket volume, first-contact resolution rate. These numbers were clean, trackable, reportable. They made sense in meetings. They answered the question: how much work is IT doing?
Now something different is happening. Organizations are still tracking those metrics, sure, but they're becoming almost secondary. The real conversation has shifted to something that's much harder to measure and infinitely more awkward to admit you weren't measuring before: is IT actually making the business work better?
This isn't a sudden reversal. It's more like a slow realization that got louder during the pandemic when everyone had to work from somewhere else suddenly. When your entire workforce depends on whether a person can log in and get to the tools they need to do their job, you stop caring quite so much about how many tickets the IT team closed that week. You care about whether your people can actually work.
The shift reveals something uncomfortable. IT has been optimizing for throughput while the business was optimizing for outcomes. A ticket got closed fast? Great. But did it solve the actual problem the person needed solved? Did it get resolved the first time, or did the person call back three days later with the same issue? And crucially, did anyone notice that the person had stopped being able to do their job entirely while waiting for resolution?
So now you're seeing IT departments start to think about things like: How long was someone actually unable to work? Not time-to-resolution from IT's perspective, but time-to-productivity from the user's perspective. These are different things. One measures how fast IT worked. The other measures how much business value was lost.
There's also this thing where organizations are starting to care about adoption metrics and user satisfaction in ways they didn't before. Whether people are actually using the systems IT spent money deploying. Whether they're using them well, or whether they've just created shadow IT workarounds because the official tool doesn't work for them. Whether a Teams implementation actually meant people stopped using five different email systems, or just added Teams on top of five different email systems.
This makes IT leadership nervous for obvious reasons. Ticket metrics are something IT controls. User satisfaction? Adoption rates? Time-to-actual-productivity? Those things involve a lot of variables that aren't IT's fault. The system might be perfect but nobody uses it because the change management was terrible. The infrastructure is solid but the software on top is confusing. IT did everything right but the organization isn't ready to use what IT built.
But that nervousness is actually the point. It means the question shifted from "is IT working hard" to "is IT making things work." And those are genuinely different questions. One is about effort. The other is about impact.
The organizations that are moving into this newer way of thinking aren't necessarily doing it because they read an article about it. They're doing it because the old metrics stopped being useful. You can have incredibly fast ticket resolution and a user base that's frustrated, dissatisfied, and cobbling together workarounds. You can look great on a dashboard while people are quietly doing their actual work somewhere else.
It's an uncomfortable shift because it means IT success and business success have to actually align. There's no more room for them to be measuring different things and both feeling successful. And that's probably not a bad thing, even if it does make the scorecard more complicated.