root
/
public
mirror of https://github.com/01-edu/public.git
14
27
Fork 0
Code Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6029 Commits
88 Branches
8 Tags
372 MiB
 
 
 
 
 
 
Tree: 2b8dd0028b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2b8dd0028b'
${ noResults }
public/subjects/user-experience/piscine-ux/going-on-holidays/README.md

14 KiB
Raw Blame History

Interview guide

Context:

Welcome to the 2nd quest.

Your mission, should you choose to accept it, is to focus on going on holidays with friends. As you may have noticed, experiencing weekends or other kinds of holidays is super nice, but may lead to some moments of irritation.

So this project’s goal is to make holidays more comfortable fo everyone. But first, as in all design processes, you need to understand the real problem behind stressful moments!

Instructions

You need to create an interview guide to get information from your user.

And remember, you are not your user!

Deliverable:

  • A PDF document with an interview guide.

Tips:

Here are the recommended steps :

  • Define your objective, what you are looking for when interviewing people. Usually, this has to do with your user's habits, and the most painful problems they have regarding this topic.
  • Write down 1 to 3 hypotheses you have regarding this topic, that needs to be either confirmed or disproved.
  • Pick 3 to 5 main topics you need to get information on.
  • For each topic, write 1 to 3 open-ended questions with a maximum of 10 questions. Remember, your user cannot answer with “Yes” or “No!” Ex: How, Why, What, When, Tell me about the last time you did... etc. If you really need to introduce a new topic by a close-ended question, ask why right after.
  • Write some screening questions to have a few pieces of demographics (age, job, location, etc.)
  • Structure your questions in a funnel, start with broad questions to focus on specific topics or situations. Remember to stay neutral in your tone to let the user tell their own story. Try to focus on 10 main questions.
  • Write a greeting introduction, describing briefly (1) who you are and (2) what you are looking for. No need to say too much, but enough to provide a framework and the purpose of the interview.
  • Write a conclusion to thank your user for their time, and prepare the next steps. Ex: ask to be put in touch with someone they know and who could be interested in this topic, etc.
  • Upload the PDF document on Github, labeled as follows: “Name_FirstName_DeliverableName_Date_VersionNumber”. For example, it can be labeled as “Doe_John_MidFiPrototype_05242024_V1”.
  • Add a title within the document.
  • Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration canva but don’t overload your design with too much details!

Resources:

Quote:

“To ask open-ended questions is the best approach, but it’s easy to get into the weeds in data analysis when every answer is a paragraph or two of prose. Users quickly tire of answering many open-ended questions, which usually require a lot of typing and explanation.” Norman Nielsen Group

Run interviews

Instructions

You must run 6 interviews in pairs, one being the interviewer and the other the note taker. Go outside! Meet random people in cafés, at the bus, on city squares, in parks, on benches, introduce yourself and ask for 15 minutes of their time. Run your interview guide and write down anything that could be helpful, like reactions, hesitations, etc. You can use a dictaphone to make sure you're not missing anything. But in this case, let the interviewee know and ask for their permission! You can offer them a coffee to thank them, sometimes a smile suffices! At least 3 of your interviews must be with strangers. You'd be surprised how people are happy to help and looooove talking about themselves.

Then, write down the script on a written document, and give elements of context regarding each interview (place, time, name, etc.)

  • Upload the PDF document on Github, labeled as follows: “Name_FirstName_DeliverableName_Date_VersionNumber”. For example, it can be labeled as “Doe_John_MidFiPrototype_05242024_V1”.
  • Add a title within the document.

Deliverables

  • A PDF document with the scripts from all the 6 interviews.

Tips:

  • Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration canva but don’t overload your design with too much details!

Affinity diagram & Empathy map

Instructions

Open your written scripts and extract the relevant information.

  1. Use paper or digital sticky notes (Post-its or Miro.com) to isolate the pieces of information your interviewees shared with you.

    1 idea, quote, or piece of information = 1 sticky note.

  2. When all your scripts are written/typed down on sticky notes, gather them in clusters based on themes, opinions, habits, or anything they could have in common.

  3. Label the clusters.

  4. Draw conclusions.

  5. Fill an empathy map ONLY with the content from your affinity diagram.

Don't forget to:

  • Upload the documents on Github, in a zip folder named “ProjectTitle_Name_FirstName”, with all project deliverables as follows: “Name_FirstName_DeliverableName_Date_VersionNumber”. For example, the first deliverable can be named as “Doe_John_MidFiPrototype_05242024_V1”.
  • Add a title within all written documents.

