Archives for "Banking Applications"

Nowadays, we can see an increasing usage of touch screen-based ‘Kiosks’ – the self-service mechanism at several places, including Bank ATMs, Shopping Malls and such other places where an assisted system is required but need to cater a large amount of users in an unorganized, non-formal way.

Kiosks are mean to be easy for all types of end-users, even those who may have very minimal experience with computers, non-tech savvy users who may be hardly interacting with computers. Also, the target end-users are expected to spend very less time at such kiosks to perform certain quick-to-do tasks such as cash withdrawal, balance statement inquiry, shopping mall information like direction for an x store located on some x floor.

For such users, ‘especially non-banking application users’, the time span to be spent on a kiosk will be minimal. And, if they are not able to learn using the kiosk and getting the information they want in around 15-25 seconds, they might turn away from the application (kiosk).

To avoid such issues, one needs to understand the underlying usability and accessibility principles for success in kiosk application development scenario.

Some of the important things which will help you achieve success in your kiosk applications are:
1. Understanding the target users and the environment they are supposed to use this application.
2. Usable interface, designed to suit the end-users / Application design
3. Reliable hardware (displays, ergonomically designed cabinet / hardware)

In this article, we will discuss about understanding the target users. Consider following aspects while designing usable interface for Kiosks / Touch screen based applications:

> End-users are not trained for the application interface: When kiosks are developed, end-users being general public can not be trained at such a large scale, considering the practicality and the viability from business perspectives. Kiosks are of “self-help, learn quickly” kind of applications. Generally, kiosks are set up in places where there is no possibility to train end-users about how to use the Kiosk application.

> Kiosk is an assistive mechanism and can be secondary for people who are late technology adopters or not willing to use such applications [except banking ATM kiosks – being the easiest way for quick-to-do banking tasks such as cash withdrawals and is a must for such users]: There are users who are not willing to use kiosk because of their bad past experiences or fear in the mind about using the technology being late technology adopters. For such users, Kiosk must attract their attention, must be engaging & should not frustrate the user with its complexity. And, most importantly, it must deliver the information.

> Even a small reason can turn them off: Any small flaw in the software / hardware design can make users feel bad about the kiosk and can have a negative effect on the usage level. For example, an action button, if not mapped properly for the action or have a bad “affordance”* can damage the experience and turn them off.  [*Affordance: a situation where an object's sensory characteristics intuitively imply its functionality and use. - Ref: UsabilityFirst ]

> End users must be satisfied: Else, they will go away from the product and may not use it again, due to the bad experience they had while using it first time. (In case of important services like banking ATMs, they will have to come back but will have an adverse effect about the respective bank’s reputation as people may spread negative message about the applications (such as “this bank’s ATM is really tough to use! I am not getting the things quickly…there are too many options to choose from…there are several actions that take me to the action which I desire to do but don’t want to waste so much of time.” And this leads to bad reputation for the x company.

Good software interface is a key to the success in Kiosk-based applications. We will discuss more factors like “An Effective interface for Kiosk – Success Factor” in the continuing post.