A lot of changes have been happening thanks to a continuously evolving FinTech industry, but many changes are yet to come. Understanding what customers want and need is very crucial for every business, and finance is no exception. There has to be a clear understanding of the things that either cause customers headaches or deliver pleasure when creating a user-centered financial service.
What defines whether a service is user-centered
For starters, every new user should be able to quickly understand how to do something with the service and how to navigate through it. If the user can do that, and their first interaction is impressive enough, the user will return to perform it again and again. Therefore, the first impression is critical.
Second, how fast can the user perform frequently used operations? With banking products, the most commonly used features are checking account balances, top-up accounts and transferring money. If any of these features take too long or require too much effort, users will probably seek a better solution.
Third, how many errors does a user make in performing any action? In a perfect scenario, the user should be able to go through the step-by-step process without thinking twice about what needs to be done. Although it is impossible to eliminate all mistakes, we can ensure that the user understands in what format information should be entered, what kind of information and don't miss any mandatory input fields.
Last but not least, how enjoyable is it to use this product? Financial products should be not only functional but also appealing because users don't enjoy using services that look too boring or outdated.
How to explore users
There are dozens of research methods available, but from our experience to create a user-centered financial product, five key research methods should be highlighted. These methods provide the best way to get main insights from your end users.
1. USER PERSONAS
To create a user-centered product, it is important to understand who the end users are. Only when we have an understanding of what they need, their behavioral habits and pain points it is possible to create the perfect product for them.
User personas are invented characters with a precise description of its age, gender, occupation, location, income, daily life, thoughts and other details. Each user persona represents a specific type of end-user that can be defined by polls, stakeholder interviews, desk research and field research.
For example, user personas in one mobile banking app can be a young student who works a part-time job, a mother of two who takes care of her household and a businessman who has to check personal finances as well as company finances.
For each type of user, the main functions of why and how they want to use this mobile banking app differs. With user personas, it is possible to create an empathy map - what those end-users feel and think, what difficulties they face in their daily life and their priorities in what they would like to do with their mobile banking app.
2. USER INTERVIEW
User interviews are one of the commonly used research methods to understand users' motivations, pain points, feelings, daily routines and behavior while using various financial products. It can be performed at any stage of a product’s development.
In the early stages, prior to product launch, user interviews will provide insight into whether the upcoming product will be used as planned in the users’ eyes. For an existing product, it will help to understand what difficulties users have and why they use or don't use a specific feature.
For example, a retail bank had a goal to increase the number of payments made from the mobile app. During user interviews, many users revealed that they don't make payments from the mobile app or make them very rarely. The main reason that was cited is that it is easier to do it from a computer and that they found the app's payment form difficult to navigate. That motivated the bank to think about how to make the payment form much easier to use, resulting in a quick change in the users' habits of making payments only from the computer.
3. CARD SORTING
Card sorting is a method used to understand how users categorize information. It can be performed when creating a brand new product or when improving an existing one to create an intuitive Information Architecture for a product.
Two types of card sorting methods currently exist: open card sorting and closed card sorting. Open card sorting helps to see how many and what kind of groups users will create and how they name each group. For example, will users put credit card information together with their accounts, or will they create a separate group for it?
Conversely, closed card sorting helps to understand what information will be put into specific groups provided to the user. For example, there is a plan to create groups: Accounts, Cards, Payments, Profile and Settings. The user is given information that needs to be ordered into those given groups. As a result, it is possible to see how the user will order it, if the structure matches the intended structure.
4. TREE TESTING
Tree testing is a tool to ensure that created Information Architecture for a product is understandable for its users and that they can easily navigate through the service and find exactly what they need.
Tree testing can be performed at any stage of a product - for a brand new product that is under development or a currently running product to prepare for improvements. This method will give good insights into whether created or current product architecture is understandable and easy to navigate, and to understand why users have difficulties finding something.
In the tree testing method, users are provided a full list of categories and sub-categories and are asked to perform specific tasks. For example, a user might be asked to pay for utilities or add an additional account in a different currency. In this way, it can be determined whether the user can easily understand how to perform the requested task.
5. USABLITY TESTING
Usability testing is the best method to get insights about exactly how real users interact with a product. It should be performed as often as possible to test separate scenarios or a whole product.
Testing can be performed in the wireframe stage to determine if users understand flows. In the design prototype stage to ensure that all visual accents are used correctly and to see how existing users use the service or how totally new users deal with the same service.
In usability testing, users are asked to perform specific scenarios, for example, to send a money request of 25 EUR to a friend or to freeze a card that a user might think is lost or stolen. It's important for a user to comment on every step along the way and verbalize every thought that comes to mind while performing each scenario.
Detailed attention must be paid to how this user performs each scenario. To get good insights, it is enough to test five users because it will give an overall idea whether the user can handle the scenario and perform it without difficulty.
The aforementioned five key methods to improve the usability of a financial service is only a part of all the possible research methods. The main purpose of all of them is to collect as much information as possible about users' behaviors in order to create the right product for them.
Without user research, it is almost impossible to create a product that fully solves users' problems in a manner that is quick and completely understandable. The main reason for this is that a business' perception and knowledge sharply differs from a product's end users. So, the business has to get to know and listen to their users to create a product that they love to use and recommend others to use it as well.