Why Device Experience Is the Thing That Actually Matters Now
I’ve been doing this since 2005. I cut my teeth on deskside, Wintel and Active Directory work, and somewhere along the way I ended up as an architect drinking far too much coffee and eating scones. In that time I’ve watched the way we manage end user estates change completely, and I want to talk about where it has landed: device experience. Not the hardware. Not the build. The experience the person sitting in front of the machine actually has.
From big bang projects to never being finished
When I started, an estate refresh was a Project with a capital P. You’d kick off a Windows migration, or a hardware rollout, and it had a start date, an end date, a budget, a steering committee and a war room. Think back to the late 2000s, the XP to Windows 7 era. You’d spend the guts of two years planning, packaging applications, testing, piloting and then grinding through site after site. When it was done, everyone breathed out, the project team disbanded, and the estate was left to slowly drift out of date until the next big project came along three or four years later.
That model made sense at the time. Hardware was expensive, operating systems shipped every few years, and the cost of touching a device was high. So you batched everything up into one painful push and tried not to do it again for as long as possible.
Then somewhere around the early 2010s that started to fall apart. A few things happened at once. Windows 10 arrived with the “Windows as a service” idea, so the OS stopped being a thing you replaced and became a thing you maintained. Cloud management came along. Application vendors moved to faster release cycles. Suddenly the idea of an estate sitting frozen for three years between projects was not just lazy, it was a security and compatibility risk. You couldn’t let a fleet go stale.
That’s where evergreening came from. Instead of a project that ends, you run a continuous process that keeps the estate current all the time. Patches, feature updates, driver updates, application versions, all flowing through in a steady stream rather than one big shove every few years. The project team never really disbands now. It becomes an operations function. We stopped asking “when is the migration finished” and started asking “how do we keep this thing healthy forever.”
Evergreen solved one problem and exposed another
Here’s the bit that took the industry a while to admit. Once you’ve reached a genuine evergreen state, currency stops being the interesting question. The machines are patched. The OS is current. The hardware is within its refresh window. By the old scorecard, everything is green.
And yet users are still ringing the service desk saying their laptop is slow.
That was the penny-drop moment for a lot of us. When you’ve fixed currency, the problems that are left aren’t about whether the device is up to date. They’re about how the whole thing feels to use. An application that takes ninety seconds to open. A login that crawls because of too many GPOs and a bloated startup. A line-of-business app that hangs every afternoon when everyone hits it at once. A laptop that’s technically within spec but spends half its life with the disk pinned at 100% because of some background agent nobody remembered installing.
None of that shows up on a currency dashboard. The device is compliant, patched and current, and the person using it is still miserable. We’d spent a decade getting really good at measuring the wrong thing. We could tell you the patch level of every machine in the estate to two decimal places, but we couldn’t tell you whether people could actually get their work done.
That’s device experience. It’s the gap between “the device meets the standard” and “the device is a pleasure, or at least not a pain, to use.” And it turns out that gap is where most of the real cost lives, in lost productivity, in support tickets, in people quietly buying their own tools because the corporate ones are too slow.
You can’t fix what you can’t see
The reason we couldn’t manage experience for so long is simple. We had no telemetry for it. We had asset data, patch compliance, maybe some SCCM reporting, but nothing that told us what the device felt like from the user’s chair. We were flying blind and relying on people to ring up and complain, which is the worst possible feedback loop. For every person who logs a ticket about a slow boot, there are ten who just put up with it and think IT is useless.
This is where digital employee experience tooling changed the game, and Nexthink is the one most people will have come across, so I’ll use it as the example. The category is broader than any one vendor, but the idea is the same across all of them.
What these tools do is put a lightweight agent on the endpoint that constantly measures the things that actually affect experience. Boot and login times. Application crashes and hangs. CPU, memory and disk pressure. Network quality. Application responsiveness. Then they roll all of that up into a score so you can see, across the whole estate, where experience is good and where it’s falling apart. Suddenly you’re not guessing. You can see that the finance team’s machines all take four minutes to log in, or that a particular app version is crashing on a specific driver, or that a recent change made boot times worse across a whole site.
The other half of the value, and honestly the part that wins people over fastest, is remote actions. It’s one thing to spot that two hundred machines have a runaway process eating their CPU. It’s another to fix it without touching any of them. With remote actions you can push a script, clear the problem, restart a service or reset a misbehaving component across the estate in one go. You can even go proactive and trigger a fix automatically the moment the telemetry sees the problem, so it’s sorted before the user notices. That’s the quick-win stuff that pays for the tooling on its own. The first time you close out a whole class of tickets with one remote action instead of two hundred desk visits, the business case writes itself.
Refreshing on a calendar versus refreshing on reality
Here’s where all of this comes together, and it’s a question I keep running into: how do you decide when to replace a device?
The traditional answer is a schedule. Every machine gets refreshed on a three or four year cycle, regardless. It’s simple, it’s predictable, finance loves it because they can plan the spend. But it’s also blunt. You end up replacing perfectly good machines that someone barely uses, while the heavy user with the genuinely struggling laptop has to wait until their number comes up. You’re spending capital on the calendar rather than on need.
Once you’ve got experience telemetry, you can do something smarter. Instead of refreshing on age, you refresh on experience. If the data shows a device is delivering a poor experience, high resource pressure, slow boots, constant crashes, and it can’t be fixed remotely, that’s a machine that needs replacing now, whether it’s two years old or four. Equally, a three-year-old machine that’s scoring well and keeping its user happy can stay in service longer. You’re letting the actual experience drive the decision, not an arbitrary date.
I’m not going to pretend it’s all or nothing. The honest answer for most organisations is a blend. Keep a baseline refresh cycle so the estate never gets truly ancient and so finance has something to plan around, but layer experience data on top so you can pull problem devices forward and let healthy ones run on. You get the predictability of a schedule and the targeting of experience-based decisions. More importantly, you stop wasting money refreshing machines that didn’t need it and start spending it where it actually improves someone’s day.
Where this leaves us
The job changed. It used to be about getting the estate current and then defending that state until the next project. Now currency is table stakes, the thing you’re expected to keep ticking over in the background, and the real work is making sure the experience is good. That means measuring what the user actually feels, fixing it fast and ideally before they notice, and making decisions, including spending decisions, based on real data rather than a date in a spreadsheet.
If you’ve got your estate to evergreen and you’re still drowning in “my machine is slow” tickets, that’s your sign. Currency was never the finish line. Experience is.
You must be logged in to post a comment.