(2) Conduct (at least) 3 formative usability tests.

script for usability test

Hinweise für den User:

Wir testen die App, nicht dich! Fragen bitte gerne stellen, ich kann aber nicht versprechen, alle Fragen direkt zu beantworten! Wir werden eine sogenannte think-aloud Methode nutzen, die uns dabei hilft, herauszufinden, was noch an unserer App verbessert werden kann.

Kontext der Anwendung erklären:

Foodie ist eine App, die dir hilft, deine Mahlzeiten zu planen und einfacher Rezepte, die perfekt auf dich zugeschnitten sind, zu finden. Besonders hilfreich ist die App für Menschen mit Nahrungsunverträglichkeiten oder mit restriktiven Diäten. Dazu gibt es einen Nahrungsmittelfilter, der die unverträglichen Substanzen direkt aus der Suche streicht und dir nur Rezepte, die du auch essen kannst, anzeigt. Des Weiteren gibt es die Möglichkeit Gruppen zu erstellen und Gerichte für diese Gruppe rauszusuchen, hier werden auch die verschiedenen, von den Nutzern ausgewählten, Unverträglichkeiten direkt angezeigt.

Szenario:

Stell dir vor, du bist vegetarier und eine Apfelallergie, kochst gerne und bist oft frustriert, dass dein ausgewähltes Rezept doch noch nach Schinkenwürfeln fragt nachdem du dich darauf gefreut hast das zu machen und du dir danach ein neues Rezept raussuchen musst. Jetzt hast du die neue App Foodie empfohlen bekommen und willst sie ausprobieren, du hast dir einen Account erstellt und benutzt jetzt die App zum ersten Mal.h

Aufgaben:

• Beschreibe was du siehst und deinen ersten Eindruck.
• Was wären deine ersten Schritte, um ein geeignetes Rezept zum Kochen zu finden?
• Wie wäre deine Vorgehensweise, um deine Unverträglichkeiten bzw. deine Ernährungsform einzustellen?

Abschließende Fragen:

• Welche Vor- und Nachteile siehst du grundsätzliche bei der Foodie-App?
• Stell dir vor du könntest ein Feature bezogen auf die Rezeptsuche-Funktion verbessern, was wäre das und wie würdest du es verbessern? Warum?
• Mit welchen Leuten könntest du dir vorstellen eine Gruppe zu erstellen? Freunde oder doch eher nur Haushalt? 

Abschluss:

• Hast du weitere Fragen oder Anmerkungen?
• Vielen Dank für deine Teilnahme! Du hast uns sehr geholfen.

Who is taking what role

Nirmin und Janis führen das Interview während Rike Notizen schreibt.

Who do we invite to our testsession

• Usability Test #1:
  • Erik, 25 Jahre alt, kocht gerne, Flexitarier und mag keine Pilze
  • Interviewdauer: 14:05-14:25 (20 Minuten)
  • Interview durchgeführt von Janis

• Usability Test #2:
  • Rama, 20 Jahre alt, probiert gerne neue Gerichte aus und folgt keiner bestimmten Ernährungsform
  • Interviewdauer: 14:55-15:15 (20 Minuten)
  • Interview durchgeführt von Nirmin

(3) Document and evaluate the results of your testing.

Wir haben uns dazu entschieden nur schriftliche Notizen zu machen und diese im Nachhinein in ein Affinity Diagramm umzuwandeln.

Zuerst haben wir die gesammelten Notizen Personenweise aufgelistet.

Als nächstes haben wir die Notizen unter den Kategorien „Features“, „Design“ und „Ideen und Verbesserungsvorschläge“ jeweils in Pro und Contra einsortiert, um die noch vorhandenen Probleme besser zu veranschaulichen.

What did we learn and what are the main takeways

Wir haben gelernt, dass die Grundrichtung in die wir gehen gut ist, allerdings der unfertige Prototyp öfter für Verwirrung gesorgt hat, da noch nicht alle Features nutzbar waren. Dass der Einstellungsbutton nicht klick bar war, führte dazu, dass ein Tester nicht sicher war wie er sein Profil bearbeiten kann. Erst nach genauerem betrachten des Prototyps ist der Tester auf das Profil-Icon aufmerksam geworden wodurch er zur Profileinstellung gelangte.

1. Hypothesis Statement and Problem Statement

Hypothesis Satement

We believe that by implementing an ingredient filter and the possibility to memerize the unused ingredient for Leroy we will achieve more satisfaction in the recipe suggestions, more time savings, and less stress while searching for recipes.

Problem Statement

