Fontys presents Jumbo, Whats for dinner?

Project description

Our project aimed to address the challenge presented by Jumbo: improving the in-store shopping experience by bringing online and offline experiences closer together. Building upon insights gained during the Jumbo Hackathon, our focus was to assist customers in deciding what to eat while simultaneously reducing store waste. The core idea involves providing personalized recipes within the Jumbo app

Context

Jumbo is a grocery store chain in the Netherlands and Belgium. They have physical stores and also offer online grocery shopping. Their main focus is putting customers first and involving them in developing new ideas and features. They want to offer affordable groceries and are working on digital products in their tech department. They believe in innovation to stay ahead in the competitive market.

Jumbo is trying to make the online and in-store shopping experiences more similar. People who shop online with Jumbo are loyal, but those who shop in the physical stores tend to also go elsewhere. Jumbo wants to bring their online and offline experiences closer together (clicks and bricks), because Jumbo wants to make people who shop in stores just as loyal as those who shop online.

Two of our team members previously attended the Jumbo Hackathon, where they worked on a challenge. During the event, they noticed additional problems that could be solved to enhance the shopping experience. These included helping customers decide what to eat and reducing store waste.

For this project we're building on the idea they created during the hackathon. The idea is to improve the in-store shopping experience by offering customers personalized recipes based on their behavioral data, diet preferences and the stock level of in-store perishables. This will bring offline and online shopping closer together and make in-store shopping more enjoyable, all while helping people answer the question, "What’s for dinner?" as well as the “How can we reduce waste?” question

Results

We had three main deliverables (products) at the end:
- Kiosk
- High Fidelity Prototype
- MVP Web application

The kiosk allowed us to collect critical user feedback and insights based on the customers that shop at Jumbo that prefer to not use their smartphone to plan recipes. Some key insights we picked up on are:
This is a good first step to make customers aware of this concept.
It helps people in the store with figuring out what to eat for dinner.
It is very easy and fast to use.

With the high fidelity mobile prototype, we were able to isolate user preferences and eliminate challenges that they might face while using an application designed to offer them personalized recipes. Through the multiple iterations and user tests we were able to come up with a final version that accurately represents what users want.
We learned that users

- Really care for the fact that it is personalized and fits with the things they like.
- Are invested in the things they saved and want to easily access it.
- Like the personalized categories and the personalized filtering options.

With existing recipe data provided by our client, we were also able to identify and visualize trends in the nature of the recipes, such as graphs of prep and cook time, allowing us to formulate a list of predetermined recipe categories where ranges of these were used.

By creating the web application, we proved that our concept was possible and coherent. It serves as a platform to give our client validated ideas not just as theoretical designs but as features they can feasibly implement into their existing application. With the version controlled source code, It also provides useful value to our client in terms of how they might implement such features. By our estimates, this puts the concept at a Technology Readiness Level position of 6.

Joran, our client representative from Jumbo, and our teachers expressed enthusiastic approval during our final project presentation. They commended the practicality and user-friendly design of our kiosk, high fidelity prototype, and MVP web application. They especially appreciated the way we showed off our kiosk and the app.

About the project group

Our project group embraced a collaborative and agile approach, working in sprints with a duration of two weeks. Leveraging the Notion platform, we organized and tracked our tasks efficiently, ensuring clarity and accountability within the team. The last day of each sprint marked a crucial milestone, as we engaged in a feedback and progress review session with Joran, a key stakeholder from Jumbo. These meetings provided valuable insights and shaped the direction of our work.

We worked every Monday, Tuesday and Thursday for the duration of 3 months.

Our diverse backgrounds, spanning hardware, software, and design, enriched our problem-solving perspectives. By combining our skills, we fostered creativity and innovation, ensuring a well-rounded and comprehensive solution for the project.
We had regular daily standups where we would showcase our work and give feedback on it.

Repository

https://github.com/danielvaswani/jumbo-dxd-app