SPRINT32 PORTFOLIO

save&make

save&make is an application tool meant to store, organize, & help to execute multiple recipes you find on social media. Whether it’s pinterest, youtube, instagram, same&make allows for a consolidation of your favorite saved posts so you can simplify how you cook, eliminate the information overload, & give you more time to do all the other things in your life.

Problem Statement  

How can we make it easier to navigate recipe information from social media and allow for actual execution of recipes & save time? 

Problem Background  

According to my user research, 82% of participants store recipes in some sort of folder or application from one of their social platforms and over 50% of them rarely make their recipes. 

Focusing on city-living millennials, working both remotely and hybrid and who cook at least 2-3 times a week, their main priorities are simplicity & how to save time . These millennials that cook at home nowadays end up "saving" recipes or how-tos in different applications or folders. This immediate saving and storing creates a sense of information overload and can get lost in the backlog of photos. This information overload makes sense since per a February 2024 report from Snap Inc. and IPG Magna, cooking recipes are the most popular form of influencer created social media content, according to 51% of worldwide social media users. 

And what if there are more than one recipe someone wants to make? Consolidating grocery lists and making sure you get the right items for each (especially when they overlap) can be time consuming and prone to error. All important things to think about when you’re busy trying to live your life. 

Research Insights & User Pain Points

  • “I screenshot or save new recipes but at the end of the day I can’t remember what I saved and it just becomes recipe overload” - User Interview #1
  • “Conversion rates are difficult to deal with when grocery shopping, especially w multiple recipes” - User Interview #1
  • “Too many steps from figuring out what to make to then going out and buying the things and making it” - User Interview #2

Supporting Data

  • 91% of the survey participants say it’s important for them to cook for themselves 
  • 81% of the survey participants say it’s difficult to do so because of time constraints 
  • 45% of the survey participants say they rarely reference the recipes they’ve saved

But 58% would like to try to cook something new at least once a month

Feedback

It’s clear that there’s a saving trend and people want to cook more for themselves, however time constraints and lack of simplicity have made it difficult to do so. Users don’t want another app to add to the steps they already have to make but are curious how this could save them time and help organise themselves. 

Future Steps

  • I’d like to further investigate the volume of saved cooking information some text
    • I want to evaluate how large of a pain point it is and how much room is there to help
  • I’d like to understand dev work that needs to be done to seamlessly connect the social media platform to save&make some text
    • What would it look like to not save the recipe on the app but automatically save it into save&make 
  • I’d like to mock up the login & navigation page of save&make 

Learnings

  • Overconsumption is a big part of social media and interestingly enough, cooking & meal content is one of the top types that are produced. 
  • People are still motivated to cook and would even like to cook more
  • There is a want to minimise the content noise and provide simplicity to cooking new recipes 

Learnings

Product Manager Learnings:

Sara Cruz

I learned that I’m quick to find/look for a solution before diving into the problem space. Product management is about settling into the problem space and understanding what and where the need is. I learned the importance of user stories and long-form interviews. These can branch into specific features or provide a completely new perspective.

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