Grumpy people with self service technology
Simplicity is the key for successful Self-service technology deployment


How to ensure your self-service kiosk solution is favoured by all who use it...
Self service technology has been around us for decades and has been accepted well in simple form. Because the self service process was simple, us humans had no hang-ups with the process, and the self-service subject was more likely to be a whim. I am talking about simple vending machines for bars of chocolate etc.
You choose what you like, put the coins in the machine and pull out the choccy bar. No software or GUI to worry about.
Coins (pennies) were used for these self-service machines and sometimes they got stuck in the mechanism and your choccy bar could not be retrieved. (this problem spawned the expression - “when the penny drops” – after it having got stuck in the mechanism. The expression now has morphed into a euphemism for someone “finally understanding something” - maybe everyone knew that anyway?).
Sorry, I have digressed - back to the now...
Self-service has moved on dramatically from those simple vending machine days. What we want out of self service, or more aptly, what has been presented to us, offers us so much more. But, today’s self service user has to be much more tech savvy to be able to use current day self-service technology. This adds further complication. Needing to be aware of current technology to use self service kiosks is potentially leaving some people behind in their ability to engage with it, or as importantly, their wish to do so.
Coinage and notes are becoming less and less used in self service technology these days, most use debit/credit cards or phone / watch tap when payment is involved.
When self service technology gets a bad name:
Where coinage and notes are still used for self service payment (think NHS car parks etc) there is often a good deal of frustration involved in its use. This leads to self service technology getting a bad name which could easily be avoided. Asking the general public to use notes and coins at a kiosk to access public services creates difficulty at the point of use. Often there is a queue building up behind the user trying to use notes where the queue becomes frustrated for the wait involved.
This same bad name is equally applicable where paying at a kiosk requires an app on a mobile phone to be accessed. In popular places a huddle of people can often be seen, all accessing their mobile phones trying to pay for parking at a kiosk where an app has to be accessed. Generally, the air is blue with the conversations surrounding this kind of self service technology.
I recently witnessed an example of self service frustration at an NHS hospital, when collecting a member of my family. I joined the self service kiosk queue to pay for parking at the hospital. At the head of the queue was a middle aged man attempting his payment for the third time – using cash in the form of notes. The kiosk was out in the open experiencing all weathers and whilst the designer’s intention was to enable all methods of payment, it was clear that paying by notes was fiddly and not working well.
The man became frustrated at the “new self service technology” not working. The rest of the queue, including me also became frustrated because of the delay. Self service is supposed to be quick and easy, but so often it leads to delays and multiple frustrations.
Incidents like this show several important things for today’s self service world:
We all want immediate service.
But, we are not prepared to queue for long.
We are ok with Self service – as long as it works with minimal fuss: AND there is no learning curve to be done in the cold and rain.
Designers of self service technologies and software should put themselves in the shoes of the disinterested user for a reality check on what they present us:
The average kiosk user is not interested in the super software coding, nor the amazing styling of it. The user is only interested in the service, and they want it without fuss, drama, software training or technical hitches.
As self service technology offers increasingly more complex services, the designers have an increasingly difficult job to design solutions for the vast majority of users who do not want a technology lesson when accessing self service kiosks
In the parking instance I described above, the chances are that if the cash option had been removed, there would not have been a queue or frustration. The negative conversations in and around the queue towards the unfortunate user, the technology, the owner of the service and its designer would not have happened.
The waiting and difficult experiences get chalked up to a bad rap for public facing self service technology.
Keeping the process simple to understand and use is the cornerstone of well accepted self service technology.
Self service technology is not a personal technology like a phone is. The best reputation a kiosk gets is a neutral “it did the job OK” kind of reputation when all goes smoothly. But unfortunately, the lasting reputation will be the one surrounding the one with a long queue, the one with the confusing process, the one that was "out of order" or my example above.
The “take away” is that organisations that offer self service tech for their customers, really need to take stock of what they include in the design. technologies and processes must be simple in nature by not being fiddly, hard to understand, lengthy in process or needing specific app knowledge, just to offer simple services like parking or check-in or way finding