A group exercise in designing an interactive interface for an emerging startup.
For this project, we chose to design a mobile interface for Slingshot, a YC startup that utilizes software that automatically monitors and reduces people's medical bills.
With Slingshot, users can sign up and connect their insurance. The software will then begin to automatically monitor all claims processed by the user’s insurance and will notify the user when they are being overcharged for errors, up-codes, uncovered costs, and negotiable items. From these notifications, users have the option of enabling Slingshot to correct and lower their medical bills. Users can also upload medical bills directly and opt in for automatic insurance claim monitoring.
We decided to focus on the direct user interactions of Slingshot, where users easily access information on their medical bill savings. As a result, we decided to create a mobile interface for Slingshot, since mobile interfaces are accessible to any smartphone user, for easy, everyday use, and they allow for real-time state monitoring through push notifications.
Because Slingshot is focused around consumer health services, there's a wide range of potential users who would be impacted by our interface:
We began our iterative design process by having each member create rough sketches for 3 different screens. We didn’t specify what those screens would entail, as we wanted to get an idea of what type of screens each member thought would be the most essential for the prototype. Though some of us had screens that overlapped, we felt that our design concepts overall were substantially different enough to include them in our final sketches. You can find each of our sketches below:
After we finished our rough sketches, we incorporated our sketches (overlapping and separate) with additional features we felt were also relevant to Slingshot’s mission into one set of wireframes with 4 different screens: a “Home” page, a “Bills” page, a “Trends” page, and a “Resources” page. You can find our lo-fi prototype here.
After creating our wireframes, we implemented them into a more polished, Hi-Fi prototype through Figma. In this prototype, we also added a few features not included in our original Lo-Fi design (such as the 'Click to Upload Bill' button on the "Home" page) and included significantly more detail for realistic interactions users would be engaging with.
We presented this prototype to a critique session with other students in the CSCI1300 course. The main critiques we received regarded:
Once we received our critiques, we further iterated on our design by implementing fixes based on the suggestions offered by our fellow CSCI1300 students. We addressed each main critique in our final, Hi-Fi prototype:
You can find and interact with our final prototype here.
After finalizing our hi-fi prototype, we sent the prototype to a remote user testing service to gather feedback and data on our design from random users.
For users to test our prototype, we needed to create a specific task for them to accomplish. We decided on the following:
"Find the cost breakdown of how much you saved in “Physician Services” on your most recently completed bill from RI Hospital."
To complete this task, we broke down a user’s required actions into 4 subtasks:
With our submission of the prototype to the UserTesting site, we included the following directions for the user to keep in mind:
"Imagine you are a company employee stressed about medical bills from your emergency room visit in September. You want to check if that medical bill has reduced in cost through the Slingshot app on your phone. Your task is to find the cost breakdown of how much you saved in “Physician Services” on your most recently completed bill from RI Hospital. You are encouraged to think aloud as you perform the task so we can better understand your thought process while navigating the site! Please note that this is an interactive mock-up and not an actual mobile application. Some screens (e.g. the Spendings tab in the Trends page) were not actually created or are unreachable through the mock-up."
We also included the following post-test questionnaire:
We had a total of 3 users test our Hi-Fi prototype, with their results and answers to our post-test questionnaire included below:
Post-Test Questionnaire:
Post-Test Questionnaire:
Post-Test Questionnaire:
Finally, we analyzed each user testing video by breaking down the subtasks, the errors users had made, overall user performance with the prototype, and iterations we would make for our prototype based on these results:
All users had a general sense of confidence and navigated with ease. Any errors they came across, they were eventually able to resolve with some exploration.
Based on all the users' feedback and their testing videos, here is what we'd improve upon in future iterations of this prototype: