SPRINT28 PORTFOLIO

MUNCH

Discover, bookmark, & organize your restaurant bucket list in one app. It will be the only map you’ll ever need when you want to dine out

Product Experience

Problem Space 

Problem Statement  

How might we better organize and access our restaurant recommendations to facilitate more efficient decision-making and planning for dining out experiences?

Problem Background  

Human beings are naturally curious. Trying new things allows us to expand our minds. It could be mastering a new skill, visiting new places, trying out new extreme adventures, or as simple as trying a new restaurant.

Toronto is a city full of diversity and culinary scenes. There are more amazing restaurants to try than time permits. How can we keep track of all the new places to choose from when the next craving strikes?

This question resonates deeply with our target audience - young adults from a big & vibrant city who enjoy dining out, socializing with friends, and trying new things. 100% of our 26 survey participants could not agree more. They said they LOVE food and enjoy exploring diverse culinary experiences. 90% dine out at least multiple times a week and 70% consider themselves adventurous when trying new restaurants.

Despite their adventurous spirit, they face a common challenge: the struggle to manage their restaurant wishlists effectively. Restaurant recommendations pour in from word of mouth to social media feeds. Yet, when the time comes to dine out, we all still ask the million-dollar question: what and where should I eat? This struggle is underscored by 2023 Google search trends with “restaurants” ranking in #14 searches globally (~185 million searches) and “food near me” ranking #20 searches in the US (~29 million searches).

Research Insights

User Pain Points & Supporting Data

  • Difficulty in organization:some text
    • 70% of respondents face challenges in categorizing restaurants by cuisine/type/occasion
    • 50% find it difficult to manage a growing number of entries on their restaurant list
  • Information retrieval:some text
    • 60% express frustration with the current method's inability to easily search or find restaurants
    • 45% find it challenging to remember the details of each restaurant on their list
    • 35% encounter difficulty incorporating reviews or ratings into the organization process
  • Lack of centralized platform:some text
    • 55% mention the absence of a centralized platform for managing restaurant recommendations
    • 30% express dissatisfaction with the fragmentation of recommendations across different platforms
  • User interface issues:some text
    • 45% are frustrated by the limitations of current methods, such as Google Maps, in organizing and accessing restaurant information
    • 25% find it inconvenient to view or sort through notes or other saved information related to restaurants
  • Appetite for recommendations:
    • 35% express interest in receiving new restaurant suggestions, particularly when similar types of restaurants open in their area

Note that the above observations are based on responses from 65% of survey participants, as 35% do not store information about restaurants they want to try on their phones.

Feedback

The pain points identified during interviews and from online surveys reflect common challenges faced by users when managing and accessing restaurant recommendations, highlighting the need for a solution that offers efficient organization, easy retrieval of information, a centralized platform, a user-friendly interface, and personalized recommendations.

Learnings

Product Manager Learnings:

Judo Tanatitiyotin

This product management journey has been incredibly eye-opening. It is rewarding to see your idea coming to life. I 100% agree with the learning-by-doing concept. We learn so much more, and it is so practical to implement what you heard in your work. This immersive approach has proven far more impactful than passive learning methods like watching videos or taking notes. I feel like I am already a product manager.

I have always been driven by a desire to improve processes and outcomes. This has often led me to jump into crafting solutions and get excited to create something new. However, through this program, I have come to appreciate the importance of first understanding the underlying problems and needs before diving into solutions.

As I’m currently a project manager in IT, I always, by default, focus on the execution of tasks to deliver an outcome. Product management solidifies my strategic thinking. It is important to understand the why before getting the what done.

I can't wait to see where my side project will lead me. Keep an eye out for MUNCH!

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