Case Study: EaseHealth

EaseHealth is for users looking to improve their health, regardless of their background or current health status. We aim to engage community integration and personal development to increase users' self-esteem and lead them to an overall positive mindset. EaseHealth understands that being accessible means learning and applying tools that encourage people with disabilities.

Problem Statement

People who are isolated result in having medical and social needs being unmet. [Source] Software tools, specifically mobile health tools, can be part of the solution. In knowing this, we have created a tool that exposes users to health resources with features to support community integration. We will know if there are positive effects when users report increased mood over an extended period.

Empathize

Competitive Analysis

View complete analysis here

Analyzing how large the market is, I understood users want a health app that feels trendy, simple, and at a low cost.

Surveys and Interviews

Remote Sessions (1 Participant): Zoom and iPhone screen recording

In Person Sessions (5 Participants): iPhone voice recording and screen recording

Each sessions took 10 minutes

•Users would like to see how their mindset and goal progress.

•If users feel overwhelmed, they will look for an app to assist them with their weakness.

•All users said they feel comfortable putting their medical information, if explanation is given.

•Users enjoy social media to learn life skills by interacting with others that think differently or use Google to ask specific questions

Define

User Personas

Users are busy and intimidated into starting something new. It is best to offer users one tool that encompasses all aspects of health, offers clear visual explanations, and can easily connect with others.

Ideate

Original Sitemap

This was the first sitemap created. To test how the effectiveness of the map, I hosted a closed card sorting session, where 6 participants sorted 16 cards into six categories using OptimalWorkshop.

Redefined Sitemap

Analysis: The versatility of the word Activity created confusion among participants. Action Plans: Change name of page to Move Your Body

Analysis: Participants found the page title to be vague Action Plan: Change page name from Questions Asked to Questions. Ask A Questions is now crosslinked with Mental and Physical Health Page, there is also an FAQ subpage on the Settings page.

Analysis: Personal Information was assumed to encompass all aspects of health. Action Plan: Omit the page "Personal Information" to "Settings". The intended page is now called User Profile. The personal information users expected from Physical Health and Mental Health will be found when opening those pages.

Prototype

Lo Fidelity Prototype

Now I understood what was important to have in my design and began working on wireframes.

Test

6 participants carried out 3 tasks with the low fidelity prototype using AdobeXD. The sessions took 10 minutes, results are below:

After the feedback from users, I implemented the following:

Question-and-Answers page became a subpage for the Mental and Physical Health pages
Menu icons were labeled
In Ask a Question, the Category button was moved up

Web Content Accessibility Guidelines

By referencing the Web Content Accessibility Guidelines (WCAG), I further improved my design.

Protoype

High Fidelity Prototype

View Prototype

What is Next?

Conduct A/B testing with menu page or menu tabs for Community Answers
Conduct user testing with disabled population

Thank for your time

Let's Work Together!

Google Sites

Report abuse