SPRINT17 - Mobile App

Full Meal

Full meal is a meal companion to help singles or couples decide what to eat.

Problem Statement  

Couples need a way to decide what to eat. Perceptions of indecision may create tension and hinder/damage bonds created between couples. Additionally, time spent on identifying meal options create additional pain for couples, as that time can be spent on fun or engaging activities. 

Problem Background  

Decision making can be difficult. When considering meal options, couples may face a series of decisions that delay ordering or preparing a meal. The result is an inefficient process that also delays gratification. 

Our survey found that couples face information overload–the myriad of options presented on food apps, add to the difficulty of deciding what to eat. 

While conducting our research, we’ve found that all couples experience some form of challenge when deciding what to eat. A third reported feeling drained during the process, resulting in a desire to further rush selection; while two-thirds expressed feeling frustrated overall. Additionally, two-thirds expressed they were concerned about price, and speed of decisions and took those into consideration when making a decision. 

Two-thirds found it difficult to decide whether or not to eat out. The difficulty didn’t stop there as that decision was the first hurdle. After identifying whether or not they would eat out they were further challenged by the options presented. If they ate out there were a number of restaurants to select from, the same would be true if they decided to use a meal app like Uber. For all surveyed, if they decided to eat at home, then they still faced difficulty with deciding what to make with what was in their pantry. 

The problem is that there isn’t an effective solution to make decisions, especially when couples are faced with a myriad of options. 

Research Insights

User Pain Points

Couples find it challenging to reach consensus when deciding what to eat. Resulting in time lost, stress, fatigue, and frustration. 

Supporting Data

100% of people we spoke to found that it was difficult to identify what to eat, when sorting through their pantry.

Feedback

Our research validated this problem and found that the majority of couples experienced some degree of difficulty when making a decision about their meals. 

Landing on the Solution

Based on our target users’ pain points, we knew we wanted to work on the following features: a decision tree app that provides a curated list for couples based on a ranked preference by both couples, and best match tool to pair pantry items with potential recipes.

Explanation of Solution

Ideally the solution would allow couples to arrive at a decision faster. Each couple would input a series of ranking for their preferences. The app will then compare the preferences of users and highlight any overlaps and provide a curated list of recommendations. 

In the scenario that couples would prefer the app to help with what meal to cook, the app can prompt the user to list items in their pantry or items they would like to use in a meal. The app will then generate a series of recipes, before showing recipes to users the app will prompt for preferences to generate recipes and ideas in line with couples preference. 

Future Steps

  • Conduct further research on decision trees and running comparisons between perferences
  • Further user research is needed, to ensure the above solution is actually needed by users
  • UX and design needed to be sorted, and timeline/roadmap needs to be created
  • User flow needs to be explored and created.

Learnings

Product Manager Learnings:

Carl Powell Jr.

Co.lab taught me the basics of being a PM and the importance of staying within the problem space. I’ve learned the importance of having varied user inputs/stories as a means of not only identifying what users want but to also uncover and challenge assumptions.

Designer Learnings:

Designer Learnings:

Jo Sturdivant

  1. Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
  2. Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
  3. Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.

Developer Learnings:

Developer Learnings:

Vanady Beard

&

As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.

Developer Learnings:

Stephen Asiedu

&

As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.

Developer Learnings:

&

Developer Learnings:

Maurquise Williams

&

  1. Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
  2. Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
  3. Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.

Developer Learnings:

Jeremiah Williams

&

All in all this experience was very awesome I learned that in coding with others being transparent is key

Developers Learnings:

Justin Farley

&

I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.

Full Team Learning