Problem Statement
The lack of a nutritional guide at Kanbar cafeterias makes it difficult for the students to decide what to eat. It causes problems for students' health. With a busy schedule and not having the time to cook food, the student ends up eating in the cafeteria and fails to balance the nutrition. This application will have all the nutritional information about all the meals served in the cafeteria. Students can easily filter out food that they are allergic to. They can also track their meal nutritional value. There are many more features that will help students make beer choices in their eating habits.​
Design Strategy
To start with, we used the Element and Anatomy method for the design process. We went layer by layer to cover every bit of the aspect.
This is an outline seeking to define key considerations that go into development and UX.
This was a very helpful method to understand every layer of the design process.
Affinity Mapping
Affinity mapping helped me Identify relationships between groupings and find informative content.
The goal was to create a credible story of why elements are related and to gain a complete picture of user needs.
Research
To understand our users better we did around 10 interviews and 15 surveys. Following were some insights from the observations:
-
4 out of 10 people are too shy to ask the chef questions
-
6 out of 10 people assess the food by just looking at
-
People walked back and forth between counters
-
People had to re-ask the chef the same questions
-
People were pointing at the food, instead of calling it by the proper name
Journey Mapping
Based on user research, understanding the user mindset and deciding the user journey from point A to point B was the goal. Beginning from feeling hungry to getting the food of his choice. I went through a lot of discussions and alterations. Finally, this is the outcome of the journey mapping.
Persona
Based on the research and workflow, we straight-dived into our personas. We took 3 different situations that students go through. And we jotted down their backgrounds, goals, motivations, and frustrations. That gave us a clear picture of what areas we should focus on solving.
Wireframes
This is the first draft of the wireframes. This helps to decide the design structure. After the first attempt at the wireframes, I did some user testing. I was noting down how the user is understanding the flow. As per the suggestions and feedback, I made re-designed the wireframes again and finalized the design.
