Before we can define the scope of the problem we're
trying to solve, we had to understanding the structure
of the current program.
1. Users sign up for the program via the site
2. Users prompt to answer 10 self-assessment questions
3. Users receive subscription confirmation email
4. The morning after, users receive an email with Day 1's lesson
5. In the afternoon, users receive an email with supplementary info
6. Users receive 2 emails a day for the rest of the program
Since the majority of our users are in India, we decided to focus on Gheeta,
the persona created based on data, research, and the client's feedback.
Our persona Gheeta, a young mother of 4 living in Bangalore,
has helped us to empathize with the different living conditions, family culture,
and religion of users living in a developing country.
Since the client had left the scope of the project open-ended, it was up to us to define the problems we wanted to solve. We decided to focus on the onboarding process.
Our team felt that for the users, this will help them understand the purpose & value of the program.
It will benefit the Foundation by increasing user engagement & improving accessibility for non-North American users.
"Transform the current web-based onboarding process into an interactive mobile experience. It should be engaging and help users to understand the value of the program."
Our team started out by sketching out different versions of prototypes both on paper and the whiteboard. Limited by the low-fidelity, we only found some minor issues after a few round of usability testing.
Our major discoveries came after creating wireframes in Sketch and linking them into a clickable digital prototype in InVision.
"The onboarding process is too long"
Users start to lose their focus & getting bored. From this, we realized that needed to break down sections into smaller subsections and to add more interesting interactions.
"Where am I?"
Users were anxious to know how much more information is coming. So we should display a progress bar to allow users to estimate how much more time & effort is needed.
"Information overload "
Many users thought the screens were too text-heavy & they don't end up reading any of the information at all. So we needed to reduce the content and make everything visually explanatory.