Leroy needs a way to filter his recipes for ingredients because he suffers from a serious lactose intollerance and an apple allergie and is too busy to spend much time in research for suitable recipes. We will know this to be true when we see him being more motivated to try out new recipes because its easy for him to find them.

2. Conceptual Models for task analysis

We decided to use  Business Process Modeling Notation (BPMN) as the way to illustrate our taskflow. The main reason was, that we need to display many decisions the user has to make to get to the wanted result. BPMN seemed to be a good and simple solution for that and also manages to show it in a more clean manner than other diagram types.

Moodboard

Sketches

Storyboard

1. Affinity Diagramm

Our questionnair includes 23 questions out of five categories. The categories are „Food planning“, „Grocery shopping“, „Cooking“, „Leftovers“ and „App“. Since we already had this presorting we started our affinity diagramm by listing the given answers to the categories in different colors.

Illustrating the answers with the different colors and headers helped us realizing, that we need to rethink which answers are really important for the diagramm. We cut out the time expenditure subheaders and were able to categorize the answers to four groups.

2. Primary Persona

The primary persona is based on our semi-structured interview. The main features of this person is the love for food but also the struggle of finding recipes that fit to the food tolerance and the prioritized diet. The other struggle this persona has is to minimize his wasted leftovers and cooking ingredients.

3. Extreme Character

Our extreme persona is a mother of two. Money is short and she struggles to prevent her kids a healthy and balanced diet. Another challenge for her is the food intolerance of her child.

4. Scenario

Our scenario is based on the persona of task 3.

Every day Leroy wakes up and first thing in the morning is coffee and a slice of freshly baked bread. The bread is from a local bakery specialized on sourdough bread. His favourite.

After the coffein has started his effect he’s headed to his desk at home. Work calls. For the next 2-4 hours he will sit here and answer calls and do paper work.

Work is done and he slowly gets hungry again. The same question as every day comes to his mind „What’s for lunch„. He has some stuff in his fridge but isn’t exactly sure what to do with it. He starts searching on cooking websites for ideas. It takes him about 20 minutes until he found something he likes to eat (and doesn’t contain ingredients he is allergic to) on that day. The recipe doesn’t contain any ingredients of the things he already has at home so he has to go grocery shopping as he has to most days.

Next thing he does is writing a list for his grocery shopping. He writes it on his phone. The shopping trip will be fast, because he exactly knows what to buy and where to find it.

He’s still a bit exhausted after the workday and his shopping trip, but gladly he chose a recipe that will only take about 30 minutes with preparation. He cuts the vegetables, and puts half the brokkoli into the fridge. He will use it next time. (He didn’t use it next time. He threw it away a week later with half a lemon, a quarter onion and a green pepper that came in a package of 3 different colored peppers.)

The food tasted great and he emptied it on the same evening.

5. Use Case Diagramm

We decided to create four Use Case Diagrams. One for the case that someone just wants a recipe for the current day, one for the case that the person likes to get inspired (This is supposed to be daily changing recipe ideas) and one for the case that soemone wants to plan food for the whole week. The fourth diagramm shows the whole basic process with and without an account.

The first three Use Case diagrams show the process for users without a profile. If the user decides to create an account the filters don’t have to be specified every time. It will be saved in the settings chosen when creating the account.

Who is your user group?

Our user group includes cooking enthusiasts who like to minimize their waste of leftover cooking ingredients and need some food inspiration as well as some help to organize the weekly shopping list. Stakeholders might be grocery stores, cookbook authors and publishers.

What is the exact problem?

It is difficult to use leftover cooking ingredients without having a matching recipe. Another challenge is to find the time to think about possible recipes due to work or study time restrictions. People with allergies or people who follow a specific diet have to manually filter out certain ingredients

Where is your user group interacting with your software?

Mostly at home, but it’s also possible to interact with the software while they are on their way home or to the supermarket.

When is the user group interacting with your software?

During meal planning.

Why do your users need this software? Why is that interesting?

Now that a lot of people are working or studying from home the need of having home cooked meals increases. However, many don’t have a lot of different recipes in their repertoire so the need to find different recipes increases. Many apps have countless recipes which means it can be hard to choose exactly the one you want, and it gets even more frustrating if after choosing one you see that one of the main ingredients is exactly the one you are allergic to or aren’t allowed to use based on your current diet.

How do you want to solve the problem?

We want to create a mobile app that provides the user with recipe ideas, that can be filtered by ingredients they already have at home and ingredients they don’t want in their meal. The app also supports the user by automatically creating a shopping list for all the chosen meals while excluding the ingredients that are already available.