SPRINT18 PORTFOLIO

PromptedPlates

PromptedPlates is a versatile and innovative product that simplifies the process of deciding on group eating preferences and generates a comprehensive grocery list for convenient and efficient shopping.

Problem Statement  

Grocery Shoppers need a quick and adaptable product to help determine household eating preferences and conveniently generate a grocery list for quick shopping.

Problem Background  

Daily food consumption is a fundamental necessity, and individuals have multiple options to fulfil this need, including dining out or cooking at home. However, for those who choose to cook at home, deciding what to prepare for each day of the week can become complicated, particularly when considering the personal preferences of other household members.

Once a decision is made, a list of necessary ingredients is created before heading to the local grocery store. However, given the distractions of daily life, it is possible to overlook an item on the list, which can result in wasted time during the week by having to return to the store to retrieve the missed item.

In the current climate, with the increasing prevalence of remote work and the ease of developing technology, there is a significant opportunity to create a distinctive product that caters to the unique needs of those impacted by these challenges.

Research Insights

User Pain Points

  • 52.9% of people visit the grocery store every other week 
  • 41% of people thought speed of making meals was important to them 

Supporting Data

  • 70% of people plan what meals they want to eat before going to the grocery store
  • 68.8% of people do not want to eat meat in every meal
  • 43.8% of people do not want to cook every meal 

Feedback

Based on user interviews, it appears that the challenge of deciding what to eat when considering the preferences of loved ones or other household members is a significant problem worth addressing. Nearly all interviewees agreed that this is a common challenge, with some reporting spending several hours each week trying to make such decisions.

Future Steps

I would like to explore additional factors that could drive the development of features, such as dietary and nutritional considerations. Additionally, I plan to implement gamification techniques to increase user engagement and encourage repeated usage. To enhance the overall user experience, I will collect usage metrics and data on the back end, including user choices, satisfaction with meal selection, and the speed at which users navigate the selection process.

Another important area to explore is the dynamic nature of user preferences. Some users may prefer consistency in their meal choices, while others seek variety. By understanding these changing preferences, I can better tailor the presentation of meal options to meet the unique needs of each user. 

Learnings

Product Manager Learnings:

Matthew Fay

During my recent learning experience, I gained insights on how to analyze competitor products to uncover key features, as well as how to use survey results to inform product development priorities. I also learned about the importance of fostering strong collaboration between functions such as Design and Engineering, as emphasized by Dave Lovecchio, MBA.

One key takeaway was the significant impact of company size on the challenges that product managers face. For smaller companies, experimentation and agility in identifying product-market fit is crucial, and not all features may be sustainable in the long term.

Furthermore, I discovered that early-stage companies may not have a clear understanding of their ideal customer profile initially, and this can lead to difficulties in managing customer expectations. Alignment between functions such as Sales, Product Marketing, and Product Management is crucial in addressing such challenges.

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