---
# System prepended metadata

title: User testing template

---

# User testing template

## Qualitative interview guide

**Introduction**
*Introduce yourself, briefly explain the purpose of the test and allow the participant(s) to comment or ask questions.*
Q1:What is a wireframe?
A wireframe is a basic visualization of our app idea. It helps to create a desgin idea of how our application could look like.
Q2:What is the purpose of the test again?
We are trying to get some feedback to see how user-friendly and intuitive the app screens are that we have created. 
Q3:What is the app about?
We've created an app for beer-lovers, party people who love to go out but don't want to worry about how to get back home. The app will make it as easy as possible since it combines the 2 steps of figuring out if we are still able to drive and when this is not the case how we will get to the place wherever we want to go. This will be as easy as possible for you as you can define destinations and mode of transportations beforehand so that you don't have to worry about such things when you are drunk. 

**General information related to the topic**
*Query the tester with general questions. Talk about his habits.*
Q4:Do you like to go to bars?
Yes, I love to go out with friends and have fun but bars are quite expensive so I usually pre-drink to save some money as I am a poor student. 
Q5:Do you frequently use ride-hailing apps like uber?
When going out and it is after 4am/5am and hence no bus is running anymore I occasionally take an uber as it is the easiest option, especially when it is cold outside. 
Q6:Would you find an application that determines your blood alcohol level automatically useful?
It would be definitely interesting to observe my blood alcohol level when going out but it would not be of great relevance for me as I don't drive anyways. 

**Behavior related to particular issues**
*Ask him to express himself on your application, product or service. Feel free to use the prototype for this part.*
Q7:How do you like the general idea of our application to combine the measurement of your capability to drive with the possibility to order a ride if that is not the case?
It is an easy and fast solution for those who've arrived with a car. I feel like it could reduce drunk-driving accidents. 
Q8:Would you prefer an alcohol measurement solution that would include a breathalyzer or one that would analyze your payment records?
Definitely a breathalyzer because I can buy drinks for my friends too and this would then falsify the results.
Q9:What if we'd offer a solution where a pop-up screen would recognize the payment in a bar and you would have to enter the number of drinks and the number of people for which you bought them? I am thinking of a solution where you would have a logo of beer, wine, hard alcohol, shoots and then the number of people on the left and a number on the right which you could increase with a + sign and decrease with a - sign. So quite simple.
Still the breathalyzer because then I'd have to monitor my app everytime I buy something which would be quite annoying. And what about the times someonelse buys me a drink?

**Constructive suggestions for improvement**
*Ask him how you could improve your prototype*
Q10: How could we improve the prototype?
Definitely the colors. There is way too much gray for me. 
:::

---

:::warning
## Testcard



## Pre-testing
**Name:** Tonia Bollin

**Age:** 23

**Occupation:** Student

**Context of the meeting (where, with who, etc.):** I, Konstantin, went ahead to interview my girlfriend about our mockup because, yes obviously it is convenient, but also because she is quite critic. She is also quite creative and generally better in such tasks so I hoped to get some valuable points out of that.

**Duration of the meeting:** 40 minutes



## User scenarios testing

**1st instruction** (this is your first scenario):
You are on the home screen now where we would display your blood alcohol level and tell you if you are able to drive. How would you add an adress?

**Observations:**
She did succesfully arrive at the screen where she could monitor the adresses the first time trying. So that is good news. However, she was nonetheless uncertain for a moment if she should go via the maps screen. Furthermore, she was uncertain for a moment between "Favorite adresses" and "Favorite transportation" as the word favorite kind of threw her of. In her opinion the favorite is obsolete as you'd obviously only save your favorite adresses. So "Adresses" would be just fine. Another suggestion was "Administer adresses" or "Manage adresses". I also observed that she did not now how to get back to the "Home" screen at first as she didn't make the link to the alcohol level sign on the bottom left.

---

**2nd instruction:** (this is your second scenario):
You want to get back home now. Order yourself the ride.

**Observations:**
She managed this task quite fast and pressed the right buttons. However, once she arrived on the final "Choose the ride!"-screen, she felt like the final "Go to Home" button on the bottom was obsolete and rather irritating. She tried at first to just press on "Uber", "Heetch" or "Mom's Car" to order the ride. We might change this. We would just have to implement a final pop-up which assures that the user did not type on one of the transportation modes by accident but really wants to order a ride.   



## Qualitative testing

**Positive feedback:**
- The "Maps"-screen really looks quite cool and authentic
- It is overall still quite clear und user-friendly
- Easy to move around in application and to get used to it

---

**Neutral feedback:**
- The background could be changeable/costumizable
- Could be more personalized/fun greeting the user on the first page for example
- Idea for business concept: Partner with ride hailing companies like uber that once someone calls a ride when to drunk to drive, he/she will gain some points to eventually get some rebates on rides
- Possible adress synchronisation with contacts in your phone?
- Voice recognition/Conversation like app asking you "Should I call a ride?" "Yes" "Where do you want to go?" "Home" "Which ride do you want to take?" "Uber" "Do you want me to call the ride now?" "Yes"

---

**Negative feedback:**
- The colors should be more positive, too much grey
- Icons to switch screens on bottom are easily understandable but could be prettier
- the "click .." on the "Add adress"-screen unnecessary.

---

**Learning & insights:** 
From that, we've learn that ...
- We need to be more precise in our choice of words for the actions/descriptions
- The final screen for ordering the ride can be made easier and more intuitive
- We still need to work on the graphics so that it is not only easily understandable but also visually appealing

---

**Decisions & actions:** 
To iterate, we will make ...

- Adapt the "Choose your ride"-screen
- Work on the icons & colors
- Make the text more easy & intuitive to understand
---
:::


