Healthcare Survey App
Role:
Key UX Designer
Timeline:
Mar '23 - May '23
Software:
Axure, Adobe Suite,
Pen and Paper
Team Size:
4 People
View Prototype
Problem
To design an innovative smartphone app and research tool that is scalable, which can be used for collecting and examining consumer feedback about optimal and suboptimal healthcare design.
Audience
Focused on improving the quality of feedback from Employees and Patients of hospitals to improve and better the spaces they work / live in.
Solution
Designed an Feedback application, that was accessible for anyone to use while also providing users with the tools and options to navigate the app and leave feedback with ease.
Project Constraints
Strict Deadlines
Had 12 Weeks to finish this project with strict deadlines in place for check-ins throughout the project.
Designing for Stakeholders
Constant check ins and feedback from key stakeholders for the client we worked for, meant an ever changing landscape of the scope we were designing for
Research
Design Inspiration
A Mixture of literary reviews and competitor analysis lead us to a strong base in HOW and WHY we are designing
Storyboards
Once we had done some base research we developed 4 potential concepts of our App through storyboards
User Interviews and Surveys
Conducted Extensive User Surveys to get a wide range of peoples opinions on issues such as how long it should take to give feedback and if they ever felt like the feedback they gave left an impact.
Persona’s and Heuristic Evaluation
The User Surveys/Interviews led us to create 3 key personas of our potential stakeholders. These persona’s were a good starting point for us beginning to design and think about usability heuristics.
Ideate
Flow Chart of Interaction and User Flows
We started off our proper ideation phase by creating and overarching Flow Chart of interaction. This then lead us to form User flow maps of each of our Persona’s doing different tasks on the application. This helped us find and eliminate an of the tension points from the usability standpoint of the application before we started testing.
Wireframes
We designed an option A and B for wireframes to give us some diversity and ended up going with Option B for our Final Design
Requirements and Style Guide
For this being a Client Project. We had to give to them both a list of technical requirements that would be needed if they were to efficiently use our application. And also a style guide for which we designed all visuals aspects of our app around.
Final Prototype
Accessibility
One big thing we wanted to address before this final hand off was accessibility. As this would be used in a healthcare spaces we needed to ensure that all the Visual options and settings offerent were both Accomdating and Accessible
Key Screens
Reflections
1.
How to work in a challenging team. Due to the nature of the people I worked with on the projects, we were all on clashing and differing schedules at the time so it was hard to find the time to really sit down and flesh things out. However, it wasn't impossible, we figured out ways to work around this and created something we are all super proud of!
2.
Accessibility is key to getting valid feedback, as everyone is different and has different levels of tech literacy. It was key to figure out how to designed with a wide range of stakeholders in mind
3.
How to work with key stakeholders to create a product I can be proud of and that they are able to used either parts of or the whole thing.