owned this note
owned this note
Published
Linked with GitHub
# Drunk safe
## Qualitative interview guide
**Introduction**
We are a group of 5 students who are developing a project called : Drunk safe. This application enables to detect when you're drunk. It detects weird behaviors like sending text to a certain group of people you've defined before, not walking straight or stalking on social media. In this world, the technology will be advanced enough to calculate correctly those parameters and help drunk people to reach their home thanks to ubers or taxis automatically ordered. It can send messages to friends if the person is too drunk and needs help.
The purpose of this test is to test our app.
Feel free to ask questions and to comment.
Q1:Hi, how are you?
Q2:What is your current situation : For example Student? Employee?
Q3:How old are you?
**General information related to the topic**
*Query the tester with general questions. Talk about his habits.*
Q4: Have you ever been in a situation of drunkenness to back home after a party? If so, how often?
Q5:Is the return journey something that scares you? Do you feel in danger when you are drunk? If so, why?
Q6: In this kind of situation do you do things you regret afterwards? (For example call your ex etc)
**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:Do you find the application useful? Does it meet the need for a benevolence service caring of drunk people? Why?
Q8:Do you find the application easy to use and instinctive? At what stages of the prototype could it be improved?
Q9:What features do you think are inappropriate? Moreover, in your opinion, are there any missing features?
**Constructive suggestions for improvement**
*Ask him how you could improve your prototype*
Q10:According to you, how could we improve our prototype?
:::
---
:::warning
## Testcard 1
## Pre-testing
**Name:** Antoine Bert
**Age:** 18
**Occupation:** Student
** The meeting took place in a café in Lyon, 24th of November. **
**Duration of the meeting:** 25min
## User scenarios testing
**1st instruction** (this is your first scenario):
You are on the application and you are trying to call a taxi to come back home, how do you do?
**Observations:**
Antoine found directly reached the appropriate feature without making any mistake in his navigation.
---
**2nd instruction:** (this is your second scenario):
You are on the application and you are trying to give a tips to your taxi driver who gives you a feedback of your behabviour?
**Observations:**
He found that the sentence "give a extra tip to your driver" was written too small at the bottom of the section, so his navigation was not smooth at this stage.
## Qualitative testing
**Positive feedback:**
- Antoine found the app very funny and the concept itself in general
- The navigation experience is quite smooth
- The possibility to have a feedback is very appreciated especially in case of blackouts
---
**Neutral feedback:**
- Quite funny communication style. (example : "happy hangover" etc)
---
**Negative feedback:**
- The size and the font of our titles and tabs
- The app is not sleek enough according to Antoine if our concept want to compete with other app as Uber etc
- The usefullness of the "call a friend feature" because this is something you are able to do without the app
---
**Learning & insights:**
From that, we've learn that we had to be careful in designing our app. The size of the font is crucial. We realized that it was essential to prioritize our titles and tabs.
---
**Decisions & actions:**
To iterate, we changed sizes of our titles in order to prioritize them.
After consultation we decided to keep the section call a friend.
:::
:::warning
## Testcard 2
## Pre-testing
**Name:** Michel Mercati
**Age:** 52
**Occupation:** School teacher
** The meeting took place at home, the 23rd of November. Michel is the father of one member of the group **
**Duration of the meeting:** 25min
## User scenarios testing
**1st instruction** (this is your first scenario):
You are on the application and you are trying to call a taxi to come back home, how do you do?
**Observations:**
Michel found directly reached the appropriate feature without making any mistake in his navigation.
---
**2nd instruction:** (this is your second scenario):
You are on the application and you are trying to give a tips to your taxi driver who gives you a feedback of your behabviour?
**Observations:**
He found directy the way to do this task.
## Qualitative testing
**Positive feedback:**
- Michel appreciated the relevance of the three main features : call a friend, call a taxi, where am I.
- He appreiated the pictures and the communication style in general
---
**Neutral feedback:**
- The user must allow the app to access his contacts and gps position
---
**Negative feedback:**
- The possibility to have a feedback. To the extent that the feedback is possibly paid for, the driver's feedback will necessarily be nice and unrealistic according to Michel
- The size and the font of our titles and tabs
---
**Learning & insights:**
From that, we've learn that we had to be careful in designing our app. The size of the font is crucial. We realized that it was essential to prioritize our titles and tabs.
---
**Decisions & actions:**
To iterate, we changed sizes of our titles in order to prioritize them.
After consultation we are open to rethink the "feedbakc" concept during our meeting of 27th of November.
:::success
:::warning
## Testcard 3
## Pre-testing
**Name:** Colette Roudet
**Age:** 63
**Occupation:** Retired
** The meeting took place in a meeting room 24th of November**
**Duration of the meeting:** 25min
## User scenarios testing
**1st instruction** (this is your first scenario):
You are on the application and you are trying to call a taxi to come back home, how do you do?
**Observations:**
After a while of hesitation Colette reached the appropriate feature without making any mistake in her navigation.
---
**2nd instruction:** (this is your second scenario):
You are on the application and you are trying to give a tips to your taxi driver who gives you a feedback of your behabviour?
**Observations:**
She directly reached this feature without any mistake.
## Qualitative testing
**Positive feedback:**
-
- The possibility to grade the driver
- The general navigation
---
**Neutral feedback:**
- Lot of pictures
---
**Negative feedback:**
- The size and the font of our titles and tabs
- Colette didn't identify herself as a potential user of the app. Our app is needed in too specific situations according to her.
---
**Learning & insights:**
From that, we've learn that we had to be careful in designing our app. The size of the font is crucial. We realized that it was essential to prioritize our titles and tabs.
---
**Decisions & actions:**
To iterate, we changed sizes of our titles in order to prioritize them. Even if we took note of the Colette's remark, we will do nothing about the seniors because they are not our targeted users.
:::
:::