---
# System prepended metadata

title: User testing template

---

# User testing template


## Qualitative interview guide


**General information related to the topic**
*Query the tester with general questions. Talk about his habits.*
Q4:Do you like to go to bars? 
I prefer going to pubs in town, I like their general atmosphere. They make for a better night out. 

Q5:Do you usually use ride-sharing apps to get home afterwards? 
I generally use the uber app if it is too late to take public transport and the pub is too far from where I live. 

Q6:Would you like to have an app that measures your level of alcohol intake during a night out? 
I think it would be quite handy to have an app that monitors your alcohol intake just to see how much I drink during one evening, if it can compare with a country’s legal limit to driven, this could save a few lives. 


**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?
Sometimes people under the influence think that they can take the wheel on their but just need a slight nudge in the right direction. A notification from the app, giving an account of the user’s consumption could prompt him or her to order a ride via the app. 

Q8:Would you prefer an alcohol measurement solution that would include a breathalyser or one that would analyse your payment records?
I would prefer a breathalyser as I am not comfortable with an app tracking any part of my expenses. 
If this data was safely secured then I would have less problems with this concept. 

**Constructive suggestions for improvement**
*Ask him how you could improve your prototype*
Q10:How can our app be improved? 
You could definitely use more colour and add an option that takes into account the drinks that the user may have paid for but didn’t drink. 

:::

---

:::warning
## Testcard



## Pre-testing
**Name:** Charles Chokre 

**Age:** 20

**Occupation:** Entrepreneur, Student

**Context of the meeting (where, with who, etc.):** I, Cameron, have known Charles since I was 3 years old. He is an entrepreneur and has done a conference in emlyon as an entrepreneur. His experience, to me, was crucial I order to identify what the consumer would think of our app in “first encounter” experience. 

**Duration of the meeting:** 25 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:**
He did manage to find the proper screen to add the adress quite fast. Nonetheless, he had to search through all the screens once. I think this problem could be adressed with an explanatory walk through when opening the app the first time.

**2nd instruction** (this is your second scenario):
You want to change an address because your friend has just moved. 

**Observations:**
Although the edit function was easily recognisable, you still have to go through the app as if you were ordering a car to get home. This could confuse the user if he or she is enebriated. 

---

## Qualitative testing

**Positive feedback:**
- Handy and easy to get used too
- Nice background images
- Like the process of ordering the ride, especially the Home-shortcut once explained

---

**Neutral feedback:**
- A walkthrough would be really helpful to understand all the features

---

**Negative feedback:**
- You could definetely add some more colors but I understand the concept of keeping it easy for drunk people, although seetings are not managed when drunk according to my understanding

---

**Learning & insights:** 
- We really need to improve our colors/layout to make it more appealing
- A walkthrough would be really nice for first users as although the app is user-friendly this would clear everything up, especially the shortcuts we have implemented.  

---

:::


