02 - Your Daily

02 -
Your Daily

02 - Your Daily

Your Daily is a mobile wellness app created by Shawna Bigby-Davis and Mike Davis. Its primary purpose is to help type-A women with autoimmune disease regulate their nervous system using holistic methods. Some of its key resources and tools include wellness courses and programs, meditations, journal prompts, and somatic exercises.

Brief and Project Objective

My team was to be the third design team to work on this product. The brief included descriptions of what designs they implemented from past teams, what they still planned on implementing, and what they had discarded. I was given access to all the previous teams’ research and design files.

I was also given the files to their current design system and wireframes, some of which were live and some of which were still being developed. The files were transferred from Adobe XD, and translated poorly to Figma. Another impending issue was the amount of prior research we had to validate. Given our 3 week timeline, I had decisions to make.

Shawna, the principal stakeholder, had a very clear direction and solid foundation for Your Daily, but also wanted fresh perspectives and designs, so I knew we would have to collaborate closely with her.

I also had to reconcile with one important ask: they didn’t want more user personas. They had a total of nine personas that they had previously designed for, and a large backlog of prior research that had contributed to them.

User Interviews

Our team conducted a total of seven user interviews - 3 current app users provided by clients and 4 non-users that I recruited.I didn’t have access to prior teams’ interview transcripts or recordings, but I did have affinity maps from their user interviews. I used these to “reverse-engineer” an interview script. I also conducted a brief contextual inquiry with interviewees in the current (BETA) version of the app to test for usability and gain better user perspective.

Personas

Since our clients were adamant about not presenting them with any new personas, I wanted to use our data to validate the personas of past teams, and make alterations to these existing personas as a means of infusing any new findings we had into existing research.

I made sure to verify with the clients that they were satisfied with prior research before carrying this out. With these personas, we were then able to formulate problem statements that we would use as a bridge into our ideation phase.

Problem Statements

Jennifer needs more personal, supportive tools to help her develop a more sustainable and authentic self-care routine.

Gianna needs more transparency of information when it comes to courses and workshops to trust that they will improve her confidence and quality of life.

Ideation

Transitioning into ideation for new designs, I again had some decisions to make. What in our research, or pre-existing research, felt worthy of making changes to the current iteration of the app? How should we go about prioritizing features I want to implement? I deliberated with my team on this for another few hours, and came up with a plan.

Our clients’ initial project brief included some sections of their app that they wanted addressed, so we started by looking at our research and whether or not the users felt the same. Overall, the users validated our clients’ priorities. The welcome flow, journal section, and the implementation of a true paywall were all highlighted by users as areas they want to see improvement with. In addition, users felt the navigation system could be improved, and our clients were open to adjustments. Other areas where users felt there could be improvement included clarity of language, reduction in page and text length, and added clarity of paid vs free app features.

After creating a feature prioritization list, I used the MoSCoW method to attribute values to features we might implement.

Must Have

Paywall
Welcome Flow
Transition into courses
New Sitemap
New Design System

Should Have

Homepage Redesign
Journal prompts redesign
Language changes
Bottom nav implementation

Could Have

Membership incentive
Paid features tags
Flare-up button
Condense long text

Won't Have

Coming Soon tags
Rewrite questionnaire
AI assistant

Site Mapping

Usability Testing

After we had complete flows and were satisfied with our direction, I started to increase screen fidelity and insert new component instances. Meanwhile, we started having more consistent client meetings (2 hour meetings once-a-day) in order to ensure any new design decisions were plausible to develop, and to ensure the clients were on board with any new design decisions.

Satisfied that the fidelity of our frames was sufficient enough for a user to navigate, we moved into usability testing. I tested our product for usability with four of the same initial seven participants that I initially interviewed for purposes of comparison with the current iteration of the app. The other three were new non-users.

Pros, Cons, Desires

Hi-fi and Prototype

After implementing changes to our frames from usability test feedback, I started increasing fidelity again and working towards our final product, while my teammates worked on creating journey maps to showcase our personas’ emotional journey through their respective task flows.

These screens showcase the transition from low to high fidelity frames and some changes that were implemented, including language changes, creation of a true paywall, and clarification of features.

Solution

With ample user feedback in multiple phases, this work is a reflection of the desires of current users and the priorities of stakeholders coming together. The users will now have clarity upon entering the app, with a more guided welcome flow, a concise paywall, and a refined journaling feature.