VARyGreen for
VARious  meals

VaryGreen, a mobile order app of an urban fast casual restaurant, aims to provide personalized, trustful and nimble online order experience to people who need the balanced healthy meals.

Duration

March - May, 2022 (~20 hrs/wk)

Type

Independent Project

Project Type

Mobile Application Design

Role

UX&UI Designer | UX Researcher

Overview

Provide tailored meals for a healthy lifestyle.

Challenge

Design a product from scratch without the background of the problem, context, and users.

Result

Defined users and market, developed business value propositions, and delivered high-fidelity prototypes and design system

Project Background

“What shall I eat?”

← A question usually pops up at least THREE TIMES a day in many people's heads. The truth is, if we want, there is always something in the fridge, in the office drawer, or in the corner convenience store waiting for us to open the packages.

People need to eat, and eat properly.

Thus, what people really are asking is, “what is the appropriate food to eat?”
Humans absolutely need calories to ensure the basic functionality of living, studying, working, and relaxing. Having appropriate food, which equals a healthy diet in most people’s definition,  can sustainably ensure so for the longer term.

But it’s hard to balance.

When I asked many people what a “healthy diet” means, the word mentioned the most was “balance”.
“I need a balanced composition of fat and vegetables.”
“I will balance my plate with the cheat meal.”
However, doing the calculation while considering all the trade-offs is a challenge.

So I will do the job of
finding the balance for users.

Thus, the project's mission is to find the balance between users’ healthy concerns, body situations, diet styles, and daily scenarios.
The product aims to answer the question:” what is the appropriate food shall I eat?”

Project Overview

Process of “designing a design”

As a starting point, the initial design prompt was straightforward, with barely any context or problem to solve. Thus, besides discover-define-develop-deliver as the conventional process of designing this product, the whole journey is also the process of going from don’t know what it could be, to do know what it should be.

Phase 1: Discover "WHO & WHAT"

To design a useful product, I needed to ensure I was not diving into a dead sea but a space where I could craft values. I had to understand the market's existing situation, challenges, and opportunities to picture what the product would look like.

Step 1.1
Identify the users

To figure out who I was designing for and what problems I could help resolve, I took a deep dive by researching diet-related data and news:
Unhealthy dietary trend. Groups between 20-39  and 40-59 ages are at the most risk of obesity, with serious health and financial consequences.  [World Health Organization]  [CDC 1999-2017] [CDC 2017-2020]
Dining out habit: 84% 20-39 ages and 75% 40-59 ages order from a restaurant at least once a week. [Technomic]
Re-bouncing workday meal needs: Because of the hybrid RTO(Return to Office) models,  more and more workers are returning to the office. [NYC] [Statista] [Cushman&Wakefield] [TheWallStreetJournal]

Findings

By doing the research, I defined:

  1. Who the users:
    a. Group between 20-39 ages and 40-59 ages
    b. Office labors who have the need of workday meal when returning to office
  2. Users’ concerns: at a high risk of serious health consequence
  3. Users’ dining pattern: having a habit of dining out or order from restaurants weekly

Step 1.2
Listen to the users

Bringing the macro user portraits forward, I wanted to go micro to understand users’ considerations, emotions, and motivations behind behaviors.
I had eight user interviews and asked questions about the considerations that emerged before/during/after ordering a meal they would consider as healthy. Then I used the empathy map and documented every interview's verbal data to translate what they said into what they thought.
At this moment, I understood users' pain points and motivations at the general level and summarized them as three archetypes.

Findings

By doing the user interviews, I defined:

3 Archetypes:

  1. Healthy-Conscious:
    Value quality and nutritional value of food to make informed decisions
  2. Execution Shortage:
    Find it hard to achieve a short-term to long-term goal due to the lack of motivation and/or task management
  3. Busy Bee:
    Don’t have time to think about what to eat, or not interested in sparing time to learn the nutrition knowledge

Step 1.3
Draw the users

Since this phase's goal was to comprehensively discover what the users want, the archetypes were still too broad to draw the user pictures.
So I generated three personas at mixed levels of the three archetypes.
Furthermore, I defined users' desires by writing down the user stories, goals, and frustrations. The desires would be translated into actionable design ideas in Phase 3.

Findings

By building 3 personas, I defined:

6 User desires:

  1. Convenient process
  2. Customization flexibility
  3. Clearly disclosed information
  1. Optimized choices
  2. Entry-level friendly
  3. Long-term values beyond

Step 1.4
Learn the market standards

Before jumping into the rabbit hole of ideation, there is still one question: where will the users go for the meal?
To answer the question, I researched users’ dining trends and found that the fast-casual restaurant (FCR) market perfectly matches all the users’ dining trends.
I analyzed direct(Sweetgreen, Chipotle, and Panera) and indirect (Platejoy and Mealtime) competitors. It helped me to understand the FCR market standard features.

Findings

By analyzing the fast-casual restaurant market competitors, I understood:

Market standard features:

  1. Typical feature of personalization & customization:
    a. dietary preference
    b. ingredients adjustment customization
    c. diet restrictions flagged accordingly
  2. Better food quality with fewer processed ingredients:
    a. clear and attractive figures paired with meals
    b. ingredient information disclosure
  3. Entry-friendly and convenient e-commence order process:
    a. comprehensive navigation between menu, meal page and cart
    b. price & calorie adjusted accordingly and flexibly

Phase 2: Define "HOW"

