Design a banking application for a blind customer or with low vision impairment.

Question

Design a banking application for a blind customer or with low vision impairment.

Asked at Meta (Facebook) over a year ago

2.3k views

Problem Solving category

& 2 other companies

Asked at

& 2 other companies

2.3k views

How to answer Problem Solving questions

Interview Guide

Top Meta (Facebook) interview questions

What is your favorite product? Why?89 answers | 263k views
How would you design a bicycle renting app for tourists?62 answers | 82.5k views
Build a product to buy and sell antiques.54 answers | 66.8k views
See Meta (Facebook) PM Interview Questions

Top Problem Solving interview questions

Invite members
Invite by email

Add another

Answer 1

Feature Clarification:

Would this be a Mobile app or a desktop app? Ans: Mobile Application
Would the Patient Master data be available form a Legacy system? Ans: Yes, some data is available, but the user would also need to enter the details
Does the Billing and Payment need to be automated after finding the doctor? Ans: No Patients needs to find the doctors only.
Should the Patients be able to rate doctors? Ans: Yes
Do we need to have different types of users who access this application? Yes, there should be different categories like Premium, Elite, Regular Users.
Can we assume that patients would like to rate the doctors based on their experience and this rating is visible to other users? Yes

User story

We need to build a Mobile application where the user should see the list of Doctors based on the geographical area in USA. The user would enter the Sickness symptoms and based on this information a doctor with expertise would be suggested. Patients will also maintain the history of illness and doctor can access this information securely and interact with the patients.

Once the Patient visits a doctor, he/she can rate the doctor based on their experience and this review is then submitted to an Admin who approves or rejects the reviews.

Backlogs

Ability for User persona Patient and Admin to login and access the application. The Patient users get the features based on their “type” of the user. E.g. Premium User, Elite User, Regular User.
User Patients will enter the sickness symptoms, want to see a list or Map View of Doctors based on the area.
User Patients can also choose Doctors based on the doctor’s expertise.
The Doctors are shown by default in the order of relevance, the user can then sort the list using rating, distance, cost etc.
User Patients can book appointments for the Doctors based on the availability calendar.
User Patients then get a notification and calendar block for their confirmed appointments
Users can rate the doctors visit and then submit this to the administrator which will then be approved
Admin user can login and change the administration details, workflow and extend the application for each business case

No	Feature	Effort	Impact/Outcome	Mandatory
1	Ability for User persona Patient and Admin to login and access the application. The Patient users get the features based on their “type” of the user. E.g. Premium User, Elite User, Regular User.	H	H	Y
2	User Patients will enter the sickness symptoms, want to see a list or Map View of Doctors based on the area.	M	H	N
3	User Patients can also choose Doctors based on the doctor’s expertise.	M	H	Y
4	The Doctors are shown by default in the order of relevance, the user can then sort the list using rating, distance, cost etc.	L	M	Y
5	User Patients can book appointments for the Doctors based on the availability calendar.	M	H	Y
6	User Patients then get a notification and calendar block for their confirmed appointments	L	M	Y
7	Admin user can login and change the administration details, workflow and extend the application for each business case	H	H	Y

The backlogs can be taken in the above order itself.

H P · Answer 2 · 2020-02-14T06:41:39+0000

Feature Clarification:

By application, do we mean a web app or a mobile app? Answer: Mobile app

So the blind user currently uses the mobile phone, is familiar in installing the app from the appstore and we need to have the app designed for him?
Answer: Yes

Objective clarification:

The ask is to design a banking app for a low vision impairment (LVI) or a blind user.

Since no bank want to have two apps on the store confusing the end users, it would the common app and when the accessibility mode is turned ON, it would work fine for LVI users

Needs of the LVI/blind user:

User wants to check the bank balance
User wants to transfer the money/pay the CC or utilities bill from the banking app
User wants to check the mini/detailed statement to understand the credits and debits in his account are ok
User wants to open a FD or a RD from within the app

There could be possibly more user needs, but we'll design the app considering the above into consideration

Features:

#	Features	Effort	Impact/Outcome	Mandatory
1	User to be provided with the accessibility mode on the login screen	L	H	Y
2	User to be provided with two options on the home screen, Statement and Transactions i.e. if the user clicks on the left side of the mobile screen, it would go to statement, RHS to transactions User to have similar two level options on each page to keep navigation easy Statement > Mini & Detailed Transaction > Transfer to Bank & Pay CC/other bills etc.	M	H	Y
3	User to be provided with a voice/screen reader feedback (or vibration) with each tap	L	H	Y
4	User to be provided with a voice assistant on all the pages of the screen which can perform the transaction without any manual input from the user	M	H	N
5	The bank statement should be controlled through the voice button for navigating through the records, which the voice reader can read	L	M	N
6	User to be allowed to set favorite action such as, asking the voice assistant to announce the balance everytime the user logs in	M	M	N

Based on the priority, we can start with #1, 2 and #3 since those are absolute must features, and the rest can follow through.

Post the deployment, we can observe the usage pattern as to how many users are using it in the accessibility mode and then plan the subsequent features if the usage is higher.