Deliverables

  • An Affinity Diagram (pictures of the Affinity Diagram on paper or on digital tools like Miro)
  • An Empathy Map (pictures of the Empathy Map on paper or on digital tools like Miro)

Tips:

  • Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration canva but don’t overload your design with too much details!

Resources:

Quote:

Remember, you are not the user, so your opinions are not absolute truth.

Problem statement

Instructions

Based on your previous work and your empathy map, define a problem statement that would clarify the main problem you want to tackle.

You may use the "How Might We" exercise in pairs.

  • Upload the PDF document on Github, labeled as follows: “Name_FirstName_DeliverableName_Date_VersionNumber”. For example, it can be labeled as “Doe_John_MidFiPrototype_05242024_V1”.
  • Add a title within the document.

Deliverable:

  • A PDF document with a problem statement starting with a "How Might We"

Tips:

  • Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration canva but don’t overload your design with too much details!

Resources:

Quote:

"Out of clutter, find simplicity. From discord, find harmony. In the middle of difficulty, lies opportunity.’ Albert Einstein

Ideation

Instructions

To find creative solutions to your problem statement, use one of these techniques in groups of 5 people, twice.

  1. Gather in groups of 2. During the first run, one is the facilitator and the other is the time-keeper and in charge of logistics. Switch roles for the second run.

  2. Get as many ideas as possible within a defined timeframe, and narrow them down to 3 main ideas with a voting process (in pair or in group). Take pictures!

Don't forget to:

  • Upload the documents on Github, in a zip folder named “ProjectTitle_Name_FirstName”, with all project deliverables as follows: “Name_FirstName_DeliverableName_Date_VersionNumber”. For example, the first deliverable can be named as “Doe_John_MidFiPrototype_05242024_V1”.
  • Add a title within all written documents.

Deliverables

  • A PDF document that includes the script with all the steps + logistics.
  • Pictures of the 2 sessions.
  • A PDF document with 3 ideas that came out the 2 workshops.

Tips:

Ideation techniques:

  • Worst Idea
  • Brainwriting
  • Mash Up
  • As to the script, you can refer to "Athlete, keep hydrated" Quest, Ideation Exercise.
  • Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration canva but don’t overload your design with too much details!

Resources:

Quote:

  • "Brainstorming means using the brain to storm a creative problem. Do so in commando fashion, with each stormer attacking the same objective.’ Alex Faickney Osborn

User flow

Instructions

Structure your main ideas into a comprehensive user flow. You can include one, two, of the three main ideas from your previous exercise "Second Ideation" process, depending on how consistent it would be for the users.

Don't forget to:

  • Upload the documents on Github, in a zip folder named “ProjectTitle_Name_FirstName”, with all project deliverables as follows: “Name_FirstName_DeliverableName_Date_VersionNumber”. For example, the first deliverable can be named as “Doe_John_MidFiPrototype_05242024_V1”.
  • Add a title within all written documents.

Deliverable:

  • A comprehensive user flow on a board (digital or pictures of a paper version).

Tips:

  • Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration canva but don’t overload your design with too much details!

Resources:

Quote:

"Each use case is represented as a sequence of simple steps, beginning with a user’s goal and ending when that goal is fulfilled.’ Usability.gov

Prototyping

Instructions

Give another dimension to your user flow and turn it into a paper prototype (6 to 12 screens max).

  • First, draw low-fidelity prototypes on paper. One main screen = 1 mobile frame. No micro-interactions nor multistate are needed for this exercise.
  • Test the prototype with 3 people. To do so, prepare a usability testing guide following the Design Sprint Five-Act interview
  • Then, draw your mid-fidelity screens on Figma with simple shapes, in black and white.
  • Upload the documents on Github, in a zip folder named “ProjectTitle_Name_FirstName”, with all project deliverables as follows: “Name_FirstName_DeliverableName_Date_VersionNumber”. For example, the first deliverable can be named as “Doe_John_MidFiPrototype_05242024_V1”.

Deliverables

  • Pictures of a paper prototype.
  • Figma file with the Wireframes (mid-fi).

Tips:

  • Low-Fidelity: Paper Prototypes - Example here
  • Mid-Fidelity: Wireframes - black and white, only the main elements, on digital prototype tools - Example here
  • High-Fidelity: Wireframes with color, styles, graphical details, and micro-interactions - Example here

Resources:

Quote:

Any design is like a joke …if you have to explain it, it’s bad.