By discovering the user groups, user problems, user desires, and marketplace, it’s time to make sense of my research. I practiced HMW to synthesize the right problem and phrase the product vision accordingly.

Phase 3: Develop "Why"

The definition of a mobile order APP was far less than enough. In other words, why VaryGreen? What makes it unique? Why don’t users just go downstairs and grab a sandwich from the closest salad bar?
I wanted to develop an advanced feature to resonate more with users.

Strategy:
from Desire to Value

To make the product stand out, users need to see the value of using it. I always believe that the answers to all user-behavior-related questions are just hidden behind what they do and say.
So I went back to previous research insights and translated the user desires into 3 value propositions.

Value 1
Personalization

Users tend to create a stronger emotional relationship if they are provided with tailored meal recommendations that catch their flexible dietary preferences and scenarios.
Being vegan, taking a keto diet, being allergic to dairy, having an upcoming fancy meal, and staying within a specific calorie range... can all address a sense of personalization.

Strategies

To address the value of personalization, i designed to:

  1. Create an onboarding dietary survey based on other competitors’ existing survey models
  2. Provide filters to reflect ongoing needs and situations

Value 2
Nimbleness

The fewer efforts users spare to complete a task, the more willing they are to return. Most users are not interested in finding the one-and-only dish from a long menu list.
Thus, a nimble order process means landing at the confirmation page as intuitive and agile as possible from the second of tapping the APP.

Strategies

To address the value of nimbleness, I designed to:

  1. Apply filters to minimize the disruption of choosing dishes listed on the screen
  2. Highlight recommended daily dish
  3. Provide shortcuts to saved or recent ordered dishes

Value 3
Trust

If the product cannot convince the users to tap the confirmation button, then all the previous values mean nothing.
Users tend to trust you if they see how the information they provide is reflected and how the dish will impact them.

Strategies

To address the value of trust, I designed to:

  1. Flag and tag specific ingredients based on the onboarding diet survey data
  2. Provide personal macro demand chart based on the onboarding body survey data
  3. Reflect how every dish will contribute to users’ daily macro demands
  4. Pair precise figures with text to indicate what and how much to be expected in the dish

Phase 4: Validate "IF"

A product can never be called a product until users examine it. I needed to validate if the product experience would be as personalized, nimble, and trusty to users as I proposed.

User test analysis + Iteration

To validate the values, I designed three targeted tasks throughout the whole user flow. 8 of 8 user test interviews were the target users in the age group with workday meal needs.
With all the good comments, I used the affinity map to tame complexity, understand the priority from ambiguous data, and identify themes.
In conclusion, the most significant issue that emerged after analyzing was: the product was not easy to digest.

Findings

By analyzing the user test results, I found that:

  1. Users were overwhelmed with the information across screens, especially the macronutrient chart
  2. Users had difficulty locating the touch points to complete the tasks
  3. Users had no problem trusting the personalized system, but some of the order steps were not nimble but redundant under specific situations

Strategy 1
Progressive disclosure

Responding to the overwhelming information, I lessened complexity by progressively disclosing it.
I designed to hide the irrelevant information until it becomes relevant. The macronutrient chart won’t be shown in the first place until the users want to know more. Besides, the users will also have a delightful sense of control by tapping to drop the chart down.

Strategy 2
Visual readability

Responding to users having difficulty locating touch points to complete the task,  I improved the visual readability.
I improved the content hierarchy by adjusting&adding text, size, color, orders, and graphics.
I also followed best practices since users are more familiar with the existing modes.
For example, after studying the same feature in Yelp, Airbnb, Postmates, and Target, the filter was changed from the dropdown to move-in. In this way, users can review all the options at the same time within a single click.

Strategy 3
Quick-decision support

Responding to users feeling some order steps were redundant under specific situations, I simplified the customization feature to support a quicker decision. The customization sets were removed since most interviews criticized them as “unnecessary”. It will reduce the decision points from 4 to 2.
Meanwhile, I split the macronutrient chart and customization feature. It will avoid the users being distracted by the numbers when trying to make a decision.

Final Design

Design System

Google Material Design Kit helped me to jump into the rabbit hole of the design system, and thinking through the typography, color palette, components, and even writings put me into the shoes of the business to convey its personality to users through the design system.
Besides, users tend to think the design is more usable if it’s visually lovely.

Inspiring Onboarding

Users will not only start building trust with the product but also be encouraged to learn and track their body health.

Enjoyable Online Enperience

Explore the dishes they love, manage diets, and learn interesting health tips... Users will have fun looking into all the great features with easy access.

Great Flexibility

Users can either follow the perfect pre-set composition of the dish or their own heart to build the bowl. The comprehensible interface will satisfy such needs without difficulty.

Lesson-learned

Designing a product
from don’t know what it could be
to do know what it should be
is an eye-opening journey for me.
  • No problem, no product: The initial design prompt had no problem-related context. Thus, the most challenging part was identifying the problem. Once I figured it out, I saw the product.
  • “Why”-driven design: There were several design steps applied before thinking through why to do so, and later I had to either dump it out of the design process or extract the useful pieces out and rethink how to embed them into the design story.
  • Build from best practice, while seek for uniqueness: Some of the features that took me the most time were later easily figured out after checking other APPs. Meanwhile, the special “aha” moment was the place that got recognized most during user tests.

I had fun diverging from 0 to ∞, and converging to 1 product :)

More Work