mirror of https://github.com/01-edu/UX-UI.git
miguel
2 years ago
113 changed files with 2031 additions and 1651 deletions
@ -1,44 +1,38 @@
|
||||
# UX I - Ex 2 - Analytics |
||||
## Analytics |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Read these articles and extract at least 5 key figures or insights that may be useful in understanding what athletes or sport practicing people experience related to hydration. |
||||
Read these articles and extract at least 5 key figures or insights that may be useful in understanding what athletes or sport practicing people experience related to hydration. |
||||
|
||||
**Deliverables:** |
||||
|
||||
- On a PDF document, write at least 5 key figures or insights you extracted from the articles. |
||||
Each insight or key figure should be justified by a quote and the title of the article. |
||||
- On a PDF document, write at least 5 key figures or insights you extracted from the articles. |
||||
- Each insight or key figure should be justified by a quote and the title of the article. |
||||
- Upload the 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
|
||||
### Deliverables |
||||
|
||||
**Resources:** |
||||
|
||||
- [The effects of Hydration on Athletic Performance](https://sportscardiologybc.org/the-effects-of-hydration-on-athletic-performance/) |
||||
- [Dehydration and its effects on performance - Human Kinetics](https://us.humankinetics.com/blogs/excerpt/dehydration-and-its-effects-on-performance) |
||||
- [Accuracy of Urine Color to Detect Equal to or Greater Than 2% Body Mass Loss in Men Journal of Athletic Training](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4741257/) |
||||
- [Fluid replacement for the physically active - Journal of Athletic Training](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5634236/) |
||||
- [The importance of hydration - Harvard School of Public Health](https://www.hsph.harvard.edu/news/hsph-in-the-news/the-importance-of-hydration/) |
||||
- [Fluids and hydration in prolonged endurance performance - Pubmed](https://pubmed.ncbi.nlm.nih.gov/15212747/) |
||||
|
||||
- A PDF document. |
||||
|
||||
**Tips:** |
||||
|
||||
Examples of insights you can extract from the articles: |
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration on [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
Examples of insights you can extract from the articles: |
||||
|
||||
- Symptoms of dehydration can be headache, dizziness, nausea, lightheadedness, or fatigue. |
||||
- People experience dehydration when they lose 2% of their body mass loss (BML) in fluids/water/sweat. |
||||
- Sweat helps the body to maintain optimal body temperature. |
||||
- Sprint athletes are generally less concerned about the effects of dehydration than are endurance athletes. |
||||
- Etc... |
||||
|
||||
It's on you to find other and more! |
||||
|
||||
**Quote:** |
||||
|
||||
Always base your decisions on the data, not on your biases. |
||||
**Resources:** |
||||
|
||||
- [The effects of Hydration on Athletic Performance](https://sportscardiologybc.org/the-effects-of-hydration-on-athletic-performance/) |
||||
- [Dehydration and its effects on performance - Human Kinetics](https://us.humankinetics.com/blogs/excerpt/dehydration-and-its-effects-on-performance) |
||||
- [Accuracy of Urine Color to Detect Equal to or Greater Than 2% Body Mass Loss in Men Journal of Athletic Training](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4741257/) |
||||
- [Fluid replacement for the physically active - Journal of Athletic Training](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5634236/) |
||||
- [The importance of hydration - Harvard School of Public Health](https://www.hsph.harvard.edu/news/hsph-in-the-news/the-importance-of-hydration/) |
||||
- [Fluids and hydration in prolonged endurance performance - Pubmed](https://pubmed.ncbi.nlm.nih.gov/15212747/) |
||||
|
||||
**Quote:** |
||||
|
||||
Always base your decisions on the data, not on your biases. |
||||
|
@ -1,8 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Are there at least 5 insights from the articles? |
||||
|
@ -1,11 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Are there pictures of the session? |
||||
###### Is there a board with all the ideas (on paper or digitally on Miro or Figma)? |
||||
###### Is there one main idea to solve the problem? |
@ -1,33 +1,38 @@
|
||||
# UX I - Ex 3 - Personas |
||||
## Personas |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
- Create a user persona based on several users from the same category |
||||
|
||||
**Deliverables:** |
||||
|
||||
- A user persona on a PDF document |
||||
- Create a user (Pierre) persona based on several users from the same category. |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
Use the material you got from the exercise `User interview` to build the pierre persona. The following must be present in the document: |
||||
- Pierre's persona card with a picture. |
||||
- A quote extracted from the interview scripts. |
||||
- A description of Pierre that is a mix of Joe, Nathan, Guillaume, and Anaelle’s stories. |
||||
- He must have at least 2 goals, habits and frustrations. |
||||
- Insights from the exercise `User interview` must be included in Pierre's persona card. |
||||
|
||||
### Deliverables |
||||
|
||||
- A user persona on a PDF document. |
||||
|
||||
**Tips:** |
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration on [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
- You may use Figma and extract a PDF document out of it. |
||||
- Use the material you got from exercise 1. |
||||
- Detect people who face the same kinds of problems and group them. |
||||
- When you find 2+ people who face the same kind of problem, you can merge their testimonials to create a persona. In this case, Joe, Nathan, Guillaume and Anaelle who run races from time to time (they have run at least one race in their life, but less than 3 times a year) and have faced dehydration problems. |
||||
- A persona is fictional: do not use one of your users’ names, but a name that is consistent with your users’ demographics and social group. In this case, we'll choose a man as 3 out of 4 are men, and Pierre as a first name so it's different (but consistent) from Joe's, Nathan's, Guillaume's and Anaelle's. |
||||
- Detect people who face the same kinds of problems and group them. |
||||
- When you find 2 or more persons who face the same kind of problem, you can merge their testimonials to create a persona. In this case, Joe, Nathan, Guillaume and Anaelle who run races from time to time (they have run at least one race in their life, but less than 3 times a year) and have faced dehydration problems. |
||||
- A persona is fictional: do not use one of your users names, but a name that is consistent with your users demographics and social group. In this case, we'll choose a man, as 3 out of 4 are men, and Pierre as a first name so it's different (but consistent) from Joe's, Nathan's, Guillaume's and Anaelle's. |
||||
- As to the age, average the ages of your selected users. In this case, 32 (Joe is 30, Nathan is 39, Guillaume is 30 and Anaelle is 29). |
||||
- The persona has to be sport-oriented, as it is the context of this research. However, broader information, like the scan info (jobs, location, etc.) are more than welcome to give more context. |
||||
|
||||
**Resources:** |
||||
**Resources:** |
||||
|
||||
- [Make your persona great again](https://uxdesign.cc/personas-e60c1c06ead1) |
||||
- [Persona, journey maps, user flow, site map, OH MY!](https://uxdesign.cc/personas-journey-maps-site-maps-and-user-flows-oh-my-e71d044b4bcb) |
||||
- [Persona framework](https://miro.medium.com/max/1400/0*RbHfR6BHhhFIENNf) |
||||
|
||||
**Quote:** |
||||
**Quote:** |
||||
|
||||
‘Focus unswervingly, on the customer’ Jesse Hertzberg | Former COO of Squarespace |
||||
"Focus unswervingly, on the customer’ Jesse Hertzberg | Former COO of Squarespace |
||||
|
@ -1,14 +0,0 @@
|
||||
#### Audit instructions |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there Pierre's persona card in the PDF document? |
||||
###### Is there a picture of Pierre's? |
||||
###### Is there a quote extracted from the inteview scripts? |
||||
###### Is there a description of Pierre that is a mix of Joe, Nathan, Guillaume, and Anaelle’s stories? |
||||
###### Does Pierre have at least 2 goals? |
||||
###### Does Pierre have at least 2 habits? |
||||
###### Does Pierre have at least 2 frustrations? |
||||
###### Are the insights from ex 1 included in Pierre's persona card? |
@ -1,42 +1,46 @@
|
||||
# UX I - Ex 5 - Problem Statement |
||||
## Problem Statement |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Based on the insights from the analytics and user interviews, comment the scope of possible problem statements. |
||||
|
||||
**Deliverables:** |
||||
Based on the insights from the exercises `analytics` and `user interviews`, comment the scope of possible problem statements. |
||||
|
||||
- On a PDF document, write down one problem statement that summarizes the main problem that Pierre has when he runs. |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
### Deliverables |
||||
|
||||
- A PDF document. |
||||
|
||||
**Tips:** |
||||
|
||||
- At this stage, it’s important to focus on the problem, not on the solution! You can start tackling the problem after (re)defining it. |
||||
- Several problem statements can be possible for each persona and user journey, but for this exercise, we are guiding you towards one. |
||||
- Examples of correct problem statements: |
||||
- How might we help Pierre (or your persona) measure and prepare his hydration before a race? |
||||
- How might we make sure Pierre doesn’t get dehydrated? |
||||
- How might we make sure Pierre drinks the cups that are offered during the race? |
||||
- How might we provide Pierre some drink that contains everything he needs to avoid dehydration? |
||||
- How might make sure Pierre doesn’t get drunk the night before the race? |
||||
- Examples of wrong problem statements: |
||||
- How might we make sure Pierre doesn’t get dehydrated? |
||||
- Too broad —> The problem statement is out of the scope of running, so the solutions cannot be integrated in the specific context of running. |
||||
- How might we make sure Pierre drinks the cups that are offered during the race? |
||||
- Too narrow —> There are plenty of options to avoid dehydration without drinking the cups that are offered during the race. |
||||
- How might we provide Pierre with a drink that contains everything he needs to avoid dehydration? |
||||
- Focused on the solution, not the problem —> The problem statement is supposed to rephrase the brief and take into account the insights from the previous phase. |
||||
- How might make sure Pierre doesn’t get drunk the night before the race? |
||||
- Out of scope —> This is not about dehydration, nor about running. |
||||
|
||||
**Resources:** |
||||
|
||||
- Examples of a correct problem statements: |
||||
- How might we help Pierre (or your persona) measure and prepare his hydration before a race? |
||||
- How might we make sure Pierre doesn’t get dehydrated? |
||||
- How might we make sure Pierre drinks the cups that are offered during the race? |
||||
- How might we provide Pierre some drink that contains everything he needs to avoid dehydration? |
||||
- How might we make sure Pierre doesn’t get drunk the night before the race? |
||||
|
||||
- Examples of wrong problem statements: |
||||
- How might we make sure Pierre doesn’t get dehydrated? |
||||
- Too broad —> The problem statement is out of the scope of running, so the solutions cannot be integrated in the specific context of running. |
||||
- How might we make sure Pierre drinks the cups that are offered during the race? |
||||
- Too narrow —> There are plenty of options to avoid dehydration without drinking the cups that are offered during the race. |
||||
- How might we provide Pierre with a drink that contains everything he needs to avoid dehydration? |
||||
- Focused on the solution, not the problem —> The problem statement is supposed to rephrase the brief and take into account the insights from the previous phase. |
||||
- How might make sure Pierre doesn’t get drunk the night before the race? |
||||
- Out of scope —> This is not about dehydration, nor about running. |
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration on [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [Stuck on a problem? Just ask how might we](https://relab.academy/design-thinking/stuck-on-a-problem-just-ask-how-might-we/) |
||||
- [Problem statement](https://www.indeed.com/career-advice/career-development/what-is-a-problem-statement) |
||||
- [Using ‘How Might We’ Questions to Ideative on the Right Problems](https://www.nngroup.com/articles/how-might-we-questions/) |
||||
- [Using "How Might We’ Questions to Ideative on the Right Problems](https://www.nngroup.com/articles/how-might-we-questions/) |
||||
|
||||
**Quote:** |
||||
|
||||
“If I had an hour to solve a problem, I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” Albert Einstein |
||||
“If I had an hour to solve a problem, I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.” Albert Einstein |
||||
|
@ -1,9 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
##### Is the problem statement focused on the problem (and NOT on the solution)? |
||||
##### Is the problem statement narrow enough (not too broad)? |
||||
##### Is the problem statement broad enough (not too narrow)? |
@ -1,29 +1,31 @@
|
||||
# UX I - Ex 7 - Prototyping |
||||
## Prototyping |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Develop your idea! |
||||
Develop the idea you got in the exercise `ideation`! |
||||
|
||||
Design a storyboard of Pierre (or your persona) using your idea as a solution. Show all the steps (from 6 to 12) with drawings on paper. |
||||
Design a storyboard of Pierre (or your persona) using your idea as a solution. Show all the steps with drawings on paper (6 to 12 steps). |
||||
|
||||
**Deliverables:** |
||||
### Deliverables |
||||
|
||||
- Pictures of 1 storyboard to describe your solution, on paper |
||||
- 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”. |
||||
- Pictures of 1 storyboard to describe your solution, on paper. |
||||
|
||||
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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
**Tips:** |
||||
|
||||
- 1 drawing per action |
||||
|
||||
**Resources:** |
||||
**Resources:** |
||||
|
||||
- [How UX storyboards can transform your creative process](https://uxdesign.cc/ux-storyboarding-2ce43875f3de?sk=41b28ecef8c52d9944e5e636881111cf) |
||||
- [17 reasons to use storyboards in UX design](https://uxdesign.cc/17-reasons-to-use-a-storyboards-in-ux-design-2bc6fea73e20?source=friends_link&sk=5bb2722f1f9ff06d4f22b0abfe52f508) |
||||
- [How to storyboard experiences](https://uxdesign.cc/how-to-storyboard-experiences-fc051e2bc04d) |
||||
- [Using comic strips and storyboards to test your UX concepts](https://uxdesign.cc/using-comic-strips-and-storyboards-to-test-your-ux-concepts-cccad7ac7f71) |
||||
|
||||
**Quote:** |
||||
**Quote:** |
||||
|
||||
“No product is an island. A product is more than the product. It is a cohesive, integrated set of experiences” Don Norman |
||||
|
@ -1,11 +1,127 @@
|
||||
#### Audit |
||||
### User interview |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Are there at least 6 insights different from the examples given in the readme? |
||||
|
||||
###### Does each insight have the name of the person(s) who said it? |
||||
|
||||
### Analytics |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Are there at least 6 insights different from the examples given in the readme? |
||||
|
||||
###### Does each insight have the name of the person(s) who said it? |
||||
|
||||
### Personas |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is Pierre's persona card in the PDF document? |
||||
|
||||
###### Is there a picture of Pierre's? |
||||
|
||||
###### Is there a quote extracted from the interview scripts? |
||||
|
||||
###### Is there a description of Pierre that is a mix of Joe, Nathan, Guillaume, and Anaelles stories? |
||||
|
||||
###### Does Pierre have at least 2 goals? |
||||
|
||||
###### Does Pierre have at least 2 habits? |
||||
|
||||
###### Does Pierre have at least 2 frustrations? |
||||
|
||||
###### Are the insights from ex 1 included in Pierre's persona card? |
||||
|
||||
### User Journey |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (Figma)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is there a timeline within the file? |
||||
|
||||
###### Does the timeline show the journey of your persona step by step, before, during and after running a race? |
||||
|
||||
###### Is the timeline divided into phases? |
||||
|
||||
###### Are there Pierre's actions written on the timeline? |
||||
|
||||
###### For each action, is there a thought written? |
||||
|
||||
###### For every thought, is there a main emotion? |
||||
|
||||
### Problem Statement |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
##### Is the problem statement focused on the problem (and NOT on the solution)? |
||||
|
||||
##### Is the problem statement narrow enough (check the readme tips to understand narrow)? |
||||
|
||||
##### Is the problem statement broad enough (check the readme tips to understand broad)? |
||||
|
||||
### Ideation |
||||
|
||||
###### Is there a zip folder? |
||||
|
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Are there pictures of the session? |
||||
|
||||
###### Is there a board with all the ideas? |
||||
|
||||
###### Is there one main idea to solve the problem? |
||||
|
||||
### prototyping |
||||
|
||||
###### Is there a zip folder? |
||||
|
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are there all the deliverables indicated in the instructions? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are there between 6 and 12 steps? |
||||
|
||||
###### Does the solution match the idea chosen in Ex 6? |
||||
|
||||
###### Are the steps logical and does the storyboard make sense? |
||||
###### Are the drawings on paper? |
||||
|
||||
###### Are the drawings on paper? |
||||
|
@ -1,8 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Are there at least 6 insights? |
||||
###### Does each insight have the name of the person(s) who said it? |
@ -1,12 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (Figma)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there a timeline within the file? |
||||
###### Does the timeline show the journey of your persona step by step, before, during and after running a race? |
||||
###### Is the timeline divided into phases? |
||||
###### Are there Pierre’s actions written on the timeline? |
||||
###### For each action, is there a thought written? |
||||
###### For every thought, is there a main emotion? |
@ -1,31 +1,39 @@
|
||||
# UX II - Ex 3 - Affinity diagram & Empathy map |
||||
## Affinity diagram & Empathy map |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Open your written scripts and extract the relevant information. |
||||
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. |
||||
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 |
||||
4. Draw conclusions. |
||||
5. Fill an empathy map ONLY with the content from your affinity diagram. |
||||
|
||||
**Deliverables:** |
||||
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) |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [What is an Affinity Diagram and how to use it](https://miro.com/blog/create-affinity-diagrams/) |
||||
- [Affinity Diagram and Relation Examples](https://www.youtube.com/watch?v=VngWHIE4k9s) |
||||
- [Updates Empathy Map Canvas by Dave Gray](https://medium.com/the-xplane-collection/updated-empathy-map-canvas-46df22df3c8a) |
||||
- [Empathy Map by Krisztina Szerovay](https://uxknowledgebase.com/empathy-map-ca037e7686b6) |
||||
|
||||
**Quote:** |
||||
**Quote:** |
||||
|
||||
Remember, you are not the user, so your opinions are not absolute truth. |
||||
|
@ -1,20 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there an affinity diagram that is digital (on Miro) or on paper? |
||||
###### Is there an empathy map that is digital (on Miro) or on paper? |
||||
###### Are there multiple sticky notes that match with the transcription? |
||||
###### Are the sticky notes gathered in clusters? |
||||
###### Are the clusters labeled? |
||||
###### Is the empathy map filled? |
||||
###### Is the "See" section complete? |
||||
###### Is the "Say & Do" section complete? |
||||
###### Is the "Hear" section complete? |
||||
###### Is the "Think and Feel" section complete? |
||||
###### Is the "Pain" section complete? |
||||
###### Is the "Goal" section complete? |
@ -1,13 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Are there pictures of the ideation workshop? |
||||
###### Is the script consistent with the goal of the workshop? |
||||
###### Is there at least one picture of each of the workshops? |
||||
###### Is there a PDF document with there at least 3 ideas? |
||||
###### Do the ideas offer a way to solve the problem statement? |
@ -1,14 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is the main purpose of the interview written? |
||||
###### Are there 1 to 3 hypotheses? |
||||
###### Is there a proper introduction that describes the interviewer and the purpose of this interview? |
||||
###### Are there 3 to 5 main topics? |
||||
###### Are there some screening questions? |
||||
###### Are there open-ended questions, max 10? |
||||
###### Is there a funnel process (broader to more accurate questions)? |
||||
###### Is there a conclusion with next steps and a thank you message? |
@ -1,11 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is the problem statement written with a How Might We question? |
||||
###### Does it include the user's main goal? |
||||
###### Does is include the user's main pain |
||||
###### Is it narrow enough? |
||||
###### Is it broad enough? |
@ -1,15 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Are there picture of a paper prototype? |
||||
###### Are there between 6 and 12 different screens on the paper prototype? |
||||
###### Do the screens match the main steps of the user flow? |
||||
###### Are there mid-fidelity wireframes on Figma that match the paper prototypes? |
||||
###### Are the paper prototypes and wireframes in black, grey, and white and do not include any style elements?. |
||||
###### Does each screen have the main navigation elements (arrows, menu, call to actions)? |
||||
###### Does each screen follow the other according to the user flow? |
@ -1,17 +1,21 @@
|
||||
# UX II - Ex 2 - Run interviews |
||||
## Run interviews |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Run 6 interviews. Go in pairs, one being the interviewer and the other the note taker. |
||||
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. |
||||
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.) |
||||
|
||||
**Deliverables:** |
||||
|
||||
- A PDF document with the scripts from all the 6 interviews. |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
### 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](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
@ -1,10 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Are there the scripts from all the interviews in the document? |
||||
###### Are there at least 6 different interviews? |
||||
###### Are there at least 3 interviews with random people outside the building (ask the conditions where the interview was triggered and made)? |
||||
###### Do the questions from the interview guide match the written script of the interview? |
@ -1,24 +1,28 @@
|
||||
# UX II - Ex 4 - Problem statement |
||||
## Second problem statement |
||||
|
||||
**Instructions:** |
||||
### 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. |
||||
You may use the "How Might We" exercise in pairs. |
||||
|
||||
**Deliverable:** |
||||
|
||||
- A PDF document with a problem statement starting with a "How Might We" |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
**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](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [Stuck on a problem? Just ask how might we](https://relab.academy/design-thinking/stuck-on-a-problem-just-ask-how-might-we/) |
||||
- [Problem statement](https://www.indeed.com/career-advice/career-development/what-is-a-problem-statement) |
||||
- [Using ‘How Might We’ Questions to Ideative on the Right Problems](https://www.nngroup.com/articles/how-might-we-questions/) |
||||
- [Using "How Might We’ Questions to Ideate on the Right Problems](https://www.nngroup.com/articles/how-might-we-questions/) |
||||
|
||||
**Quote:** |
||||
**Quote:** |
||||
|
||||
‘Out of clutter, find simplicity. From discord, find harmony. In the middle of difficulty, lies opportunity.’ Albert Einstein |
||||
"Out of clutter, find simplicity. From discord, find harmony. In the middle of difficulty, lies opportunity.’ Albert Einstein |
@ -0,0 +1,155 @@
|
||||
#### Interview Guide |
||||
|
||||
###### Is the deliverable labeled as Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is the main purpose of the interview written? |
||||
|
||||
###### Is there a proper introduction that describes the interviewer and the purpose of this interview? |
||||
|
||||
###### Are there 1 to 3 hypotheses? |
||||
|
||||
###### Are there 3 to 5 main topics? |
||||
|
||||
###### Are there some screening questions? |
||||
|
||||
###### Are there open-ended questions (10 max)? |
||||
|
||||
###### Is there a funnel process (broader to more accurate questions)? |
||||
|
||||
###### Is there a conclusion with the next steps and a thank you message? |
||||
|
||||
#### Run interviews |
||||
|
||||
###### Is the deliverable labeled as Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Are the scripts from all the interviews in the document? |
||||
|
||||
###### Are there at least 6 different interviews? |
||||
|
||||
###### Are there at least 3 interviews with random people outside the building (ask the conditions where the interview was triggered and made)? |
||||
|
||||
###### Do the questions from the interview guide match the written script of the interview? |
||||
|
||||
#### Affinity diagram & Empathy map |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is there an affinity diagram that is digital (on Miro) or on paper? |
||||
|
||||
###### Is there an empathy map that is digital (on Miro) or on paper? |
||||
|
||||
###### Are there multiple sticky notes that match with the transcription? |
||||
|
||||
###### Are the sticky notes gathered in clusters? |
||||
|
||||
###### Are the clusters labeled? |
||||
|
||||
###### Is the empathy map filled ONLY with the content from the student affinity diagram? |
||||
|
||||
###### Is the "See" section complete? |
||||
|
||||
###### Is the "Say & Do" section complete? |
||||
|
||||
###### Is the "Hear" section complete? |
||||
|
||||
###### Is the "Think and Feel" section complete? |
||||
|
||||
###### Is the "Pain" section complete? |
||||
|
||||
###### Is the "Goal" section complete? |
||||
|
||||
#### Problem Statement |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is the problem statement written with a "How Might We" question? |
||||
|
||||
###### Does it include the user's main goal? |
||||
|
||||
###### Does is include the user's main pain? |
||||
|
||||
###### Is it narrow enough? |
||||
|
||||
###### Is it broad enough? |
||||
|
||||
#### Second Ideation |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Are there pictures of the ideation workshop? |
||||
|
||||
###### Is the script consistent with the goal of the workshop? |
||||
|
||||
###### Is there at least one picture of each of the workshops? |
||||
|
||||
###### Is there a PDF document with at least 3 ideas that came out the 2 workshops? |
||||
|
||||
###### Do the ideas offer a way to solve the problem statement? |
||||
|
||||
#### User flow |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is there a user flow (picture of the paper version or digital)? |
||||
|
||||
###### Does the user have a specific goal? |
||||
|
||||
###### Is there a starting point and an ending point? |
||||
|
||||
###### Is the ending point the goal of the user? |
||||
|
||||
###### Is there a series of actions organized in rectangles (actions) or diamonds (choices)? |
||||
|
||||
###### Are the actions linked with arrows? |
||||
|
||||
#### Second prototyping |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Are there picture of a paper prototype? |
||||
|
||||
###### Are there between 6 and 12 different screens on the paper prototype? |
||||
|
||||
###### Do the screens match the main steps of the user flow? (ask the student to show you) |
||||
|
||||
###### Are there mid-fidelity wireframes on Figma that match the paper prototypes? |
||||
|
||||
###### Are the paper prototypes and wireframes in black, grey, and white and do not include any style elements?. (ask the student to show you) |
||||
|
||||
###### Does each screen have the main navigation elements (arrows, menu, call to actions)? |
||||
|
||||
###### Does each screen follow the other according to the user flow? |
@ -1,23 +1,29 @@
|
||||
# UX II - Ex 6 - User flow |
||||
## User flow |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Structure your main ideas into a comprehensive user flow. |
||||
You can include one, two, of the three main ideas from your ideation process, depending on how consistent it would be for the users. |
||||
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. |
||||
|
||||
**Deliverable:** |
||||
Don't forget to: |
||||
|
||||
- A comprehensive user flow on a board (digital or pictures of a paper version) |
||||
- 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”. |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
**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](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [User flow glossary](https://www.productplan.com/glossary/user-flow/) |
||||
- [Site flows vs User Flows](https://uxmovement.com/wireframes/site-flows-vs-user-flows-when-to-use-which/) |
||||
- [How to make a User Flow diagram](https://www.lucidchart.com/blog/how-to-make-a-user-flow-diagram) |
||||
|
||||
**Quote:** |
||||
**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 |
||||
"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 |
||||
|
@ -1,14 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there a user flow (picture of the paper version or digital)? |
||||
###### Does the user have a specific goal? |
||||
###### Is there a starting point and an ending point? |
||||
###### Is the ending point the goal of the user? |
||||
###### Is there a series of actions organized in rectangles (actions) or diamonds (choices)? |
||||
###### Are the actions linked with arrows? |
@ -1,15 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Are the ideas structured and organized? |
||||
###### Is the target defined in terms of profile, age rank, situations, location? |
||||
###### Are there at least 8 different channels (and links) with social networks, pages, groups, forums, influencers, etc. included? |
||||
###### Are there at least two different messages? |
||||
###### Are there at least 3 rounds of campaigns as plans A, B and C? |
||||
###### Are there at least 40 answers? |
||||
###### Is there a feedback document including the main takeaways from this experience? |
@ -1,41 +1,46 @@
|
||||
# UX III - Ex 1 - Competitive Analysis |
||||
## Competitive Analysis |
||||
|
||||
**Context:** |
||||
**Context:** |
||||
|
||||
Quest n°3 is about Empathy. |
||||
Quest n°3 is about Empathy. |
||||
|
||||
In this scenario, the principal of your high school heard you were a designer. They chose to reach you to help them face school harassment among teenagers. |
||||
|
||||
School harassment describes school-based harassment behaviors. It is characterized by the repeated use of violence, including mockery and other humiliations. |
||||
|
||||
As a matter of fact, they realized they didn’t know this generation (15 to 18-year-olds) very well. So they are asking you to conduct user research to meet this population and understand them. |
||||
As a matter of fact, they realized they didn’t know this generation (15 to 18-year-olds) very well. So they are asking you to conduct user research to meet this population and understand them. |
||||
|
||||
Your job is to explore your topic and use various tools included in this “Empathize” phase. |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Conduct a competitive analysis among 10 associations or organizations fighting school harassment. |
||||
Conduct a competitive analysis among 10 associations or organizations fighting school harassment. |
||||
|
||||
You can pick 10 organizations worldwide, or from your home region or home country. Let's browse! |
||||
You can pick 10 organizations worldwide, or from your home region or home country. Let's browse! |
||||
|
||||
Compare these 10 organizations' main actions, channels, values, according to the criteria you assume are relevant. |
||||
Compare these 10 organizations' main actions, channels, values, according to the criteria you assume are relevant. |
||||
|
||||
**Deliverables :** |
||||
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 competitive report with an introduction that explains your main conclusions (PDF) |
||||
- A chart to show the competitive landscape, with 2 axes of your choice (digital, psychological, local, closeness to students, institutional, etc.) (PDF) |
||||
- A table to compare the organizations on 5 to 10 criteria (PDF) |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
- A competitive table to compare the organizations on 5 to 10 criteria (PDF) |
||||
|
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
Resources: |
||||
**Resources:** |
||||
|
||||
- [Competitive Analysis: How to approach it effectively](https://uxdesign.cc/competitive-analysis-how-to-approach-it-effectively-def97d130d2c) |
||||
- [Competitive Analysis Templates](https://venngage.com/blog/competitor-analysis-template/) |
||||
|
||||
**Quote :** |
||||
**Quote:** |
||||
|
||||
- 'Always design a thing in its larger context: a chair in a room, a room in a house, a house in an environment, an environment in a city plan’ Eero Sarrinen | Knoll |
||||
- Creating a great design isn’t just about understanding what the user wants. It’s also about understanding and delivering on what the business needs. |
||||
|
@ -1,15 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there an introduction? |
||||
###### Is there a [competitive landscape](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/g2crowd-grid.png) like this example? |
||||
###### Are there 2 relevant axes on the competitive landscape? |
||||
###### Are there 10 organizations that appear on the landscape? |
||||
###### Is there a [competitive table](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/product-features-comparison-matrix.png) like this example? |
||||
###### Are there 5 to 10 criteria on the competitive table? |
||||
###### Are there 10 organizations that appear on the table? |
@ -1,37 +1,41 @@
|
||||
# UX III - Ex 4 - Interviews |
||||
## Interviews |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
- Create an interview guide |
||||
- Conduct 3 interviews with teenagers |
||||
|
||||
After knowing more about trends and "What" people do thanks to surveys, the main goal is to understand "why". |
||||
|
||||
**Deliverables:** |
||||
Don't forget to: |
||||
|
||||
- A PDF document with an interview guide |
||||
- A PDF document with 3 scripts |
||||
- An affinity diagram from your interviews (PDF or digital, on Miro or Figma for example) |
||||
- 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”. |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
After knowing more about trends and "What" people do thanks to surveys, the main goal is to understand "why". |
||||
|
||||
- [Respondent - Tool to find users](https://www.respondent.io) |
||||
- [How to conduct user interviews](https://uxdesign.cc/how-to-conduct-user-interviews-fe4b8c34b0b7?sk=9625632a522a9309a91297191e668565) |
||||
- [How to design better products through user interviews](https://uxdesign.cc/how-to-design-better-products-through-user-interviews-4c5142bb1fc4) |
||||
- [Asking the right questions](https://uxdesign.cc/asking-the-right-questions-on-user-research-interviews-and-testing-427261742a67) |
||||
### Deliverables |
||||
|
||||
**Tips:** |
||||
- A PDF document with an interview guide. |
||||
- A PDF document with 3 scripts. |
||||
- An affinity diagram from your interviews (PDF or digital, on Miro or Figma for example) |
||||
|
||||
Here are the recommended steps : |
||||
**Tips:** |
||||
|
||||
Here are the recommended steps : |
||||
|
||||
1. 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. |
||||
2. Write down 1 to 3 hypotheses you have regarding this topic, that needs to be either confirmed or disproved. |
||||
2. Write down 1 to 3 hypotheses you have regarding this topic, that needs to be either confirmed or disproved. |
||||
3. Pick 3 to 5 main topics you need to get information on. |
||||
4. For each topic, write 1 to 3 open-ended 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. |
||||
5. Write some screening questions to have a few pieces of demographics (age, job, location, etc.) |
||||
6. Structure your questions in a funnel: start with broad questions to focus on specific topics or situation. Remember to stay neutral in your tone to let the user tell their own story. Try to focus on 10 main questions. |
||||
7. 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. |
||||
8. 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. |
||||
7. 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. |
||||
8. 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. |
||||
|
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [Respondent - Tool to find users](https://www.respondent.io) |
||||
- [How to conduct user interviews](https://uxdesign.cc/how-to-conduct-user-interviews-fe4b8c34b0b7?sk=9625632a522a9309a91297191e668565) |
||||
- [How to design better products through user interviews](https://uxdesign.cc/how-to-design-better-products-through-user-interviews-4c5142bb1fc4) |
||||
- [Asking the right questions](https://uxdesign.cc/asking-the-right-questions-on-user-research-interviews-and-testing-427261742a67) |
||||
|
@ -1,11 +0,0 @@
|
||||
#### Audit |
||||
|
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Are there 3 scripts? |
||||
###### Is there an [affinity diagram](https://d2slcw3kip6qmk.cloudfront.net/marketing/blog/2017Q1/affinity-diagram3.png) from the interviews? |
@ -1,12 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there a framework? |
||||
###### Does the persona have a name (consistent with the people interviewed)? |
||||
###### Is there demographic data? |
||||
###### Are the persona's pain points included? |
||||
###### Are the persona's drivers included? |
||||
###### Are the persona's behaviors included (hobbies, technology, whatever seems relevant)? |
@ -1,11 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is the problem statement written with a How Might We question? |
||||
###### Does the problem statement include the persona's main goal or main painpoint? |
||||
###### Is it narrow enough? |
||||
###### Is it broad enough? |
||||
###### Are there 3 measurable KPIs ([check the SMART list](https://www.grow.com/blog/how-to-use-smart-goals-to-build-your-kpis))? |
@ -1,27 +1,31 @@
|
||||
# UX III - Ex 5 - Personas |
||||
## Second Personas |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Let's create a persona based on your quantitative research and your interviews. |
||||
Let's create a persona based on your quantitative research and your interviews. |
||||
|
||||
Your persona card should include common trends amongst the people you got data from (habits, verbatims, fears, drivers, frustration, and pain points). |
||||
|
||||
Reminder: Your persona is fictional and should not have the exact name or picture as someone you interviewed, but remember a persona is here so you can make decisions as a designer. |
||||
|
||||
**Deliverables:** |
||||
|
||||
- A PDF persona card extracted from a Figma file |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
**Reminder:** Your persona is fictional and should not have the exact name or picture as someone you interviewed, but remember a persona is here so you can make decisions as a designer. |
||||
|
||||
### Deliverables |
||||
|
||||
- A PDF persona card extracted from a Figma file. |
||||
|
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [Make your persona great again](https://uxdesign.cc/personas-e60c1c06ead1) |
||||
- [Persona, journey maps, user flow, site map, OH MY!](https://uxdesign.cc/personas-journey-maps-site-maps-and-user-flows-oh-my-e71d044b4bcb) |
||||
- [Persona framework](https://miro.medium.com/max/1400/0*RbHfR6BHhhFIENNf) |
||||
|
||||
**Quotes:** |
||||
**Quotes:** |
||||
|
||||
- If you design for everyone, you delight no one. |
||||
- A good user persona is the one based on user research, without regard to how many attributes we can describe. |
||||
- "If you design for everyone, you delight no one." |
||||
- "A good user persona is the one based on user research, without regard to how many attributes we can describe." |
@ -1,15 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there the main purpose of the form? |
||||
###### Are there 1 to 3 hypotheses? |
||||
###### Is there a proper introduction that describes the interviewer and the purpose of this interview? |
||||
###### Are there 3 to 5 main topics? |
||||
###### Are there a few screening questions? |
||||
###### Are there closed-ended, unbiased questions, max 10? |
||||
###### Is there a funnel process (>) ? |
||||
###### Is there a conclusion with the next steps and a thank you message? |
||||
###### Is there a link to the survey ready to be spread? |
@ -1,34 +1,39 @@
|
||||
# UX III - Ex 7 - Problem Statement |
||||
## Third problem statement |
||||
|
||||
**Instructions:** |
||||
Based on your previous work, your persona and your user journey's main painpoint, define a problem statement that would clarify the main problem you want to tackle. |
||||
You may use the How Might We exercise in pairs. |
||||
### Instructions |
||||
|
||||
Then, define 3 KPIs (Key performance Indicators) that will help you measure the definition of Done and the success of the solution. |
||||
Based on your previous work, your persona and your user journey's main pain point, define a problem statement that would clarify the main problem you want to tackle. |
||||
You may use the "How Might We" exercise in pairs. |
||||
|
||||
**Deliverables:** |
||||
Then, define 3 KPIs (Key performance Indicators) that will help you measure the definition of Done and the success of the solution. |
||||
|
||||
- A PDF document with one problem statement and 3 KPIs to measure the impact of the solution |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
### Deliverables |
||||
|
||||
- A PDF document with one problem statement and 3 KPIs to measure the impact of the solution |
||||
|
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [Stuck on a problem? Just ask how might we](https://relab.academy/design-thinking/stuck-on-a-problem-just-ask-how-might-we/) |
||||
- [Stuck on a problem? Just ask ‘How Might We’](https://relab.academy/design-thinking/stuck-on-a-problem-just-ask-how-might-we/) |
||||
- [Problem statement](https://www.indeed.com/career-advice/career-development/what-is-a-problem-statement) |
||||
- [Using ‘How Might We’ Questions to Ideative on the Right Problems](https://www.nngroup.com/articles/how-might-we-questions/) |
||||
- [Using ‘How Might We’ Questions to Ideate on the Right Problems](https://www.nngroup.com/articles/how-might-we-questions/) |
||||
- [Unleashing the power of a UX KPI](https://articles.uie.com/power_of_ux_kpi/) |
||||
- [KPI is an imperative tool for UX designers](https://uxdesign.cc/kpi-is-the-most-important-tool-ux-designers-should-be-learning-to-use-af31651120fc?sk=e619213adfda152171d597fc3ab1053a) |
||||
- [Measuring product design impact — KPIs, NPS, UX, WTF](https://uxdesign.cc/measuring-product-design-impact-kpis-nps-ux-wtf-3fe6a26e7400?sk=52c1f3842edbe90524f6da1fe85db71d) |
||||
- [A metrics-driven approach to evaluate success of UX design](https://uxdesign.cc/a-metrics-driven-approach-to-evaluate-success-of-ux-design-dd3bea098820?sk=acf1b1f7f0a7663d34d11906339b4698) |
||||
- [A big list of UX KPIs and metrics](https://www.cxpartners.co.uk/our-thinking/big_list_of_ux_kpis_and_metrics/) |
||||
- [How to use SMART goals to build your KPIs](https://www.grow.com/blog/how-to-use-smart-goals-to-build-your-kpis) |
||||
- Exampels of KPIs (fake data! Not to be copied or used!): |
||||
- Harassment case report rates increase by 20% within 2 years |
||||
- Online harassment drops by 30% within 5 years |
||||
- 90% of the 15-18 year-olds knows a harassment witness response process within 2 years |
||||
- Examples of KPIs (fake data! Not to be copied or used!): |
||||
- Harassment case report rates increase by 20% within 2 years |
||||
- Online harassment drops by 30% within 5 years |
||||
- 90% of the 15-18 year-olds knows a harassment witness response process within 2 years |
||||
|
||||
**Quote:** |
||||
**Quote:** |
||||
|
||||
‘Every problem is an opportunity for design. By framing your challenge as a How Might We question, you’ll set yourself up for an innovative solution’ IDEO |
||||
"Every problem is an opportunity for design. By framing your challenge as a How Might We question, you’ll set yourself up for an innovative solution" IDEO |
@ -0,0 +1,151 @@
|
||||
#### Competitive Analyzes |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is there an introduction that explains the main conclusions? |
||||
|
||||
###### Is there a [competitive landscape](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/g2crowd-grid.png) like this example? |
||||
|
||||
###### Are there 2 relevant axes on the competitive landscape? |
||||
|
||||
###### Are there 10 organizations that appear on the landscape? |
||||
|
||||
###### Is there a [competitive table](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/product-features-comparison-matrix.png) like this example? |
||||
|
||||
###### Are there 5 to 10 criteria on the competitive table? |
||||
|
||||
###### Are there 10 organizations that appear on the table? |
||||
|
||||
#### Surveys |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is there the main purpose of the form? |
||||
|
||||
###### Are there 1 to 3 hypotheses? |
||||
|
||||
###### Is there a proper introduction that describes the interviewer and the purpose of this interview? |
||||
|
||||
###### Are there 3 to 5 main topics? |
||||
|
||||
###### Are there a few screening questions? |
||||
|
||||
###### Are there closed-ended, unbiased questions? (10 maximum) |
||||
|
||||
###### Is there a funnel process? (broader to more accurate questions) |
||||
|
||||
###### Is there a conclusion with the next steps and a thank you message? |
||||
|
||||
###### Is there a link to the survey ready to be spread? |
||||
|
||||
#### Broadcast strategy |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Are the ideas structured and organized? |
||||
|
||||
###### Is the target defined in terms of profile, age rank, situations, location? |
||||
|
||||
###### Are there at least 8 different channels (and links) with social networks, pages, groups, forums, influencers, etc. included? |
||||
|
||||
###### Are there at least two different messages? |
||||
|
||||
###### Are there at least 3 rounds of campaigns as plans A, B and C? |
||||
|
||||
###### Are there at least 40 answers? |
||||
|
||||
###### Is there a feedback document including the main takeaways from this experience? |
||||
|
||||
#### Interviews |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is there a PDF document with an interview guide. |
||||
|
||||
###### Are there 3 scripts? |
||||
|
||||
###### Is there an [affinity diagram](https://d2slcw3kip6qmk.cloudfront.net/marketing/blog/2017Q1/affinity-diagram3.png) from the interviews? |
||||
|
||||
#### Second Personas |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is there a framework? |
||||
|
||||
###### Does the persona have a name (consistent with the people interviewed)? |
||||
|
||||
###### Is there demographic data? |
||||
|
||||
###### Are the persona's pain points included? |
||||
|
||||
###### Are the persona's drivers included? |
||||
|
||||
###### Are the persona's behaviors included (hobbies, technology, whatever seems relevant)? |
||||
|
||||
#### Second User Journey |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (Figma)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is there a frame with a timeline? |
||||
|
||||
###### Does the timeline show the journey of the persona? |
||||
|
||||
###### Are there emotions included at each step? |
||||
|
||||
###### Are the main pain points highlighted? |
||||
|
||||
#### Third Problem Statement |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is the problem statement written with a "How Might We" question? |
||||
|
||||
###### Does the problem statement include the persona's main goal or main pain point? |
||||
|
||||
###### Is the problem statement narrow enough? |
||||
|
||||
###### Is the problem statement broad enough? |
||||
|
||||
###### Are there 3 measurable KPIs ([check the SMART list](https://www.grow.com/blog/how-to-use-smart-goals-to-build-your-kpis))? |
@ -1,10 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (Figma)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there a frame with a timeline? |
||||
###### Does the timeline show the journey of the persona? |
||||
###### Are there emotions included at each step? |
||||
###### Are the main pain points highlighted? |
@ -1,11 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read?###### Is there a script including the research goals? |
||||
###### Are the research goals close to "rearrange the content"? |
||||
###### Are there pictures of the ongoing workshop? |
||||
###### Is there a new content organization shown in a table with sticky notes (it can be a picture or digital)? |
@ -1,8 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (Sheet)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is the chart duplicated? |
||||
###### Is the chart complete? |
@ -1,10 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is the sentence complete? |
||||
###### Does the "When" part involve a visit on the website? |
||||
###### Does the "I want to" part involve a practical action? |
||||
###### Does the "So I can" part involve a psychological or emotional purpose? |
@ -1,11 +1,123 @@
|
||||
#### Audit |
||||
#### Heuristics |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (Sheet)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is the chart duplicated? |
||||
|
||||
###### Is the chart complete? |
||||
|
||||
###### Is the heuristic analysis done to a South American music label? (ask the student to confirm) |
||||
|
||||
#### Site map |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Does the document have a title? |
||||
|
||||
###### Is the name of the website included in the document? |
||||
|
||||
###### Are all the pages of the website included in the chart? |
||||
|
||||
###### Are all the pages of the website linked (there is no "loose" page)? |
||||
|
||||
#### JTBD |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is the sentence complete? |
||||
|
||||
###### Does the "When" part involve a visit on the website? |
||||
|
||||
###### Does the "I want to" part involve a practical action? |
||||
|
||||
###### Does the "So I can" part involve a psychological or emotional purpose? |
||||
|
||||
#### Card sorting |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is there a PDF with a script including the research goals? |
||||
|
||||
###### Are the research goals close to "rearrange the content"? |
||||
|
||||
###### Are there pictures of the ongoing workshop? |
||||
|
||||
###### Is there a new content organization shown in a table with sticky notes (it can be a picture or digital)? |
||||
|
||||
#### Music label wireframes |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (Figma)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Are there between 6 and 12 screens? |
||||
|
||||
###### Is the sequence of links logical? |
||||
|
||||
###### Are the screens in black and white? |
||||
|
||||
#### Test protocol |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is the scope clear: What are we testing? |
||||
|
||||
###### Are there either 5 names or a strategy to find users to interview? |
||||
|
||||
###### Are the objectives clear: What are we proving? |
||||
|
||||
###### Are the metrics clear to prove the test is efficient? |
||||
|
||||
###### Is there a greeting introduction? |
||||
|
||||
###### Are the instructions clear? |
||||
|
||||
###### Is there a conclusion to thank the user? |
||||
|
||||
#### Run 5 tests |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Are there pictures of the ongoing tests? |
||||
|
||||
###### Are there conclusions from each test? |
||||
###### Are there 3 ideas to include in the next version of the prototype? |
||||
|
||||
###### Are there 3 ideas to include in the next version of the prototype? |
||||
|
@ -1,40 +1,39 @@
|
||||
# UX V - Ex 2 - Site map |
||||
## Site map |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Stick to the website you have chosen in Ex.1 and design a site map. The site map should include all the pages of the website as well as the connections and hierarchy. |
||||
Stick to the website you have chosen in the previous exercise "heuristics" and design a site map. The site map should include all the pages of the website as well as the connections and hierarchy. |
||||
|
||||
**List of websites:** |
||||
**List of websites:** |
||||
|
||||
- [Universal Music Latin America](https://www.universalmusica.com/) |
||||
- [Delta Records](https://deltarecords.net/) |
||||
- [Zoho Music](https://www.zohomusic.com/) |
||||
- [Luaka Bop](https://www.luakabop.com/) |
||||
- [Rimas Music](https://rimasmusic.com/) |
||||
- More... as long as it is a South American music label ;-) |
||||
- You can choose another one, as long as it is a South American music label. |
||||
- 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:** |
||||
### Deliverables |
||||
|
||||
- A PDF page of the site map. |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
**Tips:** |
||||
|
||||
- Start by drawing on paper, then pass it on to a digital tool. |
||||
- Please label your document! Title and name of the website. |
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
**Resources:** |
||||
|
||||
- [How to create a good site map](https://www.smokeylemon.com/blog/how-to-create-a-good-sitemap/) |
||||
|
||||
**Recommended tools:** |
||||
**Recommended tools:** |
||||
|
||||
- Figma |
||||
- Adobe Illustrator |
||||
- etc. |
||||
|
||||
**Quote:** |
||||
**Quote:** |
||||
|
||||
‘The organization, search, and navigation systems that help people to complete tasks, find what they need, and understand what they’ve found’ Peter Morville | Information Architecture for the WWW |
||||
"The organization, search, and navigation systems that help people to complete tasks, find what they need, and understand what they’ve found’ Peter Morville | Information Architecture for the WWW. |
||||
|
@ -1,10 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Does the document have a title? |
||||
###### Is the name of the website included in the document? |
||||
###### Are all the pages of the website included in the chart? |
||||
###### Are all the pages of the website linked (there is no "loose" page)? |
@ -1,32 +1,38 @@
|
||||
# UX V - Ex 6 - Test protocol |
||||
## Test protocol |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Prepare a protocol for usability testing. |
||||
Prepare a protocol for usability testing. |
||||
|
||||
**Deliverable:** |
||||
Recommended steps: |
||||
|
||||
- Define the scope of the test. |
||||
- Recruit 5 users. |
||||
- Identify objectives: What are you proving? |
||||
- Establish metrics: How are you proving your design is efficient? |
||||
- Describe the steps and the instructions. |
||||
- Write an introduction to greet their user. |
||||
- Write a conclusion to thank the user. |
||||
|
||||
Don't forget to: |
||||
|
||||
- A PDF document with a test protocol |
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** Recommended steps |
||||
**Deliverable:** |
||||
|
||||
- Define the scope of the test |
||||
- Recruit 5 users |
||||
- Identify objectives: What are you proving? |
||||
- Establish metrics: How are you proving your design is efficient? |
||||
- Describe the steps and the instructions |
||||
- Write an introduction to greet ther user |
||||
- Write a conclusion to thank the user |
||||
- A PDF document with a test protocol. |
||||
|
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources** |
||||
**Resources** |
||||
|
||||
- [How to do a user interview (tutorial from Google Ventures)](https://www.youtube.com/watch?v=Qq3OiHQ-HCU) |
||||
- [Running a usability test](https://www.usability.gov/how-to-and-tools/methods/running-usability-tests.html) |
||||
- [Usability testing: what is it and how to do it?](https://uxdesign.cc/usability-testing-what-is-it-how-to-do-it-51356e5de5d) |
||||
|
||||
**Quote:** |
||||
**Quote:** |
||||
|
||||
You need to detect: How many errors do users make? How severe are these errors? How easily can they recover from the errors? |
||||
- You need to detect: How many errors do users make? How severe are these errors? How easily can they recover from the errors? |
||||
|
@ -1,13 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is the scope clear: What are we testing? |
||||
###### Are there either 5 names or a strategy to find users to interview? |
||||
###### Are the objectives clear: What are we proving? |
||||
###### Are the metrics clear to prove the test is efficient? |
||||
###### Is there a greeting introduction? |
||||
###### Are the instructions clear? |
||||
###### Is there a conclusion to thank the user? |
@ -1,9 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (Figma)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Are there between 6 and 12 screens? |
||||
###### Is the sequence of links logical? |
||||
###### Are the screens in black and white? |
@ -1,40 +1,46 @@
|
||||
# UX VII - Ex 3 - Define |
||||
## Define |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Run at least one of the Define tools in the design process. |
||||
|
||||
**Deliverables:** |
||||
### Deliverables |
||||
|
||||
- A PDF document with the script of the tool context |
||||
- Completed tool (scripts from user interviews, results from a quantitative analysis, etc.) |
||||
- A PDF document with the key learnings from this phase |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
- A PDF document with the script of the tool context. |
||||
- Completed tool (scripts from user interviews, results from a quantitative analysis, etc.). |
||||
- A PDF document with the key learnings from this phase. |
||||
|
||||
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. |
||||
|
||||
**Tips:** |
||||
|
||||
- Use as many tools as needed, be make sure you do all the process in 4 working days! |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Criteria:** |
||||
|
||||
- Persona |
||||
- The script is the list of insights the students uses to create the persona |
||||
- The completed tool is a [Persona board](https://miro.medium.com/max/1400/0*RbHfR6BHhhFIENNf). Make sure the key insights come from the field, from reality, but the persona itself is different from only one user. |
||||
- Persona |
||||
|
||||
- The script is the list of insights the students uses to create the persona. |
||||
- The completed tool is a [Persona board](https://miro.medium.com/max/1400/0*RbHfR6BHhhFIENNf). Make sure the key insights come from the field, from reality, but the persona itself is different from only one user. |
||||
|
||||
- Empathy Map |
||||
|
||||
- The script is the list of insights the student uses to create the Empathy map. |
||||
- The completed tool is an [Empathy Map](https://miro.medium.com/max/700/1*I1ffOWdPWQva3dCMQE-TAQ.png). |
||||
|
||||
- User Journey |
||||
|
||||
- Empathy Map |
||||
- The script is the list of insights the student uses to create the Empathy map |
||||
- The completed tool is an [Empathy Map](https://miro.medium.com/max/700/1*I1ffOWdPWQva3dCMQE-TAQ.png). |
||||
- The script is the list of insights the student uses to create the User Journey. |
||||
- The completed tool is a [User Journey Map](https://d2slcw3kip6qmk.cloudfront.net/marketing/blog/2017Q3/SEO-initiative-customer-journey-mapping/CustomerJourneyMap1.png). |
||||
|
||||
- User Journey |
||||
- The script is the list of insights the student uses to create the User Journey. |
||||
- The completed tool is a [User Journey Map](https://d2slcw3kip6qmk.cloudfront.net/marketing/blog/2017Q3/SEO-initiative-customer-journey-mapping/CustomerJourneyMap1.png). |
||||
- Jobs-to-be-done (JTBD) |
||||
|
||||
- Jobs-to-be-done (JTBD) |
||||
- The JTBD is tool that goes as a conclusion to another of the previous tools. Make sure: |
||||
- The sentence is complete |
||||
- The "When" part involves a visit on the website |
||||
- The "I want to" part involves a practical action |
||||
- The "So I can" part involves a psychological or emotional purpose |
||||
- The JTBD is tool that goes as a conclusion to another of the previous tools. Make sure: |
||||
- The sentence is complete. |
||||
- The "When" part involves a visit on the website. |
||||
- The "I want to" part involves a practical action. |
||||
- The "So I can" part involves a psychological or emotional purpose. |
||||
|
@ -1,16 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there at least one of the following tools? |
||||
- Persona |
||||
- Empathy Map |
||||
- User Journey |
||||
- JBTD or Jobs-to-be-done (a JTBD must go along with another tool) |
||||
###### Is the script completed (list of criteria in the instructions section)? |
||||
###### Is the tool completed (list of criteria in the instructions section)? |
||||
###### Is there a document with the key learnings the students learnt from this phase? |
@ -1,59 +1,59 @@
|
||||
# UX VII - Ex 2 - Empathy |
||||
## Empathy |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Run at least one of the Empathy tools in the design process. |
||||
|
||||
**Deliverables:** |
||||
### Deliverables |
||||
|
||||
- A PDF document with the script of the tool context |
||||
- Completed tool (scripts from user interviews, results from a quantitative analysis, etc.) |
||||
- A PDF document with the key learnings from this phase |
||||
- 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”. |
||||
- A PDF document with the script of the tool context. |
||||
- Completed tool (scripts from user interviews, results from a quantitative analysis, etc.). |
||||
- A PDF document with the key learnings from this phase. |
||||
|
||||
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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
|
||||
- Use as many tools as needed, be make sure you do all the process in 4 working days! |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Criteria:** |
||||
|
||||
- User interviews |
||||
- The script is the interview guide. Make sure there is: |
||||
- the main purpose of the interview |
||||
- 1 to 3 hypotheses |
||||
- a proper introduction that describes the interviewer and the purpose of this interview |
||||
- 3 to 5 main topics |
||||
- a few scan questions (demographics) |
||||
- open-ended questions, max 10 |
||||
- a funnel process (>) |
||||
- a conclusion with next steps and a thank you. |
||||
- The completed tool is either: |
||||
- 5 to 10 scripts from users |
||||
- or an [Affinity Diagram](https://www.youtube.com/watch?v=VngWHIE4k9s) with the main elements |
||||
|
||||
- Analytics |
||||
- The script is the form. Make sure there is: |
||||
- The main purpose of the form |
||||
- 1 to 3 hypotheses |
||||
- A proper introduction that describes the interviewer and the purpose of this interview |
||||
- 3 to 5 main topics |
||||
- A few scan questions (demographics) |
||||
- Closed-ended, unbiased questions, max 10 |
||||
- A funnel process (>) |
||||
- A conclusion with next steps and a thank you. |
||||
- A broadcast strategy |
||||
- The completed tool is a series of quantitative data from at least 100 answers. |
||||
|
||||
|
||||
- User interviews |
||||
- The script is the interview guide. Make sure there is: |
||||
- the main purpose of the interview |
||||
- 1 to 3 hypotheses |
||||
- a proper introduction that describes the interviewer and the purpose of this interview |
||||
- 3 to 5 main topics |
||||
- a few scan questions (demographics) |
||||
- open-ended questions, max 10 |
||||
- a funnel process (>) |
||||
- a conclusion with next steps and a thank you. |
||||
- The completed tool is either: |
||||
- 5 to 10 scripts from users |
||||
- or an [Affinity Diagram](https://www.youtube.com/watch?v=VngWHIE4k9s) with the main elements |
||||
- Analytics |
||||
- The script is the form. Make sure there is: |
||||
- The main purpose of the form |
||||
- 1 to 3 hypotheses |
||||
- A proper introduction that describes the interviewer and the purpose of this interview |
||||
- 3 to 5 main topics |
||||
- A few scan questions (demographics) |
||||
- Closed-ended, unbiased questions, max 10 |
||||
- A funnel process (>) |
||||
- A conclusion with next steps and a thank you. |
||||
- A broadcast strategy |
||||
- The completed tool is a series of quantitative data from at least 100 answers. |
||||
- Competitive analysis |
||||
- The script is the strategy. The student explains what they are looking for and how they plan to find it. |
||||
- The completed tool is a report. Make sure there is; |
||||
- There is an introduction |
||||
- There is a [competitive landscape](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/g2crowd-grid.png) |
||||
- With 2 relevant axes |
||||
- 10 organizations appear on the landscape |
||||
- There is a [competitive table](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/product-features-comparison-matrix.png) |
||||
- With 5 to 10 criteria |
||||
- 10 organizations appear on the table |
||||
- The script is the strategy. The student explains what they are looking for and how they plan to find it. |
||||
- The completed tool is a report. Make sure there is; |
||||
- There is an introduction |
||||
- There is a [competitive landscape](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/g2crowd-grid.png) |
||||
- With 2 relevant axes |
||||
- 10 organizations appear on the landscape |
||||
- There is a [competitive table](https://venngage-wordpress.s3.amazonaws.com/uploads/2019/03/product-features-comparison-matrix.png) |
||||
- With 5 to 10 criteria |
||||
- 10 organizations appear on the table |
||||
|
@ -1,16 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there at least one of the following tools? |
||||
- User interviews |
||||
- Analytics |
||||
- Competitive analysis |
||||
###### Is the script completed (list of criteria in the instructions section)? |
||||
###### Is the tool completed (list of criteria in the instructions section)? |
||||
###### Is there a PDF document with the key learnings the students learnt from this phase? |
||||
|
@ -1,18 +0,0 @@
|
||||
# UX VII - Ex 5 - Ideation |
||||
|
||||
**Instructions:** |
||||
|
||||
Run at least one of the Ideation techniques in the design process. |
||||
|
||||
**Deliverables:** |
||||
|
||||
- A PDF document with the script of the tool context |
||||
- Completed tool: a board with all the ideas - on paper or digitally on Miro or Figma |
||||
- A PDF document with the key learnings from this phase |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
|
||||
- Use as many tools as needed, and make sure you do all the process in 4 working days! |
@ -1,18 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there a script of the ideation workshop? |
||||
###### Is there the main objective? |
||||
###### Is there an ice breaker? |
||||
###### Are there the main steps of the ideation process? |
||||
###### Are there clear instructions? |
||||
###### Is there a time schedule for each step? |
||||
###### Is there a voting process to select the main idea? |
||||
###### Is there board with all the ideas (on paper or digitally on Miro or Figma)? |
||||
###### Is there one main concept out of the ideation workshop? |
||||
###### Is there a document with the key learnings the students learnt from this phase? |
@ -1,35 +1,40 @@
|
||||
# UX VII - Ex 4 - Problem Statement |
||||
## Problem Statement |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Based on your research (Empathy & Define), define a problem statement to narrow the problem and KPIs to measure the success. |
||||
|
||||
**Deliverables:** |
||||
### Deliverables |
||||
|
||||
- A PDF document with: |
||||
- One problem statement |
||||
- 1 to 3 KPIs |
||||
- Key learnings from this phase |
||||
|
||||
- One problem statement. |
||||
- 1 to 3 KPIs. |
||||
- Key learnings from this phase. |
||||
|
||||
Don't forget to: |
||||
|
||||
- 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 on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
- KPIs: [check the SMART list](https://www.grow.com/blog/how-to-use-smart-goals-to-build-your-kpis)) |
||||
|
||||
**Quote:** |
||||
- KPIs: [check the SMART list](https://www.grow.com/blog/how-to-use-smart-goals-to-build-your-kpis)) |
||||
- Pay attention to the global aspect of the document. It must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Quote:** |
||||
|
||||
Design is about solving problems. Fall in Love with the Problem, Not the Solution. |
||||
|
||||
**Examples of Problem statements:** |
||||
|
||||
- How might we help Pierre measure and prepare his hydration before a race? |
||||
- Appropriate —> The problem statement is narrow enough to be specific for one painpoint, and broad enough to let creativity suggest many options. Also, it takes into accounts some of the key insights from the previous phases. |
||||
- How might we make sure Pierre doesn’t get dehydrated? |
||||
- Too broad —> The problem statement is out of the scope of running, so the solutions cannot be integrated in the specific context of running. |
||||
- How might we make sure Pierre drinks the cups that are offered during the race? |
||||
- Too narrow —> There are plenty of options to avoid dehydration without drinking the cups that are offered during the race. |
||||
- How might we provide Pierre with a drink that contains everything he needs to avoid dehydration? |
||||
- Focused on the solution, not the problem —> The problem statement is supposed to rephrase the brief and take into account the insights from the previous phase. |
||||
- How might make sure Pierre doesn’t get drunk the night before the race? |
||||
- Out of scope —> This is not about dehydration, nor about running. |
||||
- How might we help Pierre measure and prepare his hydration before a race? |
||||
- Appropriate —> The problem statement is narrow enough to be specific for one painpoint, and broad enough to let creativity suggest many options. Also, it takes into accounts some of the key insights from the previous phases. |
||||
- How might we make sure Pierre doesn’t get dehydrated? |
||||
- Too broad —> The problem statement is out of the scope of running, so the solutions cannot be integrated in the specific context of running. |
||||
- How might we make sure Pierre drinks the cups that are offered during the race? |
||||
- Too narrow —> There are plenty of options to avoid dehydration without drinking the cups that are offered during the race. |
||||
- How might we provide Pierre with a drink that contains everything he needs to avoid dehydration? |
||||
- Focused on the solution, not the problem —> The problem statement is supposed to rephrase the brief and take into account the insights from the previous phase. |
||||
- How might make sure Pierre doesn’t get drunk the night before the race? |
||||
- Out of scope —> This is not about dehydration, nor about running. |
||||
|
@ -1,9 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there one question that stands as a problem statement? |
||||
###### Are there between 1 and 3 KPIs that will help you measure the success of the upcoming solution? |
||||
###### Are there the key learnings the students learnt from this phase? |
@ -1,46 +1,43 @@
|
||||
# UX VII - Ex 6 - Prototype |
||||
## Prototype |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Make a prototype including the chosen solution. |
||||
Make a prototype including the chosen solution. |
||||
|
||||
**Deliverables:** |
||||
### Deliverables |
||||
|
||||
- Pictures of a paper prototype (low-fi) |
||||
- An animated wireframe prototype (mid-fi) |
||||
- Key learnings from this phase |
||||
- Vocabulary |
||||
- Low-Fidelity: Paper Prototypes - [Example here](https://miro.medium.com/max/1400/1*5nUfqqA2gjdAYHagjbHA5w.jpeg) |
||||
- Mid-Fidelity: Wireframes - black and white, only the main elements, on digital prototype tools - [Example here](https://miro.medium.com/max/1400/1*eGSfaxwYbxUFomYbyO6GWw.png) |
||||
- High-Fidelity: Wireframes with color, styles, graphical details, and micro-interactions - [Example here](https://miro.medium.com/max/1400/1*Xn0HSKAvhr4TZzC9lN5udw.gif) |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
- Pictures of a paper prototype (low-fi with 6 to 12 different screens). |
||||
- An animated wireframe prototype on figma (mid-fi). |
||||
- A PDF file with the key learnings from this phase. |
||||
|
||||
**Tips:** |
||||
Don't forget to: |
||||
|
||||
- Use as many tools as needed, and make sure you do all the process in 4 working days! |
||||
- You may use Card Sorting and User flows |
||||
- 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. |
||||
|
||||
**Criteria:** |
||||
|
||||
- User Flow |
||||
Make sure that for each flow: |
||||
|
||||
- The user has a specific goal. |
||||
- There is a starting point and and ending point, which is the goal of the user. |
||||
- There is a series of actions organized in rectangles (actions) or diamond (choice). |
||||
- The actions are linked with arrows. |
||||
|
||||
#### Criteria |
||||
|
||||
- User Flow |
||||
|
||||
Make sure for each flow: |
||||
|
||||
- The user has a specific goal |
||||
- There is a starting point and and ending point - which is the goal of the user |
||||
- There is a series of actions organised in rectangles (actions) or diamond (choice) |
||||
- The actions are linked with arrows |
||||
|
||||
- Card sorting |
||||
|
||||
Make sure |
||||
|
||||
- There is a script including the research goals. |
||||
- The research goals must be close to "rearrange the content" |
||||
- There are pictures of the ongoing workshop |
||||
- There is a new content organization shown in a table with sticky notes (it can be a picture or digital) |
||||
- Card sorting |
||||
Make sure that: |
||||
- There is a script including the research goals. |
||||
- The research goals are close to "rearrange the content". |
||||
- There are pictures of the ongoing workshop. |
||||
- There is a new content organization shown in a table with sticky notes (it can be a picture or digital). |
||||
|
||||
**Tips:** |
||||
|
||||
- Use as many tools as needed, and make sure you do all the process in 4 working days! |
||||
- You may use Card Sorting and User flows. |
||||
- Vocabulary: |
||||
- Low-Fidelity: Paper Prototypes - [Example here](https://miro.medium.com/max/1400/1*5nUfqqA2gjdAYHagjbHA5w.jpeg) |
||||
- Mid-Fidelity: Wireframes - black and white, only the main elements, on digital prototype tools - [Example here](https://miro.medium.com/max/1400/1*eGSfaxwYbxUFomYbyO6GWw.png) |
||||
- High-Fidelity: Wireframes with color, styles, graphical details, and micro-interactions - [Example here](https://miro.medium.com/max/1400/1*Xn0HSKAvhr4TZzC9lN5udw.gif) |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
@ -1,17 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there a paper prototype with 6 to 12 different screens? |
||||
###### Are there mid-fidelity wireframes on Figma? |
||||
###### Do the mid-fidelity wireframes match the paper prototype? |
||||
###### Are the paper prototypes and wireframes in black, grey and white and do not include any style elements? |
||||
###### Does each screen have the main navigation elements (arrows, menu, call to actions)? |
||||
###### Does each screen follow the other? |
||||
###### Is the navigation fluid from the beginning to the end? |
||||
###### If there are user flows or card-sorting, do they match the criteria (from the instructions section)? |
||||
###### Is there a PDF document with the key learnings the students learnt from this phase? |
@ -0,0 +1,31 @@
|
||||
## Second test protocol |
||||
|
||||
### Instructions |
||||
|
||||
Prepare a testing protocol and run it! |
||||
|
||||
Recommended steps: |
||||
|
||||
- Define the scope of the test. |
||||
- Recruit 5 users. |
||||
- Identify objectives: What are you proving? |
||||
- Establish metrics: How are you proving your design is efficient? |
||||
- Describe the steps and the instructions. |
||||
- Write an introduction to greet their user. |
||||
- Write a conclusion to thank the user. |
||||
|
||||
### Deliverables |
||||
|
||||
- A testing protocol script. |
||||
- Photos from the tests. |
||||
- A PDF file with the key learnings from the tests (5 tests are required) and from this phase. |
||||
- In the same PDF file you need to place at least 3 learnings or iteration suggestions to be made for the next version. |
||||
|
||||
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. |
||||
|
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
@ -0,0 +1,157 @@
|
||||
#### UX Strategy |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF or Figma)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is there a time frame? |
||||
|
||||
###### In Empathy or User Research, is there at least one tool, selected by the student, among the following list? |
||||
|
||||
- User interviews |
||||
- Analytics |
||||
- Competitive analysis |
||||
|
||||
###### In Define, is there at least one tool, selected by the student, among the following list? |
||||
|
||||
- Persona |
||||
- Empathy Map |
||||
- User Journey |
||||
- JBTD or Jobs-to-be-done |
||||
|
||||
###### Is there a “Problem Statement” spot? (ask the student to show you) |
||||
|
||||
###### In Ideation, is there at least one ideation technique? (ask the student to show you) |
||||
|
||||
###### Is there a “Prototype” spot that is either paper prototype or wireframe that contains at least one tool among the two following? |
||||
|
||||
- User Flow |
||||
- Card Sorting |
||||
|
||||
###### Is there a “Test” spot with at least 5 users? |
||||
|
||||
###### Does each of these five phases have a time frame? |
||||
|
||||
#### Empathy |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is at least one of the following tools used? |
||||
|
||||
- User interviews |
||||
- Analytics |
||||
- Competitive analysis |
||||
|
||||
###### Is the script completed (list of criteria in the instructions section)? |
||||
|
||||
###### Is the tool completed (list of criteria in the instructions section)? |
||||
|
||||
###### Is there a PDF document with the key learnings the students learnt from this phase? |
||||
|
||||
#### Fourth Problem Statement |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Is the deliverable in the correct format (PDF)? |
||||
|
||||
###### Is there a title within the document? |
||||
|
||||
###### Is the document clear, simple and easy to read? |
||||
|
||||
###### Is there one question that stands as a problem statement? |
||||
|
||||
###### Are there between 1 and 3 KPIs that will help you measure the success of the upcoming solution? |
||||
|
||||
###### Are there the key learnings the students learnt from this phase? |
||||
|
||||
#### Third Ideation |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is there a script of the ideation workshop? |
||||
|
||||
###### Is there the main objective in this script? |
||||
|
||||
###### Is there an ice breaker in this script? |
||||
|
||||
###### Are there the main steps of the ideation process in this script? |
||||
|
||||
###### Are there clear instructions in this script? |
||||
|
||||
###### Is there a time schedule for each step in this script? |
||||
|
||||
###### Is there a voting process to select the main idea in this script? |
||||
|
||||
###### Is there a board with all the ideas (on paper or digitally on Miro or Figma)? |
||||
|
||||
###### Is there one main concept out of the ideation workshop? |
||||
|
||||
###### Is there a document with the key learnings the students learnt from this phase? |
||||
|
||||
#### Prototype |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is there a paper prototype with 6 to 12 different screens? |
||||
|
||||
###### Are there mid-fidelity wireframes on Figma? |
||||
|
||||
###### Do the mid-fidelity wireframes match the paper prototype? |
||||
|
||||
###### Are the paper prototypes and wireframes in black, grey and white and do not include any style elements? |
||||
|
||||
###### Does each screen have the main navigation elements (arrows, menu, call to actions)? |
||||
|
||||
###### Does each screen follow the other? |
||||
|
||||
###### Is the navigation fluid from the beginning to the end? |
||||
|
||||
###### If there are user flows or card-sorting, do they match the criteria (from the instructions section)? |
||||
|
||||
###### Is there a PDF document with the key learnings the students learnt from this phase? |
||||
|
||||
#### Second test protocol |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is the scope clear: What are we testing? |
||||
|
||||
###### Are there either 5 names or a strategy to find users to interview? |
||||
|
||||
###### Are the objectives clear: What are we proving? |
||||
|
||||
###### Are the metrics clear to prove the test is efficient? |
||||
|
||||
###### Is there a greeting introduction? |
||||
|
||||
###### Are the instructions clear? |
||||
|
||||
###### Is there a conclusion to thank the user? |
||||
|
||||
###### Are there at least 3 learnings or iteration suggestions to be made for the next version? |
||||
|
||||
###### Is there a PDF document with the key learnings the student learned at this stage? |
@ -1,15 +0,0 @@
|
||||
# UX VII - Ex 7 - Test |
||||
|
||||
**Instructions:** |
||||
|
||||
Prepare a testing protocol and run it! |
||||
|
||||
**Deliverables:** |
||||
|
||||
- A testing protocol script |
||||
- Photos from the tests |
||||
- Key learnings from the tests (5 tests are required) |
||||
- Key learnings from this phase |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
@ -1,17 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is the scope clear: What are we testing? |
||||
###### Are there either 5 names or a strategy to find users? |
||||
###### Are the objectives clear: What are we proving? |
||||
###### Are the metrics clear to prove the test is efficient? |
||||
###### Is there a greeting introduction? |
||||
###### Are the instructions clear? |
||||
###### Is there a conclusion to thank the user? |
||||
###### Are there at least 3 learnings or iteration suggestions to be made for the next version? |
||||
###### Are there the key learnings the students learnt from this phase? |
@ -0,0 +1,21 @@
|
||||
## Third Ideation |
||||
|
||||
### Instructions |
||||
|
||||
Run at least one of the Ideation techniques in the design process. |
||||
|
||||
### Deliverables |
||||
|
||||
- A PDF document with the script of the tool context. |
||||
- Completed tool: a board with all the ideas - on paper or digitally on Miro or Figma. |
||||
- A PDF document with the key learnings from this phase. |
||||
|
||||
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. |
||||
|
||||
**Tips:** |
||||
|
||||
- Use as many tools as needed, and make sure you do all the process in 4 working days! |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
@ -1,23 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (PDF or Figma)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there a time frame? |
||||
###### In Empathy or User Research, is there at least one tool among the following list? |
||||
- User interviews |
||||
- Analytics |
||||
- Competitive analysis |
||||
###### In Define, is there at least one tool among the following list? |
||||
- Persona |
||||
- Empathy Map |
||||
- User Journey |
||||
- JBTD or Jobs-to-be-done |
||||
###### Is there a “Problem Statement” spot? |
||||
###### In Ideation, is there at least one ideation technique? |
||||
###### Is there a “Prototype” spot that is either paper prototype or wireframe that contains at least one tool among the two following? |
||||
- User Flow |
||||
- Card Sorting |
||||
###### Is there a “Test” spot with at least 5 users? |
||||
###### Does each of these five phases have a time frame? |
@ -1,25 +1,27 @@
|
||||
# UX VI - Ex 7 - Iteration |
||||
## Iteration |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Based on your previous tests, pick one of your 3 prototypes. |
||||
|
||||
Implement the 3 ideas you wrote down as suggestions. |
||||
Implement the 3 ideas you wrote down as suggestions. |
||||
|
||||
Run another series of test (and adapt your test protocol if necessary). |
||||
|
||||
Write a report with the conclusion you made out of this iteration loop. |
||||
Write a report with the conclusion you made out of this iteration loop. |
||||
|
||||
**Deliverables:** |
||||
### Deliverables |
||||
|
||||
- Pictures of the new test |
||||
- A report with your conclusions, your impressions and your key learnings from this iteration (PDF document out of Microsoft Word, Pages, Google Docs or any word-processing software) |
||||
- Comparison between V1 and V2 of the prototype in the report |
||||
- 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”. |
||||
- Pictures of the new test. |
||||
- A report with your conclusions, your impressions and your key learnings from this iteration (PDF document). |
||||
- Comparison between V1 and V2 of the prototype in the report. |
||||
|
||||
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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
**Tips:** |
||||
|
||||
- This report will be handed on to the CEO. Pay attention to the details and make sure the document is clean and easy to use! |
||||
|
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
@ -1,16 +1,83 @@
|
||||
#### Audit |
||||
#### Third user flow |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
#### In Flow n1, n2 and n3: |
||||
|
||||
###### Are there 3 user flows? |
||||
|
||||
###### Are the user flows about the features we gave on the readme? |
||||
|
||||
###### Does the user have a specific goal? |
||||
|
||||
###### Is there a starting and ending point? |
||||
|
||||
###### Is the ending point the goal of the user? |
||||
|
||||
###### Is there a series of actions organized in rectangles (actions) or diamonds (choices)? |
||||
|
||||
###### Are the actions linked with arrows? |
||||
|
||||
### Movie wireframes |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the deliverables in the correct format? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Are there pictures of the new test? |
||||
|
||||
#### In Flow n1, n2 and n3: |
||||
|
||||
###### Are there between 6 and 12 screens per flow? |
||||
|
||||
###### Is the sequence of links logical? |
||||
|
||||
###### Are the screens in black and white? |
||||
|
||||
#### Test on features |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Is there a PDF document with a test protocol for each wireframe? |
||||
|
||||
###### Are the tests goals written and explicit? |
||||
|
||||
###### Are there pictures of the ongoing tests? |
||||
|
||||
###### Is there a PDF document with 3 ideas to improve the prototype for each wireframe? |
||||
|
||||
#### Iteration |
||||
|
||||
###### Is there a zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
|
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
|
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
###### Are there pictures of the new test? |
||||
|
||||
###### Is there a PDF document with the report? |
||||
###### Are the V1 and V2 versions different? |
||||
###### Does the V2 version include the ideas from Ex 4, 5 or 6 (depending on the prototype you used)? |
||||
|
||||
###### Are the V1 and V2 versions different and included in the report? |
||||
|
||||
###### Does the V2 version include the ideas from the previous exercise "Test on Features" (depending on the prototype you used)? |
||||
|
||||
###### Does the report include the conclusions from this second series of test? |
||||
|
||||
###### Does the report include the personal impressions from the students? |
||||
###### Does the report include the students' key learnings? |
||||
###### Does the report include a comparison between V1 and V2? |
||||
|
||||
###### Does the report include the student key learnings? |
||||
|
||||
###### Does the report include a comparison between V1 and V2? |
||||
|
@ -0,0 +1,37 @@
|
||||
## Movie wireframes |
||||
|
||||
### Instructions |
||||
|
||||
Based on the 3 user flows, design 3 series of wireframes. |
||||
|
||||
### Deliverables |
||||
|
||||
- 3 series of wireframes (6 to 12 screens per flow) on Figma. |
||||
|
||||
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”. |
||||
|
||||
**Tips:** |
||||
|
||||
- Drawing paper prototypes before going digital might save you some time. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
- Vocabulary |
||||
- Low-Fidelity: Paper Prototypes - [Example here](https://miro.medium.com/max/1400/1*5nUfqqA2gjdAYHagjbHA5w.jpeg). |
||||
- Mid-Fidelity: Wireframes - black and white, only the main elements, on digital prototype tools - [Example here](https://miro.medium.com/max/1400/1*eGSfaxwYbxUFomYbyO6GWw.png). |
||||
- High-Fidelity: Wireframes with color, styles, graphical details, and micro-interactions - [Example here](https://miro.medium.com/max/1400/1*Xn0HSKAvhr4TZzC9lN5udw.gif). |
||||
|
||||
**Resources:** |
||||
|
||||
- [How to start sketching and wireframing](https://uxdesign.cc/how-to-start-sketching-and-wireframing-84a821f092e2) |
||||
- [Why should product teams use wireframes more often?](https://uxdesign.cc/why-should-product-teams-use-wireframes-more-often-60e34a2bc55) |
||||
- [The 5-pass reduction wireframing: A minimalist UX technique](https://uxdesign.cc/the-5-pass-reduction-wireframing-a-minimalist-ux-technique-aa415aad9ce2?sk=a218ac4db9d1049249bd381fbc5edeee) |
||||
- [The art of designing good wireframes](https://uxdesign.cc/the-art-of-designing-good-wireframes-8a2a9c10a95b) |
||||
|
||||
**Recommended tools:** |
||||
|
||||
- Figma. |
||||
|
||||
**Quote:** |
||||
|
||||
- "77% of users return to content and information sites because of ease-of-use. Only 22% return because the site belongs to a favorite brand." Forrester |
@ -1,25 +0,0 @@
|
||||
# UX VI - Ex 4 - Test on feature #1 |
||||
|
||||
**Instructions:** |
||||
|
||||
Test your wireframes! |
||||
|
||||
Focus on the 1st journey. Prepare a test protocol with your research goals (what you want to test), test it on 5 different people and write down 3 ways to improve the prototype. |
||||
|
||||
**Deliverables:** |
||||
|
||||
- A PDF document with a Test protocol |
||||
- Pictures of the ongoing tests |
||||
- A PDF document with 3 ideas to improve the prototype based on you users' feedbacks. |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [How to do a user interview (tutorial from Google Ventures)](https://www.youtube.com/watch?v=Qq3OiHQ-HCU) |
||||
- [Running a usability test](https://www.usability.gov/how-to-and-tools/methods/running-usability-tests.html) |
||||
- [Usability testing: what is it and how to do it?](https://uxdesign.cc/usability-testing-what-is-it-how-to-do-it-51356e5de5d) |
||||
- [Analyzing usability testing data](https://uxdesign.cc/analysing-usability-testing-data-97667ae4999e) |
||||
- [The art of guerrilla usability testing](http://www.uxbooth.com/articles/the-art-of-guerrilla-usability-testing/) |
||||
- [How to write a user testing report that people will actually read](https://uxdesign.cc/how-to-write-a-user-testing-report-that-people-will-actually-read-652d15d2f92e) |
@ -1,12 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there a PDF document with a protocol? |
||||
###### Are the test goals written and explicit? |
||||
###### Are there pictures of the ongoing test? |
||||
###### Is there a PDF document with 3 ideas to improve the prototype? |
@ -1,25 +0,0 @@
|
||||
# UX VI - Ex 5 - Test on feature #2 |
||||
|
||||
**Instructions:** |
||||
|
||||
Test your wireframes! |
||||
|
||||
Focus on the 2nd journey. Prepare a test protocol with your research goals (what you want to test), test it on 5 different people and write down 3 ways to improve the prototype. |
||||
|
||||
**Deliverables:** |
||||
|
||||
- A PDF document with a Test protocol |
||||
- Pictures of the ongoing tests |
||||
- A PDF document with 3 ideas to improve the prototype based on you users' feedbacks. |
||||
- 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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [How to do a user interview (tutorial from Google Ventures)](https://www.youtube.com/watch?v=Qq3OiHQ-HCU) |
||||
- [Running a usability test](https://www.usability.gov/how-to-and-tools/methods/running-usability-tests.html) |
||||
- [Usability testing: what is it and how to do it?](https://uxdesign.cc/usability-testing-what-is-it-how-to-do-it-51356e5de5d) |
||||
- [Analyzing usability testing data](https://uxdesign.cc/analysing-usability-testing-data-97667ae4999e) |
||||
- [The art of guerrilla usability testing](http://www.uxbooth.com/articles/the-art-of-guerrilla-usability-testing/) |
||||
- [How to write a user testing report that people will actually read](https://uxdesign.cc/how-to-write-a-user-testing-report-that-people-will-actually-read-652d15d2f92e) |
@ -1,12 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there a PDF document with a protocol? |
||||
###### Are the test goals written and explicit? |
||||
###### Are there pictures of the ongoing test? |
||||
###### Is there a PDF document with 3 ideas to improve the prototype? |
@ -1,12 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Is there a PDF document with a protocol? |
||||
###### Are the test goals written and explicit? |
||||
###### Are there pictures of the ongoing test? |
||||
###### Is there a PDF document with 3 ideas to improve the prototype? |
@ -1,21 +1,29 @@
|
||||
# UX VI - Ex 6 - Test on feature #3 |
||||
## Test on features |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Test your wireframes! |
||||
Test your wireframes! |
||||
|
||||
Focus on the 3rd journey. Prepare a test protocol with your research goals (what you want to test), test it on 5 different people and write down 3 ways to improve the prototype. |
||||
Focus on the journeys. Prepare a test protocol with your research goals (what you want to test), test it on 5 different people and write down 3 ways to improve the prototype. Do this for all your wireframes! |
||||
|
||||
**Deliverables**: |
||||
### Deliverables |
||||
|
||||
- A PDF document with a Test protocol |
||||
- Pictures of the ongoing tests |
||||
For each of the tests: |
||||
|
||||
- A PDF document with a test protocol. |
||||
- Pictures of the ongoing tests. |
||||
- A PDF document with 3 ideas to improve the prototype based on you users' feedbacks. |
||||
- 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”. |
||||
|
||||
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. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources**: |
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [How to do a user interview (tutorial from Google Ventures)](https://www.youtube.com/watch?v=Qq3OiHQ-HCU) |
||||
- [Running a usability test](https://www.usability.gov/how-to-and-tools/methods/running-usability-tests.html) |
@ -1,32 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
|
||||
#### In Flow n1: |
||||
###### Does the user have a specific goal? |
||||
###### Is there a starting point and |
||||
###### Is there an ending point? |
||||
###### Is the ending point the goal of the user? |
||||
###### Is there a series of actions organised in rectangles (actions) or diamonds (choices)? |
||||
###### Are the actions linked with arrows? |
||||
|
||||
#### In Flow n2: |
||||
###### Does the user have a specific goal? |
||||
###### Is there a starting point and |
||||
###### Is there an ending point? |
||||
###### Is the ending point the goal of the user? |
||||
###### Is there a series of actions organised in rectangles (actions) or diamonds (choices)? |
||||
###### Are the actions linked with arrows? |
||||
|
||||
#### In Flow n3: |
||||
###### Does the user have a specific goal? |
||||
###### Is there a starting point and |
||||
###### Is there an ending point? |
||||
###### Is the ending point the goal of the user? |
||||
###### Is there a series of actions organised in rectangles (actions) or diamonds (choices)? |
||||
###### Are the actions linked with arrows? |
@ -1,22 +1,26 @@
|
||||
# UX VI - Ex 3 - Wireframes animation |
||||
## Wireframes animation |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Animate your wireframes on Figma. |
||||
|
||||
Think about multistate!! |
||||
|
||||
This exercise is to be made individually. |
||||
This exercise is to be made individually. |
||||
|
||||
**Deliverables:** |
||||
### Deliverables |
||||
|
||||
- An animated prototype on Figma. |
||||
|
||||
Don't forget to: |
||||
|
||||
- An animated prototype on Figma |
||||
- Upload the Figma file 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 file. |
||||
- Pay attention to the global aspect of the file. It must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Tips:** |
||||
|
||||
**Resources:** |
||||
- Pay attention to the global aspect of the file. It must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
- [Efficiently Manage Your Designs - How Mockplus State Page Helps To View & Manage Multiple State](https://help.mockplus.com/p/372) |
||||
**Resources:** |
||||
|
||||
- [Efficiently Manage Your Designs - How Mockplus State Page Helps To View & Manage Multiple State](https://help.mockplus.com/p/372) |
||||
|
@ -1,10 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (Figma)? |
||||
###### Is there a title within the document? |
||||
###### Is the document clear, simple and easy to read? |
||||
###### Is there a starting screen? |
||||
###### Is there an ending screen? |
||||
###### Do all the connections between screens work? |
||||
###### Are there multistate buttons which change every time you click somewhere? |
@ -1,35 +0,0 @@
|
||||
# UX VI - Ex 2 - Wireframes |
||||
|
||||
**Instructions:** |
||||
|
||||
Based on the 3 user flows, design 3 series of wireframes. |
||||
|
||||
**Deliverables:** |
||||
|
||||
- 3 series of wireframes (6 to 12 screens per flow) on Figma |
||||
- 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”. |
||||
- Pay attention to the global aspect of the deliverables. They must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
|
||||
**Tips:** |
||||
|
||||
- Drawing paper prototypes before going digital might save you some time ;) |
||||
- Vocabulary |
||||
- Low-Fidelity: Paper Prototypes - [Example here](https://miro.medium.com/max/1400/1*5nUfqqA2gjdAYHagjbHA5w.jpeg) |
||||
- Mid-Fidelity: Wireframes - black and white, only the main elements, on digital prototype tools - [Example here](https://miro.medium.com/max/1400/1*eGSfaxwYbxUFomYbyO6GWw.png) |
||||
- High-Fidelity: Wireframes with color, styles, graphical details, and micro-interactions - [Example here](https://miro.medium.com/max/1400/1*Xn0HSKAvhr4TZzC9lN5udw.gif) |
||||
|
||||
**Resources:** |
||||
|
||||
- [How to start sketching and wireframing](https://uxdesign.cc/how-to-start-sketching-and-wireframing-84a821f092e2) |
||||
- [Why should product teams use wireframes more often?](https://uxdesign.cc/why-should-product-teams-use-wireframes-more-often-60e34a2bc55) |
||||
- [The 5-pass reduction wireframing: A minimalist UX technique](https://uxdesign.cc/the-5-pass-reduction-wireframing-a-minimalist-ux-technique-aa415aad9ce2?sk=a218ac4db9d1049249bd381fbc5edeee) |
||||
- [The art of designing good wireframes](https://uxdesign.cc/the-art-of-designing-good-wireframes-8a2a9c10a95b) |
||||
|
||||
**Recommended tools:** |
||||
|
||||
- Figma |
||||
|
||||
**Quote:** |
||||
|
||||
‘77% of users return to content and information sites because of ease-of-use. Only 22% return because the site belongs to a favorite brand.’ Forrester |
@ -1,25 +0,0 @@
|
||||
#### Audit |
||||
|
||||
|
||||
###### Is there a zip folder? |
||||
###### Is the zip folder labeled as “ProjectTitle_Name_FirstName”? |
||||
###### Are there all the deliverables indicated in the instructions? |
||||
###### Are the deliverables labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Are the deliverables in the correct format? |
||||
###### Are the documents clear, simple and easy to read? |
||||
###### Are there between 6 and 12 screens per flow? |
||||
|
||||
#### In Flow n1: |
||||
###### Are there between 6 and 12 screens per flow? |
||||
###### Is the sequence of links logical? |
||||
###### Are the screens in black and white? |
||||
|
||||
#### In Flow n2: |
||||
###### Are there between 6 and 12 screens per flow? |
||||
###### Is the sequence of links logical? |
||||
###### Are the screens in black and white? |
||||
|
||||
#### In Flow n3: |
||||
###### Are there between 6 and 12 screens per flow? |
||||
###### Is the sequence of links logical? |
||||
###### Are the screens in black and white? |
@ -1,20 +1,24 @@
|
||||
# UX IV - Ex 6 - Animation |
||||
## Animation |
||||
|
||||
**Instructions:** |
||||
### Instructions |
||||
|
||||
Animate your wireframes on Figma. |
||||
|
||||
Think about multistate!! |
||||
|
||||
This exercise is to be made individually. |
||||
This exercise is to be made individually. |
||||
|
||||
**Deliverable:** |
||||
|
||||
- An animated Mid-Fi prototype on Figma |
||||
- Upload the Figma file 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 file. |
||||
- Pay attention to the global aspect of the file. It must be clear, simple and easy to read. You can get inspiration on canva.com but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
**Deliverable:** |
||||
|
||||
- An animated Mid-Fi prototype on Figma. |
||||
|
||||
**Tips:** |
||||
|
||||
- Pay attention to the global aspect of the file. It must be clear, simple and easy to read. You can get inspiration [canva](https://www.canva.com/) but don’t overload your design with too much details! |
||||
|
||||
**Resources:** |
||||
|
||||
- [Efficiently Manage Your Designs - How Mockplus State Page Helps To View & Manage Multiple State](https://help.mockplus.com/p/372) |
||||
|
@ -1,9 +0,0 @@
|
||||
#### Audit |
||||
|
||||
###### Is the deliverable labeled as “Name_FirstName_DeliverableName_Date_VersionNumber”? |
||||
###### Is the deliverable in the correct format (Figma)? |
||||
###### Is there a title within the document? |
||||
###### Is there a starting screen? |
||||
###### Is there an ending screen? |
||||
###### Do all the connexions between screens work? |
||||
###### Are there multistate buttons that change every time you click somewhere? |
Some files were not shown because too many files changed in this diff diff.show_more
Loading…
Reference in new issue