Product Design: How would you build an alarm clock for the blind?
What is the question asking?
First task would be to figure out what kind of clock are we talking about here. You can ask the interviewer or present options i.e. a physical clock or a mobile application or something else.
Second thing that we need to figure out is if the users are completely blind.
Let’s say we want to go ahead with a physical clock for completely blind . Among other things to consider, one could be that it is a table mounted small physical clock. We will go with this for now?
To summarize the requirement for the alarm clock:
You have to design a physical clock probably the size of a 4 inch cube for the completely blind user(4 inch is an assumption to help you visualize the end product).
Who are the users?
Users are blind. So they have the following attributes and assumptions:
- Users cannot see anything.
- Users can read braille.
- Users can touch and feel.
- Users can hear.
It is good to iterate the user’s specific attributes related to the problem.
What are the use cases?
Use cases that the alarm clock will fulfill:
- User should be able to locate the clock easily.
- User should be able to know the time and the date easily.
- User should be able to set the current date/time.
- User should be able to set an alarm.
- User should be able to snooze when the alarm rings.
- User should be able to close the alarm.
- User should be able to know when the battery is low.
- User should be able to change battery easily/charge the clock.
What are the solutions to the use cases?
Let’s look at the use cases one by one and mark the ones I would like to do for the MVP. The key here is that you should select the ones which solves the use case with minimum effort. I will be marking the solution with “MVP” that I have selected for the MVP.
User should be able to locate the clock easily.
- Install it beside the bed/fixed location (assuming that the user uses it only for waking up) — we have not talked about any such use case does not mean we cannot do this. — MVP
- The clock can be voice activated. So when the user calls out, it will reply back to the user.
- Connect the clock with the user’s smartphone. There should be a clock app which will be voice activated (user can ask where the clock is). User can map the location of the clock in the house with the app and the app can pinpoint the location of the clock. Every time it is moved, it registers the new location. This clock app will suffice for a lot of the use cases (like setting the time, setting the alarm and may even act as the alarm), hence we will not be going ahead with this implementation.
User should be able to know the time and the date easily
- User can ask the clock for the time and date
- Single touch button and the clock will loudly say out the time and the date — MVP
- Braille on sides for date and time(right side can be used for date and left for time)
User should be able to set the current date/time
User should be able to set an alarm
- Voice based setting of alarm — MVP
- Through the user’s smartphone
- Virtual clock with hands on the back of the clock through which we can set the alarm with buttons for AM or PM
User should be able to snooze when the alarm rings.
- Snooze button/close button — MVP
- Voice based: Please snooze or snooze
- Snooze for 10 mnts: Knob for snooze by 10 mnts — MVP
- Snooze from smartphone
User should be able to close the alarm
- Close alarm button — MVP
- Voice based close
- Close from smartphone
User should be able to know when the battery is low.
User should be able to change battery easily/charge the clock.
- Should let the user know how much is left(20% onward) — MVP
- Should be usb chargeable or wireless charging — MVP
So, I have defined the users, the user needs, the use cases and the solutions to the use cases. The MVP product shall contain all the features marked in MVP.
How else do you think this question could’ve been approached? What could’ve been better? Let me know.
