We use the word experience everywhere today. Customer experience. Employee experience. Travel experience. Dining experience. Digital experience. Somewhere along the way, we have also become very comfortable talking about managing all of these experiences.
But can an experience actually be managed?
Think about the last time you had a genuinely great experience. Perhaps it was at a hotel, a restaurant, on a flight, in a store, or simply in an interaction with another person. What made you describe it as great?
It probably wasn’t because everything merely worked as expected.
A clean hotel room is expected. Food arriving at the table is expected. A flight getting you safely to your destination is expected. A product doing what you bought it to do is expected. These things matter, of course. When they fail, we notice immediately. But when they work exactly as expected, we rarely walk away thinking, What an incredible experience.
Something else usually has to happen.
Perhaps someone anticipated what you needed before you asked. Something that could have been difficult became unexpectedly easy. Someone saved you time. Someone noticed something others normally wouldn’t. Maybe you were guided through something unfamiliar without having to struggle. Perhaps the service adapted to your situation rather than forcing you through the standard process.
Something changed for you.
And that distinction matters.
The experience happens somewhere else
The hotel can manage the room. The restaurant can manage the food and service. The airline can manage its operations. People can manage processes, environments, standards and support. All of these things can be designed and delivered extraordinarily well.
But the experience itself happens somewhere else.
It happens in the person.
Experience is what we feel as a consequence of all those things coming together.
That is why I increasingly find the phrase experience management slightly uncomfortable.
Experiences are felt. They are not managed.
What can be managed are the conditions from which an experience emerges.
Simply meeting an expectation does not automatically make something a great experience either.
Below expectation, something feels wrong. At expectation, things work as they should. Beyond expectation, effort may disappear. Time may be returned. Complexity may be removed. A need may be anticipated. Confidence may increase. Something may become easier or better than it reasonably needed to be.
That is when an experience begins to become noticeable.
And perhaps that is the point.
The service can be delivered. The conditions can be created. But the experience itself can only emerge from them.
Experience is an outcome.
And it has to be earned.
Why should Digital Experience be any different?
An employee does not come to work to experience technology.
They come to work — and increasingly, that work happens with and through technology.
A salesperson uses technology to sell. A developer uses it to build. An analyst uses it to analyse. A designer uses it to create. A manager uses it to communicate, collaborate and make decisions.
Technology has become inseparable from much of modern work.
But technology is still not the purpose of the work.
It is the instrument. Work is the purpose.
The laptop, applications, network, collaboration platforms, enterprise systems and, increasingly, AI are all part of that instrument.
So what should we reasonably expect from an instrument we use to do our work?
The laptop should work. The application should open. The network should connect. The meeting should not keep dropping. People should have access to the things they need. Applications should perform adequately. And when something does go wrong, support should help resolve it.
These things matter enormously.
But if all of them happen exactly as expected, should we really describe that as a great Digital Employee Experience?
Or has technology simply done what we expect it to do?
Perhaps the difference begins when technology does more than simply work.
It notices something that is going to slow me down and resolves it before I encounter it. It removes unnecessary steps from something I do every day. It helps me discover a capability I didn’t know existed. It recognises when I’m struggling with a new application and guides me through it. It helps me adopt a better way of working rather than simply giving me another tool and a training link.
Perhaps it automates something I have been doing manually for months. Perhaps it gives me relevant help instead of generic instructions. Perhaps it saves me twenty minutes on a task, prevents an interruption entirely, or allows me to accomplish something better, faster or with less effort than before.
Now something has changed for me.
Technology has not merely worked.
It has worked for me.
When technology does more than work
This is where I think the distinction becomes important.
There is a meaningful difference between technology that works, technology that helps, and technology that elevates what a person is capable of doing.
Technology that works meets the expected baseline. It is available, reliable, performant and supportable.
Technology that helps removes effort from the work. It guides, simplifies, prevents, assists and makes better ways of working easier to adopt.
Technology that elevates goes further. It anticipates, automates, gives time back and expands what someone is able to accomplish.
But experience isn’t the next stage in that sequence.
Experience is what the person feels as a consequence of it.
Technology can be managed. Performance can be managed. Availability and support can be managed. Devices and applications can be managed. Friction can be identified and removed. Adoption can be supported. Problems can be anticipated. Unnecessary work can be automated.
All of these shape the conditions in which someone works with technology.
But the experience itself still belongs to the employee.
Two people can interact with exactly the same technology and experience it differently. Their expectations are different. Their familiarity is different. Their work is different. Their confidence is different. Their context is different.
What feels effortless to one person can feel frustrating to another.
Experience is ultimately personal.
So perhaps the ambition of Digital Employee Experience should not be to manufacture delight or somehow directly “manage” how employees feel about technology.
Perhaps the ambition should be much more grounded.
Make technology extraordinarily reliable. Make support extraordinarily effective. Remove unnecessary friction. Help people adopt what has been given to them. Guide them when they need guidance. Anticipate problems where possible. Eliminate work they should never have needed to perform. Give them time back. Help them become more capable through the technology they use.
Do those things exceptionally well, and something important may happen.
Work may feel easier. The employee may feel less frustrated. More confident. More capable. Better supported. Perhaps, occasionally, even delighted.
But that judgement belongs to them.
Perhaps that is the distinction that matters most when we talk about Digital Employee Experience.
We can design the conditions.
We can measure them.
We can keep making them better.
Technology can work better, remove effort, anticipate needs, give time back and help people accomplish more.
But whether any of that became a better experience?
That belongs to the person who experienced it.
Technology can be managed.
Experience can only be felt.