In case you’ve stumbled upon this blog post and you would like to have more context on what this project is about and how it has evolved, please check the Kick-off, Iteration 1, Iteration 2 and Iteration 3 blog posts.
This is week 6 of the second quarter in AC4D and so far – in our Rapid Ideation and Creative Problem Solving class – we’ve gone through 4 wireframe and concept map iterations, 4 rounds of usability testing and 5 blog posts about on the process of re-designing a mobile bank application.
This past week I focused on refining the flows that I keep receiving feedback on which are mainly the flows of Checking Account Balance and Send Money to Someone.
Problem: Check balance
Before I first tested the flow so a person could check their balance, I decided to redesign the current way all of the accounts are displayed in the original application. With the intention to provide cues to users that indicate that from each one of their accounts, a user could not only check their list of transactions and balance, but also everything else that could be done with a specific account in a mobile application. I did this by adding buttons to each of the account cards.
Unfortunately, the space was so small that the buttons didn’t seem actionable and it took longer for a user to read and select an option (see screen B1) , than to just click the account card and see the list of transactions.
Problem areas: Screen B1, B2 & B3 of Check Balance
Redesign: Buttons where redesigned to seem more actionable. Also, different UI's were used for those buttons that had actions that were taking place on the same screen (transactions, details, settings) and on another part of the app the option to make a card payment.
Problem: Confirmation screen for mobile deposit
I tested the Deposit a Mobile Check flow with up to 5 users so far and they were able to go through it quickly – despite some technical, non-wireframe related issues, like the interactive prototype not being fully interactive, some screens not loading on time, etc. The only main concern I resolved for this flow, was the fact that the screen before the Summary screen and the Summary screen looked too similar – this brought confusion to most users – they weren’t enough indicators that made them think they were in a previous and final step.
Problem areas: Screen C1 and C2, are two different actions. C2 is the summary screen.
The way I solved this is by slightly re-accommodating the content on the confirmation screen:
Redesign: 1st screen is previous to the Summary screen that gives you the confirmation for your check deposit. 2nd screen is the Confirmation screen.
Design Decisions: The “Welcome Screen”
The “Welcome Screen” was initially created after one of the individuals that tested my prototype didn’t know where to go after loging-in. During the session he was able to tap on a few screens from the Accounts screen but was not able to actually accomplish any of the tasks that were given to him.
The screen contains the main options a user will most commonly use on a mobile banking app: Review account balance and information, transfer money, make a deposit and profile and application settings.
After this round of testing, the screen was designed and added to the flow. During the following usability testings, users were quickly able to tap on the option they thought was related to the task I assigned to them:
"Send $100.00 to your friend Ethan Baldwin" - Task #1 - Users would quickly tap on Transfer Money and complete the task.
What’s keeping me from making a design decision is the thought that users might get the impression that they’re being constrained by only seeing these options, especially after repetitive uses of the application.
For this next iteration, I’ve decided to A/B test the Welcome Screen vs the traditional landing screen that most banks use which takes a user to his/her list of Accounts.
Concept Map: Revisited
I rearranged many of the actions that can be taken on the application, after the changes made to the wireframe this week.
Iteration: Above is the 4th iteration of the mobile bank concept map up until now. * Circles with thicker line wait are frequently visited screens or actions * Words on grey font are screens that I still need to build.
Bill Payment & Alerts
Last week I worked on designing the flows for viewing, setting up and changing recurring bill payments, and setting up alerts. For this week, I will be testing these flows.
Stay tuned for more findings!