diff --git a/subjects/prerequisite-admin.md b/subjects/prerequisite-admin.md new file mode 100644 index 0000000..defac07 --- /dev/null +++ b/subjects/prerequisite-admin.md @@ -0,0 +1,10 @@ +Here are some insights about the program: + +1. Students are encouraged to use Figma as a UX and UI tool. Is the students have a student certificate delivered by your administration, they will have access to a free plan. Please make sure you can deliver one to them. + +2. In some exercises and in the projects, we encourage studnets to talk to random people in the streets of in cafés, to ask them about their habits. Please make sure the students have a sufficient age to do so, based on your admission requirements. + +3. The projects are supposed to be done after the UX and the UI quest. Each project is divided in two parts, one focused on UX and the other one focused on UI. At the end of each part, the students will be invited to show their work in front of an audience of at least 5 people. Please make sure they have access to a screen to display they work and a room like a classroom, a meeting room or an auditorium. + + + diff --git a/subjects/prerequisite-students.md b/subjects/prerequisite-students.md new file mode 100644 index 0000000..42b9fab --- /dev/null +++ b/subjects/prerequisite-students.md @@ -0,0 +1,9 @@ +Here are some insights about the program: + +1. As a student, you are invited to send your documents by pushing them on GIthub. + +2. One of the main tools that is used in design is Figma. Ask a student certificate at the school administration services and enjoy a free plan as a student through this page: https://www.figma.com/education/students/ + +3. In some UX exercises, you will be invited to go outside the building and talk to people in the street. Get in touch with the school administration services to make sure your age is sufficient with the school rules. + +4. The projects are supposed to be done after the UX quest and the UI quest. Each project is divided in two parts, one that is focused on UX and one that is focused on UI. At the end of each part, you are supposed to show your work in front of an audience of at least 5 people who will be invited to give you feedback. \ No newline at end of file diff --git a/subjects/project-a-table/ui/README.md b/subjects/project-a-table/ui/README.md index d76cfa8..76d3cef 100644 --- a/subjects/project-a-table/ui/README.md +++ b/subjects/project-a-table/ui/README.md @@ -13,6 +13,9 @@ Show a tested high-fidelity prototype of each of the 4 journeys. - Prepare a feedback form to send the audience. The form must include at least the questions listed below. - Timing: 15 minutes for the presentation and 5 minutes for Q&A. - You may use the presentation audits to structure your presentations. +- 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! - Have fun! **Tools:** diff --git a/subjects/project-a-table/ux/README.md b/subjects/project-a-table/ux/README.md index ba2419e..4822675 100644 --- a/subjects/project-a-table/ux/README.md +++ b/subjects/project-a-table/ux/README.md @@ -41,6 +41,9 @@ The final presentation of your work will take place 2 weeks after the mid presen - Prepare a feedback form to send the audience. The form must include at least the questions listed below. - Timing: 15 minutes for the presentation and 5 minutes for Q&A. - You may use the presentation audits to structure your presentations. +- 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! - Have fun! **Tools:** diff --git a/subjects/project-get-a-room/ui/README.md b/subjects/project-get-a-room/ui/README.md index 47fb939..5300560 100644 --- a/subjects/project-get-a-room/ui/README.md +++ b/subjects/project-get-a-room/ui/README.md @@ -10,6 +10,9 @@ Show a tested high-fidelity prototype. - Test your prototypes with at least 5 people. - Make a presentation as if you were showing your work to your client. Make sure there are at least 5 people in the audience. +- 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! - Prepare a feedback form to send the audience. The form must include at least the questions listed below. - In both presentations, you are presenting to Barbara and her team. - Timing: 10 minutes for the presentation and 5 minutes for Q&A. diff --git a/subjects/project-get-a-room/ux/README.md b/subjects/project-get-a-room/ux/README.md index 3076ed3..f8bf010 100644 --- a/subjects/project-get-a-room/ux/README.md +++ b/subjects/project-get-a-room/ux/README.md @@ -23,6 +23,9 @@ The final presentation of your work will take place one week after the mid prese - You must interview or ask real people during the Empathy / User Research and Test phases. - In both phases, you must test your prototypes with at least 5 people. - Make a presentation as if you were showing your work to your client. Make sure there are at least 5 people in the audience. +- 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! - Prepare a feedback form to send the audience. The form must include at least the questions listed below. - In both presentations, you are presenting to Barbara and her team. - Timing: 10 minutes for the presentation and 5 minutes for Q&A. diff --git a/subjects/project-lets-do-some-sports/ui/README.md b/subjects/project-lets-do-some-sports/ui/README.md index 0211db6..5e49ede 100644 --- a/subjects/project-lets-do-some-sports/ui/README.md +++ b/subjects/project-lets-do-some-sports/ui/README.md @@ -10,6 +10,9 @@ Show a tested high-fidelity prototype. - Test your prototypes with at least 5 people. - Make a presentation as if you were showing your work to Yara. Make sure there are at least 5 people in the audience. +- 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! - Prepare a feedback form to send the audience. The form must include at least the questions listed below. - In both presentations, you are presenting to Barbara and her team. - Timing: 10 minutes for the presentation and 5 minutes for Q&A. diff --git a/subjects/project-lets-do-some-sports/ux/README.md b/subjects/project-lets-do-some-sports/ux/README.md index 5c25707..4fc2153 100644 --- a/subjects/project-lets-do-some-sports/ux/README.md +++ b/subjects/project-lets-do-some-sports/ux/README.md @@ -23,6 +23,9 @@ The final presentation of your work will take place one week after the mid prese - You may consider building your UX and UI strategy before jumping in. Remember to question the initial brief with user research. - Beware all the steps of the design process: Empathy, Define, Problem Statement, Ideation, Prototype, Test. - You must interview or ask real people during the Empathy / User Research and Test phases. +- 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! - In both phases, you must test your prototypes with at least 5 people. - Make a presentation as if you were showing your work to Yara. Make sure there are at least 5 people in the audience. - Prepare a feedback form to send the audience. The form must include at least the questions listed below. diff --git a/subjects/project-lets-fair-trade/ui/README.md b/subjects/project-lets-fair-trade/ui/README.md index 30d110d..b9e6446 100644 --- a/subjects/project-lets-fair-trade/ui/README.md +++ b/subjects/project-lets-fair-trade/ui/README.md @@ -10,6 +10,9 @@ Show a tested high-fidelity prototype. - Test your prototypes with at least 5 people. - Make a presentation as if you were showing your work to Bruno. Make sure there are at least 5 people in the audience. +- 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! - Prepare a feedback form to send the audience. The form must include at least the questions listed below. - In both presentations, you are presenting to Barbara and her team. - Timing: 10 minutes for the presentation and 5 minutes for Q&A. diff --git a/subjects/project-lets-fair-trade/ux/README.md b/subjects/project-lets-fair-trade/ux/README.md index 2a6877b..587c775 100644 --- a/subjects/project-lets-fair-trade/ux/README.md +++ b/subjects/project-lets-fair-trade/ux/README.md @@ -23,6 +23,9 @@ The final presentation of your work will take place 2 weeks after the mid presen - You must interview or ask real people during the Empathy / User Research and Test phases. - In both phases, you must test your prototypes with at least 5 people. - Make a presentation as if you were showing your work to Bruno. Make sure there are at least 5 people in the audience. +- 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! - Prepare a feedback form to send the audience. The form must include at least the questions listed below. - In both presentations, you are presenting to Barbara and her team. - Timing: 10 minutes for the presentation and 5 minutes for Q&A. diff --git a/subjects/ui/atomic-design/browsing/README.md b/subjects/ui/atomic-design/browsing/README.md index a02ad89..1a48541 100644 --- a/subjects/ui/atomic-design/browsing/README.md +++ b/subjects/ui/atomic-design/browsing/README.md @@ -24,8 +24,12 @@ Among these 4 websites, make snapshots of these elements: **Deliverables:** -- A PDF document extracted from a Figma file of 4 pages +- A Figma file of 4 pages - On each page, a screenshot of a template, an organism, a molecule and an atom +- 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:** diff --git a/subjects/ui/atomic-design/browsing/audit/README.md b/subjects/ui/atomic-design/browsing/audit/README.md index 750e0e5..fbc8918 100644 --- a/subjects/ui/atomic-design/browsing/audit/README.md +++ b/subjects/ui/atomic-design/browsing/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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 4 pages? #### On page 1, diff --git a/subjects/ui/atomic-design/design-system-library/README.md b/subjects/ui/atomic-design/design-system-library/README.md index eed469b..16084a8 100644 --- a/subjects/ui/atomic-design/design-system-library/README.md +++ b/subjects/ui/atomic-design/design-system-library/README.md @@ -10,7 +10,10 @@ Copy 10 elements from easyJet design system, including **Deliverable:** -- A PDF document extracted from a Figma file including 10 elements from easyJet design system +- A Figma file including 10 elements from easyJet design system +- 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:** diff --git a/subjects/ui/atomic-design/design-system-library/audit/README.md b/subjects/ui/atomic-design/design-system-library/audit/README.md index 8078a7c..4a2070c 100644 --- a/subjects/ui/atomic-design/design-system-library/audit/README.md +++ b/subjects/ui/atomic-design/design-system-library/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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 at least 10 elements from easyJet? ###### Is there at least one atom? ###### Is there at least one molecule? diff --git a/subjects/ui/atomic-design/library-for-a-dating-app/README.md b/subjects/ui/atomic-design/library-for-a-dating-app/README.md index 6a01785..efff9e9 100644 --- a/subjects/ui/atomic-design/library-for-a-dating-app/README.md +++ b/subjects/ui/atomic-design/library-for-a-dating-app/README.md @@ -8,16 +8,20 @@ Based on a moodboard you have composed, create a design system with at least 20 **Deliverables:** -- A PDF document extracted from a Figma file with a moodboard for a dating app. Include: +- A Figma file with a moodboard for a dating app. Include: - Pictures - Colors (2 to 3 main colors) - Typography -- A PDF document extracted from a Figma file with a library including +- A Figma file with a library including - At least graphic design 20 elements - At least one atom - At least one molecule - At least one organism - At least 5 multistate elements +- 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:** diff --git a/subjects/ui/atomic-design/library-for-a-dating-app/audit/README.md b/subjects/ui/atomic-design/library-for-a-dating-app/audit/README.md index 93061a4..b49f3a0 100644 --- a/subjects/ui/atomic-design/library-for-a-dating-app/audit/README.md +++ b/subjects/ui/atomic-design/library-for-a-dating-app/audit/README.md @@ -1,10 +1,16 @@ #### Audit -###### Is there a PDF moodboard for a dating app? +###### 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 moodboard for a dating app? ###### Are there pictures? ###### Are there 2 to 3 main colors? ###### Is there typography? -###### Is there a PDF library? +###### Is there a library? ###### Are there at least graphic design 20 elements (including the ones below)? ###### Is there at least one atom? ###### Is there at least one molecule? diff --git a/subjects/ui/atomic-design/library-for-climbing-addicts/README.md b/subjects/ui/atomic-design/library-for-climbing-addicts/README.md index bbe71f7..ec30199 100644 --- a/subjects/ui/atomic-design/library-for-climbing-addicts/README.md +++ b/subjects/ui/atomic-design/library-for-climbing-addicts/README.md @@ -8,16 +8,19 @@ Based on a moodboard, create a design system with at least 20 elements, includin **Deliverables:** -- A PDF document extracted from a Figma file with a moodboard for a climbing group. Include: +- A Figma file with a moodboard for a climbing group. Include: - Pictures - Colors (2 to 3 main colors) - Typography -- A PDF document extracted from a Figma file with a library including: +- A Figma file with a library including: - At least graphic design 20 elements - At least one atom - At least one molecule - At least one organism - At least 5 multistate elements +- 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:** diff --git a/subjects/ui/atomic-design/library-for-climbing-addicts/audit/README.md b/subjects/ui/atomic-design/library-for-climbing-addicts/audit/README.md index ae9d40a..d898976 100644 --- a/subjects/ui/atomic-design/library-for-climbing-addicts/audit/README.md +++ b/subjects/ui/atomic-design/library-for-climbing-addicts/audit/README.md @@ -1,10 +1,16 @@ #### Audit -###### Is there a PDF moodboard for a climbing group? +###### 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 moodboard for a climbing group? ###### Are there pictures? ###### Are there 2 to 3 main colors? ###### Is there typography? -###### Is there a PDF library? +###### Is there a library? ###### Are there at least graphic design 20 elements (including the one below)? ###### Is there at least one atom? ###### Is there at least one molecule? diff --git a/subjects/ui/atomic-design/material-design/README.md b/subjects/ui/atomic-design/material-design/README.md index 767a26e..603ae42 100644 --- a/subjects/ui/atomic-design/material-design/README.md +++ b/subjects/ui/atomic-design/material-design/README.md @@ -6,8 +6,11 @@ Download [this image](https://storage.googleapis.com/gd-wagtail-prod-assets/orig **Deliverables:** -- A PDF document extracted from a Figma file with the image +- A Figma file with the image - On each screen, indicate the layers order with numbers. 1 being the background image, 2 the element right on top, etc. +- 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:** diff --git a/subjects/ui/atomic-design/material-design/audit/README.md b/subjects/ui/atomic-design/material-design/audit/README.md index f9142ef..52edbd6 100644 --- a/subjects/ui/atomic-design/material-design/audit/README.md +++ b/subjects/ui/atomic-design/material-design/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document? +###### 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 the layers are indicated with numbers? diff --git a/subjects/ui/building-an-interface/animation/README.md b/subjects/ui/building-an-interface/animation/README.md index 720a868..ffb3d51 100644 --- a/subjects/ui/building-an-interface/animation/README.md +++ b/subjects/ui/building-an-interface/animation/README.md @@ -7,6 +7,9 @@ Animate your 5 screens on Figma. Think about multistate!! **Deliverable:** - An animated high-fidelity 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:** diff --git a/subjects/ui/building-an-interface/animation/audit/README.md b/subjects/ui/building-an-interface/animation/audit/README.md index e376657..7496f9f 100644 --- a/subjects/ui/building-an-interface/animation/audit/README.md +++ b/subjects/ui/building-an-interface/animation/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a Figma file? +###### 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? diff --git a/subjects/ui/building-an-interface/design-screens/README.md b/subjects/ui/building-an-interface/design-screens/README.md index 9bd27db..e718f9a 100644 --- a/subjects/ui/building-an-interface/design-screens/README.md +++ b/subjects/ui/building-an-interface/design-screens/README.md @@ -17,6 +17,9 @@ Use your components, call to actions and visuals to complete the wireframes. **Deliverables:** - 5 high-fidelity screens from 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:** diff --git a/subjects/ui/building-an-interface/design-screens/audit/README.md b/subjects/ui/building-an-interface/design-screens/audit/README.md index 3b2b75c..30b10a4 100644 --- a/subjects/ui/building-an-interface/design-screens/audit/README.md +++ b/subjects/ui/building-an-interface/design-screens/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a Figma file? +###### 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 5 screens? ###### Do style, colors, buttons, text match with the initial wireframes? \ No newline at end of file diff --git a/subjects/ui/building-an-interface/design-system-library/README.md b/subjects/ui/building-an-interface/design-system-library/README.md index c669716..9f125fc 100644 --- a/subjects/ui/building-an-interface/design-system-library/README.md +++ b/subjects/ui/building-an-interface/design-system-library/README.md @@ -6,12 +6,15 @@ Based on the moodboard you designed in Ex 1, create a design system with at leas **Deliverables:** -- A PDF document extracted from a Figma file with a library including +- A Figma file with a library including: - At least graphic design 30 elements - At least 5 atoms - At least 5 molecules - At least 5 organisms - At least 10 multistate variations +- 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:** diff --git a/subjects/ui/building-an-interface/design-system-library/audit/README.md b/subjects/ui/building-an-interface/design-system-library/audit/README.md index c47079e..e8f41bb 100644 --- a/subjects/ui/building-an-interface/design-system-library/audit/README.md +++ b/subjects/ui/building-an-interface/design-system-library/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF library? +###### 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 at least graphic design 30 elements ###### Are there at least 5 atoms? ###### Are there at least 5 molecules? diff --git a/subjects/ui/building-an-interface/desirability-testing/README.md b/subjects/ui/building-an-interface/desirability-testing/README.md index 402854e..6780c07 100644 --- a/subjects/ui/building-an-interface/desirability-testing/README.md +++ b/subjects/ui/building-an-interface/desirability-testing/README.md @@ -18,6 +18,11 @@ The point of this phase is to make sure the values and the spirit you chose for - Pictures from the desirability test - A PDF document with the outcomes of the desirability test - If the outcomes are not consistent with the values, 3 suggestions on how to make the moodboard and design library evolve. +- 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:** diff --git a/subjects/ui/building-an-interface/desirability-testing/audit/README.md b/subjects/ui/building-an-interface/desirability-testing/audit/README.md index afdc2ee..be7e9a1 100644 --- a/subjects/ui/building-an-interface/desirability-testing/audit/README.md +++ b/subjects/ui/building-an-interface/desirability-testing/audit/README.md @@ -1,5 +1,11 @@ #### 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 desirability testing board with 25+ different adjectives? ###### Are there pictures from the desirability test? ###### Is there a PDF document with the outcomes of the desirability test? diff --git a/subjects/ui/building-an-interface/styleguide/README.md b/subjects/ui/building-an-interface/styleguide/README.md index 1795e57..1c86097 100644 --- a/subjects/ui/building-an-interface/styleguide/README.md +++ b/subjects/ui/building-an-interface/styleguide/README.md @@ -20,7 +20,7 @@ Also think about the values and spirit you want to spread through this moodboard **Deliverables:** -- A PDF moodboard that includes: +- A Figma moodboard that includes: - Pictures - 2 to 3 main colors - Examples of typography applied to graphic elements @@ -28,6 +28,10 @@ Also think about the values and spirit you want to spread through this moodboard - Description or subtitle - Content - Button +- 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:** diff --git a/subjects/ui/building-an-interface/styleguide/audit/README.md b/subjects/ui/building-an-interface/styleguide/audit/README.md index 7776d80..d2bf3ab 100644 --- a/subjects/ui/building-an-interface/styleguide/audit/README.md +++ b/subjects/ui/building-an-interface/styleguide/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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? ###### Does the moodboard include pictures? ###### Does the moodboard include 2 to 3 main colors? ###### Is there typography for a title? diff --git a/subjects/ui/colors-and-moodboard/color-codes/README.md b/subjects/ui/colors-and-moodboard/color-codes/README.md index 791c925..9fc204a 100644 --- a/subjects/ui/colors-and-moodboard/color-codes/README.md +++ b/subjects/ui/colors-and-moodboard/color-codes/README.md @@ -6,7 +6,11 @@ Go to these 7 websites and make the color palettes out of them (3 to 4 main colo **Deliverable:** -- A PDF documents extracted from a Figma file including screenshots of the main page, URL, extracted colors and the matching color codes. +- A Figma file including screenshots of the main page, URL, extracted colors and the matching color codes. +- 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:** diff --git a/subjects/ui/colors-and-moodboard/color-codes/audit/README.md b/subjects/ui/colors-and-moodboard/color-codes/audit/README.md index dc1b895..aae9d12 100644 --- a/subjects/ui/colors-and-moodboard/color-codes/audit/README.md +++ b/subjects/ui/colors-and-moodboard/color-codes/audit/README.md @@ -1,4 +1,7 @@ #### Audit -###### Is there a PDF document? +###### 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? ###### Do the color codes match with the extracted colors ? You can use [Hex Color Codes](https://hexcolorcodes.org/) diff --git a/subjects/ui/colors-and-moodboard/color-combinations/README.md b/subjects/ui/colors-and-moodboard/color-combinations/README.md index 7c54aa9..8edc09a 100644 --- a/subjects/ui/colors-and-moodboard/color-combinations/README.md +++ b/subjects/ui/colors-and-moodboard/color-combinations/README.md @@ -15,11 +15,16 @@ Find 3 digital products (websites or apps) that use each kind of color palette c **Deliverable:** -- A PDF document extracted from a Figma file including for each +- A Figma file including for each digital product (websites or apps) - screenshots of the main page - the matching URL - the main colors and - the kind of color combination. +- 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:** diff --git a/subjects/ui/colors-and-moodboard/color-combinations/audit/README.md b/subjects/ui/colors-and-moodboard/color-combinations/audit/README.md index 8cab020..a93444a 100644 --- a/subjects/ui/colors-and-moodboard/color-combinations/audit/README.md +++ b/subjects/ui/colors-and-moodboard/color-combinations/audit/README.md @@ -1,7 +1,10 @@ #### Audit - -###### Do the websites or apps chosen by the students match with a correct color wheel combinations? +###### 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? +###### Do the websites or apps chosen match with a correct color wheel combinations? ###### Are there 3 websites or apps per color palette combination? ###### Are all websites or apps different from the examples in the instructions? diff --git a/subjects/ui/colors-and-moodboard/find-the-colors/README.md b/subjects/ui/colors-and-moodboard/find-the-colors/README.md index a8eebc9..02d6f88 100644 --- a/subjects/ui/colors-and-moodboard/find-the-colors/README.md +++ b/subjects/ui/colors-and-moodboard/find-the-colors/README.md @@ -10,7 +10,10 @@ Go to these 7 websites and make the color palettes out of them (3 to 4 main colo **Deliverable:** -- A PDF document extracted from a Figma file including screenshots of the main page, URL and extracted colors next to the screenshots. +- A Figma file including screenshots of the main page, URL and extracted colors next to the screenshots. +- 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:** diff --git a/subjects/ui/colors-and-moodboard/find-the-colors/audit/README.md b/subjects/ui/colors-and-moodboard/find-the-colors/audit/README.md index 2a13f54..ccad69a 100644 --- a/subjects/ui/colors-and-moodboard/find-the-colors/audit/README.md +++ b/subjects/ui/colors-and-moodboard/find-the-colors/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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 7 screenshots of the 7 pages or screens? ###### Does each screenshot have a URL next to it? ###### Do the main colors match with the ones from the screens? diff --git a/subjects/ui/colors-and-moodboard/moodboard/README.md b/subjects/ui/colors-and-moodboard/moodboard/README.md index 1e3f582..4b7169f 100644 --- a/subjects/ui/colors-and-moodboard/moodboard/README.md +++ b/subjects/ui/colors-and-moodboard/moodboard/README.md @@ -13,10 +13,13 @@ Create 4 different moodboards based on these 4 briefs and extract a color palett **Deliverables:** -- 1 PDF document extracted from a Figma file per moodboard +- A Figma file per moodboard - On each moodboard, several pictures (5 to 12) that are graphically consistent in terms of colors - The main colors extracted and shown on the side - One color code per color (RGB, Hex or HSB) +- 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:** diff --git a/subjects/ui/colors-and-moodboard/moodboard/audit/README.md b/subjects/ui/colors-and-moodboard/moodboard/audit/README.md index c7877cb..909e0d1 100644 --- a/subjects/ui/colors-and-moodboard/moodboard/audit/README.md +++ b/subjects/ui/colors-and-moodboard/moodboard/audit/README.md @@ -1,18 +1,27 @@ #### Audit -###### Are there 4 PDF extracted moodboards? +###### 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? + ###### On Moodboard #1, are there several pictures that are graphically consistent? ###### On Moodboard #1, are there 2 to 3 main colors that stand out ###### On Moodboard #1, do the colors have at least one code (RGB, Hex, or HSB) ###### On Moodboard #1, do the color code match with the designated color? [thanks to this tool](http://onlinewebtool.com/colorpicker.php) + ###### On Moodboard #2, are there several pictures that are graphically consistent? ###### On Moodboard #2, are there 2 to 3 main colors that stand out ###### On Moodboard #2, do the colors have at least one code (RGB, Hex, or HSB) ###### On Moodboard #2, do the color code match with the designated color? [thanks to this tool](http://onlinewebtool.com/colorpicker.php) + ###### On Moodboard #3, are there several pictures that are graphically consistent? ###### On Moodboard #3, are there 2 to 3 main colors that stand out ###### On Moodboard #3, do the colors have at least one code (RGB, Hex, or HSB) ###### On Moodboard #3, do the color code match with the designated color? [thanks to this tool](http://onlinewebtool.com/colorpicker.php) + ###### On Moodboard #4, are there several pictures that are graphically consistent? ###### On Moodboard #4, are there 2 to 3 main colors that stand out ###### On Moodboard #4, do the colors have at least one code (RGB, Hex, or HSB) diff --git a/subjects/ui/colors-and-moodboard/typography-moodboard/README.md b/subjects/ui/colors-and-moodboard/typography-moodboard/README.md index 4b4ff40..461b558 100644 --- a/subjects/ui/colors-and-moodboard/typography-moodboard/README.md +++ b/subjects/ui/colors-and-moodboard/typography-moodboard/README.md @@ -6,11 +6,14 @@ Find consistent typography for your moodboards from Ex. 4. **Deliverables:** -- A PDF document extracted from a Figma file with 4 moodboards from Ex. 4 and typography: +- A Figma file with 4 moodboards from Ex. 4 and typography: - 1 for a title - 1 for a button - 1 for a description - 1 for the text +- 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:** diff --git a/subjects/ui/colors-and-moodboard/typography-moodboard/audit/README.md b/subjects/ui/colors-and-moodboard/typography-moodboard/audit/README.md index 9404ac0..bf92fc9 100644 --- a/subjects/ui/colors-and-moodboard/typography-moodboard/audit/README.md +++ b/subjects/ui/colors-and-moodboard/typography-moodboard/audit/README.md @@ -1,6 +1,10 @@ #### Audit -###### Is there a PDF document? +###### 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 4 different fonts (one for each moodboard)? ###### On Moodboard #1, is there a typography for a title? ###### On Moodboard #1, is there a typography for a button? diff --git a/subjects/ui/colors-and-moodboard/typography/README.md b/subjects/ui/colors-and-moodboard/typography/README.md index b0d4462..a221420 100644 --- a/subjects/ui/colors-and-moodboard/typography/README.md +++ b/subjects/ui/colors-and-moodboard/typography/README.md @@ -17,7 +17,11 @@ Go to these websites and detect the typographies used. **Deliverables:** -- A PDF document extracted from a Figma file showing all the typographies used in each website or app. +- A Figma file showing all the typographies used in each website or app. +- 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:** diff --git a/subjects/ui/colors-and-moodboard/typography/audit/README.md b/subjects/ui/colors-and-moodboard/typography/audit/README.md index 8f83d49..1cf9605 100644 --- a/subjects/ui/colors-and-moodboard/typography/audit/README.md +++ b/subjects/ui/colors-and-moodboard/typography/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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 4 fonts from Unric.org? ###### Are there 3 fonts from Strongbowcider.org? ###### Are there 3 fonts from Bbqgrillsandfire.com? diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/README.md index 73be15d..10a9fa0 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/README.md @@ -14,6 +14,9 @@ Copy this image on Figma - You use overlays - You use masks to change the shape of an imported image - You use linear color function +- 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:** diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/audit/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/audit/README.md index a28d0b3..67db388 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/audit/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-bitcoin-dashboard/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a Figma file? +###### 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? ###### Does the designed screen match the image? ###### Do all layers have a name and belong to a group of graphic elements? diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-flight/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-flight/README.md index 4baeb56..c8efc0e 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-flight/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-flight/README.md @@ -14,6 +14,9 @@ Copy this image on Figma - All you layers are names and organized - You use overlays - You use masks to change the shape of an imported image (Amsterdam, Maldives, New Delhi, Sydney icons) +- 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:** diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-flight/audit/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-flight/audit/README.md index 3a24798..c4649c0 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-flight/audit/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-flight/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a Figma file? +###### 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? ###### Does the designed screen match the image? ###### Do all layers have a name and belong to a group of graphic elements? diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-spotify/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-spotify/README.md index c94c1ca..edd9846 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-spotify/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-spotify/README.md @@ -14,6 +14,9 @@ Copy this image on Figma - Named and organized layers - Apple design system (head bar) - Symbols and variants for the songs (1 page for the Symbols) +- 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:** diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-spotify/audit/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-spotify/audit/README.md index 9c6a002..18f381d 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-spotify/audit/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-spotify/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a Figma file ? +###### 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? ###### Does the designed screen match the image ###### Are there 2 pages: one for the screen and one with the symbols? diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-timer/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-timer/README.md index 9780e6e..e8377e7 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-timer/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-timer/README.md @@ -14,6 +14,9 @@ Copy this image on Figma. - Gradient to fill the main circle - Groups - Named layers +- 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:** diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-timer/audit/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-timer/audit/README.md index 9292c40..028fa23 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-timer/audit/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-timer/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a Figma File? +###### 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 two half circles as this one? ![Example](Timer2.png) diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-watches/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-watches/README.md index 118e800..1873f6a 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-watches/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-watches/README.md @@ -18,6 +18,9 @@ Copy these images on Figma - All your layers are named and organized - You use overlays - You use masks to change the shape of the imported image +- 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:** diff --git a/subjects/ui/colors-and-moodboard/ui-challenge-watches/audit/README.md b/subjects/ui/colors-and-moodboard/ui-challenge-watches/audit/README.md index e467241..25565aa 100644 --- a/subjects/ui/colors-and-moodboard/ui-challenge-watches/audit/README.md +++ b/subjects/ui/colors-and-moodboard/ui-challenge-watches/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a Figma file? +###### 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? ###### Do the designed screens designed match the images? ###### Do all layers have a name and belong to a group of graphic elements? diff --git a/subjects/ui/heuristics/audit/README.md b/subjects/ui/heuristics/audit/README.md index 99d56b3..ecc3bf0 100644 --- a/subjects/ui/heuristics/audit/README.md +++ b/subjects/ui/heuristics/audit/README.md @@ -20,6 +20,10 @@ Run a heuristic audit on one of these 3 different websites or app: - A completed chart - A report including the 5 recommended steps described below +- 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:** diff --git a/subjects/ui/heuristics/audit/audit/README.md b/subjects/ui/heuristics/audit/audit/README.md index f2acf70..279bff3 100644 --- a/subjects/ui/heuristics/audit/audit/README.md +++ b/subjects/ui/heuristics/audit/audit/README.md @@ -1,5 +1,11 @@ #### 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 chart? ###### Is the chart complete? ###### Are the 5 steps included in the report? \ No newline at end of file diff --git a/subjects/ui/heuristics/recommendations/README.md b/subjects/ui/heuristics/recommendations/README.md index f0ff1d9..d717a63 100644 --- a/subjects/ui/heuristics/recommendations/README.md +++ b/subjects/ui/heuristics/recommendations/README.md @@ -13,6 +13,9 @@ Based on the audit you made in Ex.1, write a set of 3 to 6 recommendations to im **Deliverable:** - A PDF document with 3 to 6 recommendations +- 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:** diff --git a/subjects/ui/heuristics/recommendations/audit/README.md b/subjects/ui/heuristics/recommendations/audit/README.md index 4dd0b0b..2176f4e 100644 --- a/subjects/ui/heuristics/recommendations/audit/README.md +++ b/subjects/ui/heuristics/recommendations/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document with the recommendations? +###### 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 recommendations consistent with the report's conclusions? ###### Do the recommendations fit in some of these criteria: - Visibility of system status diff --git a/subjects/ui/rules/accessbility-app/README.md b/subjects/ui/rules/accessbility-app/README.md index ca9c6d0..92a9065 100644 --- a/subjects/ui/rules/accessbility-app/README.md +++ b/subjects/ui/rules/accessbility-app/README.md @@ -6,7 +6,11 @@ Choose an app you find particularly accessible. Find at least 3 concrete example **Deliverables:** -- A 3-page PDF document extracted from a Figma file with 3 different elements from an app (it can be from 3 different apps) that are accessible. The three measures must be different. +- A 3-page Figma file with 3 different elements from an app (it can be from 3 different apps) that are accessible. The three measures must be different. +- 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:** diff --git a/subjects/ui/rules/accessbility-app/audit/README.md b/subjects/ui/rules/accessbility-app/audit/README.md index 69c1cf1..22f38c3 100644 --- a/subjects/ui/rules/accessbility-app/audit/README.md +++ b/subjects/ui/rules/accessbility-app/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there is a PDF document? +###### 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? ###### At least 3 different measures have been shown, like in the instructions section? diff --git a/subjects/ui/rules/accessbility-website/README.md b/subjects/ui/rules/accessbility-website/README.md index 3649cee..482536c 100644 --- a/subjects/ui/rules/accessbility-website/README.md +++ b/subjects/ui/rules/accessbility-website/README.md @@ -6,7 +6,11 @@ Choose a website you find particularly accessible. Find at least 3 concrete exam **Deliverables:** -- A 3-page PDF document extracted from a Figma file with 3 different elements from a website (it can be from 3 different websites) that are accessible. The three measures must be different. +- A 3-page Figma file with 3 different elements from a website (it can be from 3 different websites) that are accessible. The three measures must be different. +- 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:** diff --git a/subjects/ui/rules/accessbility-website/audit/README.md b/subjects/ui/rules/accessbility-website/audit/README.md index c9c7261..1e9695f 100644 --- a/subjects/ui/rules/accessbility-website/audit/README.md +++ b/subjects/ui/rules/accessbility-website/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there is a PDF document? +###### 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? ###### At least 3 different measures have been shown, like in the instructions section? diff --git a/subjects/ui/rules/breadcrumbs/README.md b/subjects/ui/rules/breadcrumbs/README.md index 6dc9f2f..1833f77 100644 --- a/subjects/ui/rules/breadcrumbs/README.md +++ b/subjects/ui/rules/breadcrumbs/README.md @@ -6,7 +6,11 @@ Browse the internet and find at least 5 different examples of breadcrumbs from w **Deliverable:** -- A PDF document extracted from a Figma file gathering 5 screenshots of breadcrumbs. +- A Figma file gathering 5 screenshots of breadcrumbs. +- 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:** diff --git a/subjects/ui/rules/breadcrumbs/audit/README.md b/subjects/ui/rules/breadcrumbs/audit/README.md index 6f299a8..dd936ca 100644 --- a/subjects/ui/rules/breadcrumbs/audit/README.md +++ b/subjects/ui/rules/breadcrumbs/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document with a proper title? +###### 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 are at least 5 different examples of breadcrumbs? ###### Is the name of each app or website written? \ No newline at end of file diff --git a/subjects/ui/rules/calendars/README.md b/subjects/ui/rules/calendars/README.md index 1232869..112de8c 100644 --- a/subjects/ui/rules/calendars/README.md +++ b/subjects/ui/rules/calendars/README.md @@ -6,4 +6,8 @@ Browse the internet and find at least 5 different examples of calendars from web **Deliverable:** -- A PDF document extracted from a Figma file gathering 5 screenshots of calendars. +- A Figma file gathering 5 screenshots of calendars. +- 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! + diff --git a/subjects/ui/rules/calendars/audit/README.md b/subjects/ui/rules/calendars/audit/README.md index e711c44..a6f47d2 100644 --- a/subjects/ui/rules/calendars/audit/README.md +++ b/subjects/ui/rules/calendars/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there is a PDF document with a proper title? +###### 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 at least 5 examples of calendars? ###### Is the name of each app or website written? \ No newline at end of file diff --git a/subjects/ui/rules/consistency/README.md b/subjects/ui/rules/consistency/README.md index 0c1d0b5..8db9810 100644 --- a/subjects/ui/rules/consistency/README.md +++ b/subjects/ui/rules/consistency/README.md @@ -8,7 +8,11 @@ Pick a website or an app of your choice*. Highlight 5 signs of consistency acros **Deliverable:** -- A PDF document extracted from a Figma file gathering at least 5 signs of consistency. +- A Figma file gathering at least 5 signs of consistency. +- 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:** diff --git a/subjects/ui/rules/consistency/audit/README.md b/subjects/ui/rules/consistency/audit/README.md index 83e62c9..146bd08 100644 --- a/subjects/ui/rules/consistency/audit/README.md +++ b/subjects/ui/rules/consistency/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document with a proper title? +###### 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 at least 5 signs of consistency? ###### Is the name of each app or website written? diff --git a/subjects/ui/rules/grids/README.md b/subjects/ui/rules/grids/README.md index 77a5a4a..8a04b53 100644 --- a/subjects/ui/rules/grids/README.md +++ b/subjects/ui/rules/grids/README.md @@ -16,8 +16,11 @@ Open these 5 images on Figma and draw lines and grids every time you find aligne **Deliverables:** -- A PDF document extracted from a Figma file -- The file should include the screens with lines on top to show grids. One PDF page per screen or frame. +- A Figma file including the screens with lines on top to show grids. One page per screen or frame. +- 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:** diff --git a/subjects/ui/rules/grids/audit/README.md b/subjects/ui/rules/grids/audit/README.md index a7cb4c9..4bf041e 100644 --- a/subjects/ui/rules/grids/audit/README.md +++ b/subjects/ui/rules/grids/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there one PDF of one page per image? +###### 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 colored lines on top of the images? ###### Do the lines highlight aligned elements? diff --git a/subjects/ui/rules/micro-interactions/README.md b/subjects/ui/rules/micro-interactions/README.md index fb0be46..28e2a43 100644 --- a/subjects/ui/rules/micro-interactions/README.md +++ b/subjects/ui/rules/micro-interactions/README.md @@ -8,7 +8,11 @@ Be careful! Feedback is helpful to provide information to the user, not just sho **Deliverable:** -- A PDF document extracted from a Figma file gathering 5 examples of **feedback** micro-interactions or animations. In each example, show the different versions of the element. +- A Figma file gathering 5 examples of **feedback** micro-interactions or animations. In each example, show the different versions of the element. +- 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:** diff --git a/subjects/ui/rules/micro-interactions/audit/README.md b/subjects/ui/rules/micro-interactions/audit/README.md index 073ce7a..8da08cd 100644 --- a/subjects/ui/rules/micro-interactions/audit/README.md +++ b/subjects/ui/rules/micro-interactions/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document with a proper title? +###### 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 at least 5 examples of micro-interactions or animations? ###### Is the name of each app or website written? \ No newline at end of file diff --git a/subjects/ui/rules/multi-state/README.md b/subjects/ui/rules/multi-state/README.md index 8674879..51a7fbd 100644 --- a/subjects/ui/rules/multi-state/README.md +++ b/subjects/ui/rules/multi-state/README.md @@ -10,7 +10,11 @@ Find at least five combinations of multi state elements. **Deliverables:** -- A PDF document extracted from a Figma file with 5 combinations of multi state elements +- A Figma file with 5 combinations of multi state elements. +- 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:** diff --git a/subjects/ui/rules/multi-state/audit/README.md b/subjects/ui/rules/multi-state/audit/README.md index a613a5e..b02aa90 100644 --- a/subjects/ui/rules/multi-state/audit/README.md +++ b/subjects/ui/rules/multi-state/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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 at least five combinations of buttons, menus or call to actions? ###### Are the multi state buttons gathered in groups? ###### Is the document clean and the elements aligned? diff --git a/subjects/ui/rules/radio-buttons/README.md b/subjects/ui/rules/radio-buttons/README.md index 0954491..f1c23a4 100644 --- a/subjects/ui/rules/radio-buttons/README.md +++ b/subjects/ui/rules/radio-buttons/README.md @@ -6,7 +6,11 @@ Browse the internet and find at least 5 different examples of radio buttons from **Deliverable:** -- A PDF document extracted from a Figma file gathering 5 screenshots of radio buttons. +- A Figma file gathering 5 screenshots of radio buttons. +- 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:** diff --git a/subjects/ui/rules/radio-buttons/audit/README.md b/subjects/ui/rules/radio-buttons/audit/README.md index 26d58f8..3fbdfd8 100644 --- a/subjects/ui/rules/radio-buttons/audit/README.md +++ b/subjects/ui/rules/radio-buttons/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document with a proper title? +###### 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 at least 5 examples of radio buttons? ###### Is the name of each app or website written? \ No newline at end of file diff --git a/subjects/ui/rules/time-pickers/README.md b/subjects/ui/rules/time-pickers/README.md index cc87a95..bffa072 100644 --- a/subjects/ui/rules/time-pickers/README.md +++ b/subjects/ui/rules/time-pickers/README.md @@ -6,4 +6,8 @@ Browse the internet and find at least 5 different examples of time pickers from **Deliverable:** -- A PDF document extracted from a Figma file gathering 5 screenshots of time pickers. +- A Figma file gathering 5 screenshots of time pickers. +- 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! + diff --git a/subjects/ui/rules/time-pickers/audit/README.md b/subjects/ui/rules/time-pickers/audit/README.md index ae57abb..cd7969f 100644 --- a/subjects/ui/rules/time-pickers/audit/README.md +++ b/subjects/ui/rules/time-pickers/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document with a proper title? +###### 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 at least 5 examples of time pickers? ###### Is the name of each app or website written? \ No newline at end of file diff --git a/subjects/ui/rules/toggle-buttons/README.md b/subjects/ui/rules/toggle-buttons/README.md index e594a0c..5f1912e 100644 --- a/subjects/ui/rules/toggle-buttons/README.md +++ b/subjects/ui/rules/toggle-buttons/README.md @@ -6,7 +6,11 @@ Browse the internet and find at least 5 different examples of toggle buttons fro **Deliverable:** -- A PDF document extracted from a Figma file gathering 5 screenshots of toggle buttons. +- A Figma file gathering 5 screenshots of toggle buttons. +- 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:** diff --git a/subjects/ui/rules/toggle-buttons/audit/README.md b/subjects/ui/rules/toggle-buttons/audit/README.md index c350b2a..3637651 100644 --- a/subjects/ui/rules/toggle-buttons/audit/README.md +++ b/subjects/ui/rules/toggle-buttons/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document with a proper title? +###### 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 at least 5 examples of toggle buttons? ###### Is the name of each app or website written? \ No newline at end of file diff --git a/subjects/ux/athele-keep-hydrated/analytics/README.md b/subjects/ux/athele-keep-hydrated/analytics/README.md index 4bbf3f5..1fbaf8a 100644 --- a/subjects/ux/athele-keep-hydrated/analytics/README.md +++ b/subjects/ux/athele-keep-hydrated/analytics/README.md @@ -8,6 +8,11 @@ Read these articles and extract at least 5 key figures or insights that may be u - 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! + + **Resources:** diff --git a/subjects/ux/athele-keep-hydrated/analytics/audit/README.md b/subjects/ux/athele-keep-hydrated/analytics/audit/README.md index 3525f38..25028a1 100644 --- a/subjects/ux/athele-keep-hydrated/analytics/audit/README.md +++ b/subjects/ux/athele-keep-hydrated/analytics/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document? +###### 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? diff --git a/subjects/ux/athele-keep-hydrated/ideation/README.md b/subjects/ux/athele-keep-hydrated/ideation/README.md index cc09984..a0fd20b 100644 --- a/subjects/ux/athele-keep-hydrated/ideation/README.md +++ b/subjects/ux/athele-keep-hydrated/ideation/README.md @@ -48,6 +48,11 @@ Find 3 friends outside of the program and run a quick ideation session (20 minut - Pictures of the session - A board with all the ideas (on paper or digitally on Miro or Figma) - One main idea to solve the problem next to the board +- 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:** diff --git a/subjects/ux/athele-keep-hydrated/ideation/audit/README.md b/subjects/ux/athele-keep-hydrated/ideation/audit/README.md index 1efabc6..a196ed4 100644 --- a/subjects/ux/athele-keep-hydrated/ideation/audit/README.md +++ b/subjects/ux/athele-keep-hydrated/ideation/audit/README.md @@ -1,5 +1,11 @@ #### 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? \ No newline at end of file +###### Is there one main idea to solve the problem? diff --git a/subjects/ux/athele-keep-hydrated/personas/README.md b/subjects/ux/athele-keep-hydrated/personas/README.md index 96e3075..bccc666 100644 --- a/subjects/ux/athele-keep-hydrated/personas/README.md +++ b/subjects/ux/athele-keep-hydrated/personas/README.md @@ -7,6 +7,10 @@ **Deliverables:** - A user persona on a PDF document +- 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:** diff --git a/subjects/ux/athele-keep-hydrated/personas/audit/README.md b/subjects/ux/athele-keep-hydrated/personas/audit/README.md index d9dfd8c..4e0c2f6 100644 --- a/subjects/ux/athele-keep-hydrated/personas/audit/README.md +++ b/subjects/ux/athele-keep-hydrated/personas/audit/README.md @@ -1,6 +1,10 @@ #### Audit instructions -###### Is there a PDF document with Pierre's persona card? +###### 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? diff --git a/subjects/ux/athele-keep-hydrated/problem-statement/README.md b/subjects/ux/athele-keep-hydrated/problem-statement/README.md index 7ced2ef..de88454 100644 --- a/subjects/ux/athele-keep-hydrated/problem-statement/README.md +++ b/subjects/ux/athele-keep-hydrated/problem-statement/README.md @@ -7,6 +7,9 @@ Based on the insights from the analytics and user interviews, comment the scope **Deliverables:** - 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:** diff --git a/subjects/ux/athele-keep-hydrated/problem-statement/audit/README.md b/subjects/ux/athele-keep-hydrated/problem-statement/audit/README.md index 2ddaea0..6234670 100644 --- a/subjects/ux/athele-keep-hydrated/problem-statement/audit/README.md +++ b/subjects/ux/athele-keep-hydrated/problem-statement/audit/README.md @@ -1,6 +1,9 @@ #### Audit -##### Is there a PDF document? +###### 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)? \ No newline at end of file diff --git a/subjects/ux/athele-keep-hydrated/prototyping/README.md b/subjects/ux/athele-keep-hydrated/prototyping/README.md index a44db3f..1d07de7 100644 --- a/subjects/ux/athele-keep-hydrated/prototyping/README.md +++ b/subjects/ux/athele-keep-hydrated/prototyping/README.md @@ -8,7 +8,10 @@ Design a storyboard of Pierre (or your persona) using your idea as a solution. S **Deliverables:** -- 1 storyboard to describe your solution, on paper +- 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”. +- 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:** diff --git a/subjects/ux/athele-keep-hydrated/prototyping/audit/README.md b/subjects/ux/athele-keep-hydrated/prototyping/audit/README.md index 2f3ab2d..81bf6ed 100644 --- a/subjects/ux/athele-keep-hydrated/prototyping/audit/README.md +++ b/subjects/ux/athele-keep-hydrated/prototyping/audit/README.md @@ -1,5 +1,10 @@ #### 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 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? diff --git a/subjects/ux/athele-keep-hydrated/user-interviews/README.md b/subjects/ux/athele-keep-hydrated/user-interviews/README.md index 0a991a7..ae211f8 100644 --- a/subjects/ux/athele-keep-hydrated/user-interviews/README.md +++ b/subjects/ux/athele-keep-hydrated/user-interviews/README.md @@ -29,6 +29,10 @@ Failure is even a necessary step, but ideally it should happen before a product **Deliverables:** - Create a PDF document and write at least 6 insights and the name of the person(s) who said it. +- 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:** diff --git a/subjects/ux/athele-keep-hydrated/user-interviews/audit/README.md b/subjects/ux/athele-keep-hydrated/user-interviews/audit/README.md index 6413773..a228d3e 100644 --- a/subjects/ux/athele-keep-hydrated/user-interviews/audit/README.md +++ b/subjects/ux/athele-keep-hydrated/user-interviews/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a PDF document? +###### 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? diff --git a/subjects/ux/athele-keep-hydrated/user-journey/README.md b/subjects/ux/athele-keep-hydrated/user-journey/README.md index bdedad5..ebb5491 100644 --- a/subjects/ux/athele-keep-hydrated/user-journey/README.md +++ b/subjects/ux/athele-keep-hydrated/user-journey/README.md @@ -6,7 +6,10 @@ Based on your persona card, and the interview scripts, design Pierre’s user jo **Deliverables:** -- A PDF document with Pierre’s user journey. +- A Figma file with Pierre’s user journey. +- 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:** diff --git a/subjects/ux/athele-keep-hydrated/user-journey/audit/README.md b/subjects/ux/athele-keep-hydrated/user-journey/audit/README.md index 1c56ecf..5733a3b 100644 --- a/subjects/ux/athele-keep-hydrated/user-journey/audit/README.md +++ b/subjects/ux/athele-keep-hydrated/user-journey/audit/README.md @@ -1,6 +1,10 @@ #### Audit -###### Is there a timeline? +###### 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? diff --git a/subjects/ux/going-on-holidays-with-friends/affinity-diagram/README.md b/subjects/ux/going-on-holidays-with-friends/affinity-diagram/README.md index e65fcd2..ea0c4ee 100644 --- a/subjects/ux/going-on-holidays-with-friends/affinity-diagram/README.md +++ b/subjects/ux/going-on-holidays-with-friends/affinity-diagram/README.md @@ -13,8 +13,11 @@ Open your written scripts and extract the relevant information. **Deliverables:** -- An Affinity Diagram (paper or on digital tools like Miro) -- An Empathy Map (paper or on digital tools like Miro) +- 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:** diff --git a/subjects/ux/going-on-holidays-with-friends/affinity-diagram/audit/README.md b/subjects/ux/going-on-holidays-with-friends/affinity-diagram/audit/README.md index e10afc3..51444b6 100644 --- a/subjects/ux/going-on-holidays-with-friends/affinity-diagram/audit/README.md +++ b/subjects/ux/going-on-holidays-with-friends/affinity-diagram/audit/README.md @@ -1,5 +1,11 @@ #### 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? diff --git a/subjects/ux/going-on-holidays-with-friends/ideation/README.md b/subjects/ux/going-on-holidays-with-friends/ideation/README.md index a7bffd8..1a28193 100644 --- a/subjects/ux/going-on-holidays-with-friends/ideation/README.md +++ b/subjects/ux/going-on-holidays-with-friends/ideation/README.md @@ -13,6 +13,9 @@ Get as many ideas as possible within a defined timeframe, and narrow them down t - A PDF document that includes the script with all the steps + logistics - Pictures of the 2 sessions - A PDF document with 3 ideas that came out the 2 workshops. +- 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:** diff --git a/subjects/ux/going-on-holidays-with-friends/ideation/audit/README.md b/subjects/ux/going-on-holidays-with-friends/ideation/audit/README.md index f4bd23f..3085267 100644 --- a/subjects/ux/going-on-holidays-with-friends/ideation/audit/README.md +++ b/subjects/ux/going-on-holidays-with-friends/ideation/audit/README.md @@ -1,6 +1,11 @@ #### Audit -###### Is there a PDF document with the script of the workshop? +###### 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? diff --git a/subjects/ux/going-on-holidays-with-friends/interview-guide/README.md b/subjects/ux/going-on-holidays-with-friends/interview-guide/README.md index a30f479..e71b183 100644 --- a/subjects/ux/going-on-holidays-with-friends/interview-guide/README.md +++ b/subjects/ux/going-on-holidays-with-friends/interview-guide/README.md @@ -17,6 +17,10 @@ And remember, you are not your user! **Deliverable:** - A PDF document with an interview guide +- 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:** Here are the recommended steps : diff --git a/subjects/ux/going-on-holidays-with-friends/interview-guide/audit/README.md b/subjects/ux/going-on-holidays-with-friends/interview-guide/audit/README.md index bc6e798..54a6040 100644 --- a/subjects/ux/going-on-holidays-with-friends/interview-guide/audit/README.md +++ b/subjects/ux/going-on-holidays-with-friends/interview-guide/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document with the interview script? +###### 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? diff --git a/subjects/ux/going-on-holidays-with-friends/problem-statement/README.md b/subjects/ux/going-on-holidays-with-friends/problem-statement/README.md index 01c3c08..7a1d8d6 100644 --- a/subjects/ux/going-on-holidays-with-friends/problem-statement/README.md +++ b/subjects/ux/going-on-holidays-with-friends/problem-statement/README.md @@ -9,6 +9,9 @@ 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:** diff --git a/subjects/ux/going-on-holidays-with-friends/problem-statement/audit/README.md b/subjects/ux/going-on-holidays-with-friends/problem-statement/audit/README.md index a638a75..17ed107 100644 --- a/subjects/ux/going-on-holidays-with-friends/problem-statement/audit/README.md +++ b/subjects/ux/going-on-holidays-with-friends/problem-statement/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document ? +###### 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 diff --git a/subjects/ux/going-on-holidays-with-friends/prototyping/README.md b/subjects/ux/going-on-holidays-with-friends/prototyping/README.md index 9ac1711..91455e8 100644 --- a/subjects/ux/going-on-holidays-with-friends/prototyping/README.md +++ b/subjects/ux/going-on-holidays-with-friends/prototyping/README.md @@ -10,8 +10,12 @@ Give another dimension to your user flow and turn your user flow into a paper pr **Deliverables:** -- A paper prototype -- Wireframes (mid-fi) to upload on the Figma +- Pictures of a paper prototype +- Wireframes (mid-fi) to upload on the Figma file +- 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:** Vocabulary diff --git a/subjects/ux/going-on-holidays-with-friends/prototyping/audit/README.md b/subjects/ux/going-on-holidays-with-friends/prototyping/audit/README.md index d4ab60b..93681f6 100644 --- a/subjects/ux/going-on-holidays-with-friends/prototyping/audit/README.md +++ b/subjects/ux/going-on-holidays-with-friends/prototyping/audit/README.md @@ -1,6 +1,12 @@ #### Audit -###### Is there a paper prototype? +###### 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? diff --git a/subjects/ux/going-on-holidays-with-friends/run-interviews/README.md b/subjects/ux/going-on-holidays-with-friends/run-interviews/README.md index fbdd864..fd83b18 100644 --- a/subjects/ux/going-on-holidays-with-friends/run-interviews/README.md +++ b/subjects/ux/going-on-holidays-with-friends/run-interviews/README.md @@ -11,4 +11,7 @@ Then, write down the script on a written document, and give elements of context **Deliverables:** -- A PDF document with the scripts from all the 6 interviews. \ No newline at end of file +- 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! diff --git a/subjects/ux/going-on-holidays-with-friends/run-interviews/audit/README.md b/subjects/ux/going-on-holidays-with-friends/run-interviews/audit/README.md index 788effe..ae44b96 100644 --- a/subjects/ux/going-on-holidays-with-friends/run-interviews/audit/README.md +++ b/subjects/ux/going-on-holidays-with-friends/run-interviews/audit/README.md @@ -1,6 +1,10 @@ #### Audit -###### Is there a PDF document with the scripts from all the 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 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 question from the interview guide match the written script of the interview? \ No newline at end of file +###### Do the questions from the interview guide match the written script of the interview? \ No newline at end of file diff --git a/subjects/ux/going-on-holidays-with-friends/user-flow/README.md b/subjects/ux/going-on-holidays-with-friends/user-flow/README.md index 22631eb..2ca7bd6 100644 --- a/subjects/ux/going-on-holidays-with-friends/user-flow/README.md +++ b/subjects/ux/going-on-holidays-with-friends/user-flow/README.md @@ -7,7 +7,10 @@ You can include one, two, of the three main ideas from your ideation process, de **Deliverable:** -- A comprehensive user flow on a board (digital or on paper) +- 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”. +- 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:** diff --git a/subjects/ux/going-on-holidays-with-friends/user-flow/audit/README.md b/subjects/ux/going-on-holidays-with-friends/user-flow/audit/README.md index 43f204b..5f65048 100644 --- a/subjects/ux/going-on-holidays-with-friends/user-flow/audit/README.md +++ b/subjects/ux/going-on-holidays-with-friends/user-flow/audit/README.md @@ -1,6 +1,12 @@ #### Audit -###### Is there a user flow (on paper or digital)? +###### 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? diff --git a/subjects/ux/lets-fight-harassment/broadcast-stategy/README.md b/subjects/ux/lets-fight-harassment/broadcast-stategy/README.md index f48983c..20969ce 100644 --- a/subjects/ux/lets-fight-harassment/broadcast-stategy/README.md +++ b/subjects/ux/lets-fight-harassment/broadcast-stategy/README.md @@ -15,6 +15,10 @@ Even though a proper survey requires at least 100 answers, for this exercise we - At least 2 different messages - A plan A, a plan B, a plan C - A document to express your main feedback after running your broadcast strategy: what worked best? have you encountered any difficulties? What were they? How did you overcome them? +- 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:** diff --git a/subjects/ux/lets-fight-harassment/broadcast-stategy/audit/README.md b/subjects/ux/lets-fight-harassment/broadcast-stategy/audit/README.md index c0770cc..4a0fe9a 100644 --- a/subjects/ux/lets-fight-harassment/broadcast-stategy/audit/README.md +++ b/subjects/ux/lets-fight-harassment/broadcast-stategy/audit/README.md @@ -1,7 +1,12 @@ #### Audit -###### Is there a PDF document? -###### Are the ideas structured? +###### 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? diff --git a/subjects/ux/lets-fight-harassment/competitive-analyss/README.md b/subjects/ux/lets-fight-harassment/competitive-analyss/README.md index 7921831..98b925e 100644 --- a/subjects/ux/lets-fight-harassment/competitive-analyss/README.md +++ b/subjects/ux/lets-fight-harassment/competitive-analyss/README.md @@ -22,9 +22,13 @@ Compare these 10 organizations' main actions, channels, values, according to the **Deliverables :** -- A PDF document of a competitive report with an introduction that explains your main conclusions -- A chart to show the competitive landscape, with 2 axes of your choice (digital, psychological, local, closeness to students, institutional, etc.) -- A table to compare the organizations on 5 to 10 criteria +- 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! + Resources: diff --git a/subjects/ux/lets-fight-harassment/competitive-analyss/audit/README.md b/subjects/ux/lets-fight-harassment/competitive-analyss/audit/README.md index 9088b38..4171d19 100644 --- a/subjects/ux/lets-fight-harassment/competitive-analyss/audit/README.md +++ b/subjects/ux/lets-fight-harassment/competitive-analyss/audit/README.md @@ -1,6 +1,11 @@ #### Audit -###### Is there a PDF document that includes the deliverables? +###### 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? diff --git a/subjects/ux/lets-fight-harassment/interviews/README.md b/subjects/ux/lets-fight-harassment/interviews/README.md index c69575e..648ecd6 100644 --- a/subjects/ux/lets-fight-harassment/interviews/README.md +++ b/subjects/ux/lets-fight-harassment/interviews/README.md @@ -12,6 +12,9 @@ After knowing more about trends and "What" people do thanks to surveys, the main - 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”. +- 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:** diff --git a/subjects/ux/lets-fight-harassment/interviews/audit/README.md b/subjects/ux/lets-fight-harassment/interviews/audit/README.md index 3d64e7c..6412f9d 100644 --- a/subjects/ux/lets-fight-harassment/interviews/audit/README.md +++ b/subjects/ux/lets-fight-harassment/interviews/audit/README.md @@ -1,5 +1,11 @@ #### Audit -###### Is there a PDF document wtih the interview guide? + +###### 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? \ No newline at end of file diff --git a/subjects/ux/lets-fight-harassment/personas/README.md b/subjects/ux/lets-fight-harassment/personas/README.md index 3207e58..0038eb7 100644 --- a/subjects/ux/lets-fight-harassment/personas/README.md +++ b/subjects/ux/lets-fight-harassment/personas/README.md @@ -11,6 +11,9 @@ Reminder: Your persona is fictional and should not have the exact name or pictur **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:** diff --git a/subjects/ux/lets-fight-harassment/personas/audit/README.md b/subjects/ux/lets-fight-harassment/personas/audit/README.md index 1388725..0f3e3d7 100644 --- a/subjects/ux/lets-fight-harassment/personas/audit/README.md +++ b/subjects/ux/lets-fight-harassment/personas/audit/README.md @@ -1,9 +1,12 @@ #### Audit -###### Is there a PDF document ? +###### 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)? \ No newline at end of file +###### Are the persona's behaviors included (hobbies, technology, whatever seems relevant)? diff --git a/subjects/ux/lets-fight-harassment/problem-statement/README.md b/subjects/ux/lets-fight-harassment/problem-statement/README.md index c71da0d..9e8b4ba 100644 --- a/subjects/ux/lets-fight-harassment/problem-statement/README.md +++ b/subjects/ux/lets-fight-harassment/problem-statement/README.md @@ -9,6 +9,9 @@ Then, define 3 KPIs (Key performance Indicators) that will help you measure the **Deliverables:** - 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:** diff --git a/subjects/ux/lets-fight-harassment/problem-statement/audit/README.md b/subjects/ux/lets-fight-harassment/problem-statement/audit/README.md index 9f5a83a..d65c759 100644 --- a/subjects/ux/lets-fight-harassment/problem-statement/audit/README.md +++ b/subjects/ux/lets-fight-harassment/problem-statement/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document ? +###### 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? diff --git a/subjects/ux/lets-fight-harassment/surveys/README.md b/subjects/ux/lets-fight-harassment/surveys/README.md index 9c9f821..e38cdb8 100644 --- a/subjects/ux/lets-fight-harassment/surveys/README.md +++ b/subjects/ux/lets-fight-harassment/surveys/README.md @@ -10,8 +10,12 @@ To be used in proper studies and get viable results, a form should gather at lea **Deliverables:** -- A PDF document including your objective(s) and your hypotheses -- A survey ready to be spread +- A PDF document including your objective(s) and your hypotheses, the questions, an introduction and a conclusion. +- In the document, add the link to a survey ready to be spread +- 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:** diff --git a/subjects/ux/lets-fight-harassment/surveys/audit/README.md b/subjects/ux/lets-fight-harassment/surveys/audit/README.md index ff61c5b..402a510 100644 --- a/subjects/ux/lets-fight-harassment/surveys/audit/README.md +++ b/subjects/ux/lets-fight-harassment/surveys/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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? @@ -8,4 +11,5 @@ ###### 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? \ No newline at end of file +###### Is there a conclusion with the next steps and a thank you message? +###### Is there a link to the survey ready to be spread? \ No newline at end of file diff --git a/subjects/ux/lets-fight-harassment/user-journey/README.md b/subjects/ux/lets-fight-harassment/user-journey/README.md index 67bb37d..2185c72 100644 --- a/subjects/ux/lets-fight-harassment/user-journey/README.md +++ b/subjects/ux/lets-fight-harassment/user-journey/README.md @@ -12,7 +12,11 @@ Then, highlight the main pain points that need to be solved. **Deliverable:** -- A PDF document with your persona's user journey +- A Figma document with your persona's user journey +- 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:** diff --git a/subjects/ux/lets-fight-harassment/user-journey/audit/README.md b/subjects/ux/lets-fight-harassment/user-journey/audit/README.md index 3cbd7b8..ec10eec 100644 --- a/subjects/ux/lets-fight-harassment/user-journey/audit/README.md +++ b/subjects/ux/lets-fight-harassment/user-journey/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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? diff --git a/subjects/ux/music-on/card-sorting/README.md b/subjects/ux/music-on/card-sorting/README.md index 7f99108..6ad9d4b 100644 --- a/subjects/ux/music-on/card-sorting/README.md +++ b/subjects/ux/music-on/card-sorting/README.md @@ -28,6 +28,9 @@ To do so: - A card sorting workshop script with the research goals (PDF document) - Pictures of the ongoing workshop - A document to show the new content organization (it can be a picture of the board with sticky notes or the digital 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”. +- 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:** diff --git a/subjects/ux/music-on/card-sorting/audit/README.md b/subjects/ux/music-on/card-sorting/audit/README.md index 68adc2f..884359a 100644 --- a/subjects/ux/music-on/card-sorting/audit/README.md +++ b/subjects/ux/music-on/card-sorting/audit/README.md @@ -1,7 +1,11 @@ #### Audit -###### Is there a PDF document ? -###### Is there a script including the research goals? +###### 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)? \ No newline at end of file diff --git a/subjects/ux/music-on/heuristics/README.md b/subjects/ux/music-on/heuristics/README.md index 18be798..424c7f4 100644 --- a/subjects/ux/music-on/heuristics/README.md +++ b/subjects/ux/music-on/heuristics/README.md @@ -19,6 +19,9 @@ Conduct a heuristic analysis on **one** of these websites: - A duplicated and completed chhecklist on a sheet document (Google Sheets, Airtable, Excel, etc.) - [Tool : Heuristic evaluation checklist](https://drive.google.com/file/d/10KbfbNZA1oVS1sXbjjXLPPmdZ6nqVkdc/view) +- 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! **Resources:** diff --git a/subjects/ux/music-on/heuristics/audit/README.md b/subjects/ux/music-on/heuristics/audit/README.md index 67eeb84..194e202 100644 --- a/subjects/ux/music-on/heuristics/audit/README.md +++ b/subjects/ux/music-on/heuristics/audit/README.md @@ -1,5 +1,8 @@ #### Audit -###### Is there a document? +###### 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? \ No newline at end of file diff --git a/subjects/ux/music-on/jtbd/README.md b/subjects/ux/music-on/jtbd/README.md index 06d55a9..1fde055 100644 --- a/subjects/ux/music-on/jtbd/README.md +++ b/subjects/ux/music-on/jtbd/README.md @@ -18,6 +18,9 @@ And remember: You are not your user! - A complete Jobs-to-Be-Done on a PDF document - "When ______, I want to _____ So I can _____" +- 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:** diff --git a/subjects/ux/music-on/jtbd/audit/README.md b/subjects/ux/music-on/jtbd/audit/README.md index bedb46c..b7414c9 100644 --- a/subjects/ux/music-on/jtbd/audit/README.md +++ b/subjects/ux/music-on/jtbd/audit/README.md @@ -1,5 +1,9 @@ #### 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? diff --git a/subjects/ux/music-on/run-5-tests/README.md b/subjects/ux/music-on/run-5-tests/README.md index 555062c..fcccaae 100644 --- a/subjects/ux/music-on/run-5-tests/README.md +++ b/subjects/ux/music-on/run-5-tests/README.md @@ -8,6 +8,9 @@ Run the test on 5 people! - Pictures of the ongoing test - A PDF document with the conclusions from each test and 3 major ideas to improve the prototype +- 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:** diff --git a/subjects/ux/music-on/run-5-tests/audit/README.md b/subjects/ux/music-on/run-5-tests/audit/README.md index 5d29f0e..2ba1b71 100644 --- a/subjects/ux/music-on/run-5-tests/audit/README.md +++ b/subjects/ux/music-on/run-5-tests/audit/README.md @@ -1,5 +1,11 @@ #### 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 ongoing tests? ###### Are there conclusions from each test? ###### Are there 3 ideas to include in the next version of the prototype? \ No newline at end of file diff --git a/subjects/ux/music-on/site-map/README.md b/subjects/ux/music-on/site-map/README.md index fdb3ef1..8a62c53 100644 --- a/subjects/ux/music-on/site-map/README.md +++ b/subjects/ux/music-on/site-map/README.md @@ -16,6 +16,9 @@ Stick to the website you have chosen in Ex.1 and design a site map. The site map **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:** diff --git a/subjects/ux/music-on/site-map/audit/README.md b/subjects/ux/music-on/site-map/audit/README.md index 69be94c..d459c44 100644 --- a/subjects/ux/music-on/site-map/audit/README.md +++ b/subjects/ux/music-on/site-map/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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? diff --git a/subjects/ux/music-on/test-protocol/README.md b/subjects/ux/music-on/test-protocol/README.md index fa801b2..fa5eba1 100644 --- a/subjects/ux/music-on/test-protocol/README.md +++ b/subjects/ux/music-on/test-protocol/README.md @@ -7,6 +7,9 @@ Prepare a protocol for usability testing. **Deliverable:** - 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 diff --git a/subjects/ux/music-on/test-protocol/audit/README.md b/subjects/ux/music-on/test-protocol/audit/README.md index a9fbdf5..b763a05 100644 --- a/subjects/ux/music-on/test-protocol/audit/README.md +++ b/subjects/ux/music-on/test-protocol/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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? diff --git a/subjects/ux/music-on/wireframes/README.md b/subjects/ux/music-on/wireframes/README.md index fd007d4..feaa38b 100644 --- a/subjects/ux/music-on/wireframes/README.md +++ b/subjects/ux/music-on/wireframes/README.md @@ -30,6 +30,9 @@ Vocabulary **Deliverables:** - Wireframes (6 to 12 screens) from the home page to the product page, 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:** diff --git a/subjects/ux/music-on/wireframes/audit/README.md b/subjects/ux/music-on/wireframes/audit/README.md index 4338a99..e08fdfc 100644 --- a/subjects/ux/music-on/wireframes/audit/README.md +++ b/subjects/ux/music-on/wireframes/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a Figma file? +###### 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? \ No newline at end of file diff --git a/subjects/ux/seamstress/define/README.md b/subjects/ux/seamstress/define/README.md index 2c6349d..af30f0b 100644 --- a/subjects/ux/seamstress/define/README.md +++ b/subjects/ux/seamstress/define/README.md @@ -9,6 +9,10 @@ Run at least one of the Define tools in the design process. - 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! + **Tips:** diff --git a/subjects/ux/seamstress/define/audit/README.md b/subjects/ux/seamstress/define/audit/README.md index b75589c..fa2f68f 100644 --- a/subjects/ux/seamstress/define/audit/README.md +++ b/subjects/ux/seamstress/define/audit/README.md @@ -1,5 +1,11 @@ #### 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 diff --git a/subjects/ux/seamstress/empathy/README.md b/subjects/ux/seamstress/empathy/README.md index c1a02d3..9033640 100644 --- a/subjects/ux/seamstress/empathy/README.md +++ b/subjects/ux/seamstress/empathy/README.md @@ -9,6 +9,9 @@ Run at least one of the Empathy tools in the design process. - 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! **Tips:** diff --git a/subjects/ux/seamstress/empathy/audit/README.md b/subjects/ux/seamstress/empathy/audit/README.md index 8b65072..64f0a2b 100644 --- a/subjects/ux/seamstress/empathy/audit/README.md +++ b/subjects/ux/seamstress/empathy/audit/README.md @@ -1,5 +1,11 @@ #### 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 diff --git a/subjects/ux/seamstress/ideation/README.md b/subjects/ux/seamstress/ideation/README.md index b746d1b..e2a661e 100644 --- a/subjects/ux/seamstress/ideation/README.md +++ b/subjects/ux/seamstress/ideation/README.md @@ -9,6 +9,9 @@ Run at least one of the Ideation techniques in the design process. - 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:** diff --git a/subjects/ux/seamstress/ideation/audit/README.md b/subjects/ux/seamstress/ideation/audit/README.md index 3007473..c8a44d4 100644 --- a/subjects/ux/seamstress/ideation/audit/README.md +++ b/subjects/ux/seamstress/ideation/audit/README.md @@ -1,5 +1,11 @@ #### 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? diff --git a/subjects/ux/seamstress/problem-statement/README.md b/subjects/ux/seamstress/problem-statement/README.md index 52587f6..c339a3b 100644 --- a/subjects/ux/seamstress/problem-statement/README.md +++ b/subjects/ux/seamstress/problem-statement/README.md @@ -10,6 +10,9 @@ Based on your research (Empathy & Define), define a problem statement to narrow - One problem statement - 1 to 3 KPIs - Key learnings from this phase +- 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)) diff --git a/subjects/ux/seamstress/problem-statement/audit/README.md b/subjects/ux/seamstress/problem-statement/audit/README.md index 325cd1f..9a0f1c3 100644 --- a/subjects/ux/seamstress/problem-statement/audit/README.md +++ b/subjects/ux/seamstress/problem-statement/audit/README.md @@ -1,6 +1,9 @@ #### Audit -###### Is there a PDF document? +###### 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? \ No newline at end of file diff --git a/subjects/ux/seamstress/prototype/README.md b/subjects/ux/seamstress/prototype/README.md index 11e5eeb..0645c96 100644 --- a/subjects/ux/seamstress/prototype/README.md +++ b/subjects/ux/seamstress/prototype/README.md @@ -6,13 +6,16 @@ Make a prototype including the chosen solution. **Deliverables:** -- A paper prototype (low-fi) +- 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! **Tips:** diff --git a/subjects/ux/seamstress/prototype/audit/README.md b/subjects/ux/seamstress/prototype/audit/README.md index 414439b..82c76b7 100644 --- a/subjects/ux/seamstress/prototype/audit/README.md +++ b/subjects/ux/seamstress/prototype/audit/README.md @@ -1,5 +1,11 @@ #### 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? diff --git a/subjects/ux/seamstress/test/README.md b/subjects/ux/seamstress/test/README.md index a7151c2..b7d4323 100644 --- a/subjects/ux/seamstress/test/README.md +++ b/subjects/ux/seamstress/test/README.md @@ -9,4 +9,7 @@ Prepare a testing protocol and run it! - A testing protocol script - Photos from the tests - Key learnings from the tests (5 tests are required) -- Key learnings from this phase \ No newline at end of file +- 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! \ No newline at end of file diff --git a/subjects/ux/seamstress/test/audit/README.md b/subjects/ux/seamstress/test/audit/README.md index acdbdbc..48aa712 100644 --- a/subjects/ux/seamstress/test/audit/README.md +++ b/subjects/ux/seamstress/test/audit/README.md @@ -1,6 +1,11 @@ #### Audit -###### Is there a PDF docuemnt with the script? +###### 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? diff --git a/subjects/ux/seamstress/ux-strategy/README.md b/subjects/ux/seamstress/ux-strategy/README.md index bcbc51d..4ded2d3 100644 --- a/subjects/ux/seamstress/ux-strategy/README.md +++ b/subjects/ux/seamstress/ux-strategy/README.md @@ -26,6 +26,11 @@ Select at least one tool for each phase, name it, and take into account the amou **Deliverables:** - A time frame, on PDF or on Figma, of the project, including the working days ahead, each phase of the process, the main tools you plan to use for each phase and the time you plan to spend for each tool. +- Upload the PDF or Figma 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! + + **Resource:** diff --git a/subjects/ux/seamstress/ux-strategy/audit/README.md b/subjects/ux/seamstress/ux-strategy/audit/README.md index 9fabedc..e2fce4c 100644 --- a/subjects/ux/seamstress/ux-strategy/audit/README.md +++ b/subjects/ux/seamstress/ux-strategy/audit/README.md @@ -1,5 +1,9 @@ #### 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 diff --git a/subjects/ux/sunday-night-movie/iteration/README.md b/subjects/ux/sunday-night-movie/iteration/README.md index 11737e2..0f2a065 100644 --- a/subjects/ux/sunday-night-movie/iteration/README.md +++ b/subjects/ux/sunday-night-movie/iteration/README.md @@ -15,6 +15,9 @@ Write a report with the conclusion you made out of this iteration loop. - 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”. +- 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:** diff --git a/subjects/ux/sunday-night-movie/iteration/audit/README.md b/subjects/ux/sunday-night-movie/iteration/audit/README.md index aff7db3..e337ae4 100644 --- a/subjects/ux/sunday-night-movie/iteration/audit/README.md +++ b/subjects/ux/sunday-night-movie/iteration/audit/README.md @@ -1,5 +1,11 @@ #### 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 new test? ###### Is there a PDF document with the report? ###### Are the V1 and V2 versions different? diff --git a/subjects/ux/sunday-night-movie/test-feature-1/README.md b/subjects/ux/sunday-night-movie/test-feature-1/README.md index f98ad9c..016899b 100644 --- a/subjects/ux/sunday-night-movie/test-feature-1/README.md +++ b/subjects/ux/sunday-night-movie/test-feature-1/README.md @@ -11,6 +11,9 @@ Focus on the 1st journey. Prepare a test protocol with your research goals (what - 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:** diff --git a/subjects/ux/sunday-night-movie/test-feature-1/audit/README.md b/subjects/ux/sunday-night-movie/test-feature-1/audit/README.md index 266ed1f..8798ab6 100644 --- a/subjects/ux/sunday-night-movie/test-feature-1/audit/README.md +++ b/subjects/ux/sunday-night-movie/test-feature-1/audit/README.md @@ -1,5 +1,11 @@ #### 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? diff --git a/subjects/ux/sunday-night-movie/test-feature-2/README.md b/subjects/ux/sunday-night-movie/test-feature-2/README.md index df1598b..863cd05 100644 --- a/subjects/ux/sunday-night-movie/test-feature-2/README.md +++ b/subjects/ux/sunday-night-movie/test-feature-2/README.md @@ -11,6 +11,9 @@ Focus on the 2nd journey. Prepare a test protocol with your research goals (what - 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:** diff --git a/subjects/ux/sunday-night-movie/test-feature-2/audit/README.md b/subjects/ux/sunday-night-movie/test-feature-2/audit/README.md index 266ed1f..8798ab6 100644 --- a/subjects/ux/sunday-night-movie/test-feature-2/audit/README.md +++ b/subjects/ux/sunday-night-movie/test-feature-2/audit/README.md @@ -1,5 +1,11 @@ #### 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? diff --git a/subjects/ux/sunday-night-movie/test-feature-3/README.md b/subjects/ux/sunday-night-movie/test-feature-3/README.md index f20217b..768db35 100644 --- a/subjects/ux/sunday-night-movie/test-feature-3/README.md +++ b/subjects/ux/sunday-night-movie/test-feature-3/README.md @@ -11,6 +11,9 @@ Focus on the 3rd journey. Prepare a test protocol with your research goals (what - 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**: diff --git a/subjects/ux/sunday-night-movie/test-feature-3/audit/README.md b/subjects/ux/sunday-night-movie/test-feature-3/audit/README.md index 266ed1f..8798ab6 100644 --- a/subjects/ux/sunday-night-movie/test-feature-3/audit/README.md +++ b/subjects/ux/sunday-night-movie/test-feature-3/audit/README.md @@ -1,5 +1,11 @@ #### 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? diff --git a/subjects/ux/sunday-night-movie/user-flow/README.md b/subjects/ux/sunday-night-movie/user-flow/README.md index 664649d..801faf7 100644 --- a/subjects/ux/sunday-night-movie/user-flow/README.md +++ b/subjects/ux/sunday-night-movie/user-flow/README.md @@ -19,7 +19,10 @@ Features: **Deliverables:** -- 3 user flows on a board (digital or physical) +- 3 user flows on a board (digital or pictures of a paper board) +- 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:** diff --git a/subjects/ux/sunday-night-movie/user-flow/audit/README.md b/subjects/ux/sunday-night-movie/user-flow/audit/README.md index f7bc5d5..9e3cb3e 100644 --- a/subjects/ux/sunday-night-movie/user-flow/audit/README.md +++ b/subjects/ux/sunday-night-movie/user-flow/audit/README.md @@ -1,5 +1,12 @@ #### 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 diff --git a/subjects/ux/sunday-night-movie/wireframes-animation/README.md b/subjects/ux/sunday-night-movie/wireframes-animation/README.md index d4e2d46..6e6ae0d 100644 --- a/subjects/ux/sunday-night-movie/wireframes-animation/README.md +++ b/subjects/ux/sunday-night-movie/wireframes-animation/README.md @@ -11,6 +11,10 @@ This exercise is to be made individually. **Deliverables:** - 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! + **Resources:** diff --git a/subjects/ux/sunday-night-movie/wireframes-animation/audit/README.md b/subjects/ux/sunday-night-movie/wireframes-animation/audit/README.md index 32d5f97..7496f9f 100644 --- a/subjects/ux/sunday-night-movie/wireframes-animation/audit/README.md +++ b/subjects/ux/sunday-night-movie/wireframes-animation/audit/README.md @@ -1,5 +1,9 @@ #### 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? diff --git a/subjects/ux/sunday-night-movie/wireframes/README.md b/subjects/ux/sunday-night-movie/wireframes/README.md index 92135fd..89e018c 100644 --- a/subjects/ux/sunday-night-movie/wireframes/README.md +++ b/subjects/ux/sunday-night-movie/wireframes/README.md @@ -7,6 +7,9 @@ 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:** diff --git a/subjects/ux/sunday-night-movie/wireframes/audit/README.md b/subjects/ux/sunday-night-movie/wireframes/audit/README.md index 5509f0e..91bee82 100644 --- a/subjects/ux/sunday-night-movie/wireframes/audit/README.md +++ b/subjects/ux/sunday-night-movie/wireframes/audit/README.md @@ -1,16 +1,25 @@ #### Audit -###### Is there a Figma file? + +###### 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? \ No newline at end of file diff --git a/subjects/ux/the-olympics/animation/README.md b/subjects/ux/the-olympics/animation/README.md index dd28af4..ee03156 100644 --- a/subjects/ux/the-olympics/animation/README.md +++ b/subjects/ux/the-olympics/animation/README.md @@ -11,6 +11,9 @@ 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:** diff --git a/subjects/ux/the-olympics/animation/audit/README.md b/subjects/ux/the-olympics/animation/audit/README.md index 9f78a36..65d33a0 100644 --- a/subjects/ux/the-olympics/animation/audit/README.md +++ b/subjects/ux/the-olympics/animation/audit/README.md @@ -1,5 +1,8 @@ #### 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? diff --git a/subjects/ux/the-olympics/ideation-a/README.md b/subjects/ux/the-olympics/ideation-a/README.md index e46ac53..5cb832f 100644 --- a/subjects/ux/the-olympics/ideation-a/README.md +++ b/subjects/ux/the-olympics/ideation-a/README.md @@ -23,6 +23,9 @@ A is leader, B is time-keeper and C focuses on logistics - A PDF document with the ideation workshop script - Pictures of the ongoing workshop - A PDF document that represents the main concept out of the workshop +- 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:** diff --git a/subjects/ux/the-olympics/ideation-a/audit/README.md b/subjects/ux/the-olympics/ideation-a/audit/README.md index c8df8ee..4d8a7dc 100644 --- a/subjects/ux/the-olympics/ideation-a/audit/README.md +++ b/subjects/ux/the-olympics/ideation-a/audit/README.md @@ -1,6 +1,12 @@ #### Audit -###### Is there is a script for the ideation workshop ? +###### 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 is a script for the ideation workshop? ###### Is there the main objective? ###### Is there an ice breaker? ###### Are there the main steps of the ideation process? diff --git a/subjects/ux/the-olympics/ideation-b/README.md b/subjects/ux/the-olympics/ideation-b/README.md index b180b59..83feec1 100644 --- a/subjects/ux/the-olympics/ideation-b/README.md +++ b/subjects/ux/the-olympics/ideation-b/README.md @@ -17,6 +17,9 @@ Pay attention not to use the same ideation technique as in Ex 1! - A PDF document with the ideation workshop script - Pictures of the ongoing workshop - A PDF document that represents the main concept out of the workshop +- 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:** diff --git a/subjects/ux/the-olympics/ideation-b/audit/README.md b/subjects/ux/the-olympics/ideation-b/audit/README.md index c8df8ee..4d8a7dc 100644 --- a/subjects/ux/the-olympics/ideation-b/audit/README.md +++ b/subjects/ux/the-olympics/ideation-b/audit/README.md @@ -1,6 +1,12 @@ #### Audit -###### Is there is a script for the ideation workshop ? +###### 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 is a script for the ideation workshop? ###### Is there the main objective? ###### Is there an ice breaker? ###### Are there the main steps of the ideation process? diff --git a/subjects/ux/the-olympics/ideation-c/README.md b/subjects/ux/the-olympics/ideation-c/README.md index c7433e8..1f599b8 100644 --- a/subjects/ux/the-olympics/ideation-c/README.md +++ b/subjects/ux/the-olympics/ideation-c/README.md @@ -17,6 +17,9 @@ Pay attention not to use the same ideation technique as in ex 2! - A PDF document with the ideation workshop script - Pictures of the ongoing workshop - A PDF document that represents the main concept out of the workshop +- 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:** diff --git a/subjects/ux/the-olympics/ideation-c/audit/README.md b/subjects/ux/the-olympics/ideation-c/audit/README.md index c8df8ee..4d8a7dc 100644 --- a/subjects/ux/the-olympics/ideation-c/audit/README.md +++ b/subjects/ux/the-olympics/ideation-c/audit/README.md @@ -1,6 +1,12 @@ #### Audit -###### Is there is a script for the ideation workshop ? +###### 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 is a script for the ideation workshop? ###### Is there the main objective? ###### Is there an ice breaker? ###### Are there the main steps of the ideation process? diff --git a/subjects/ux/the-olympics/prototyping/README.md b/subjects/ux/the-olympics/prototyping/README.md index a17298f..1764868 100644 --- a/subjects/ux/the-olympics/prototyping/README.md +++ b/subjects/ux/the-olympics/prototyping/README.md @@ -18,6 +18,10 @@ Then, draw your mid-fidelity screens on Figma with simple shapes, in black and w - Picture of a paper prototype - A Figma file with the wireframes (mid-fi) +- 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:** diff --git a/subjects/ux/the-olympics/prototyping/audit/README.md b/subjects/ux/the-olympics/prototyping/audit/README.md index 88be839..d2b1f2b 100644 --- a/subjects/ux/the-olympics/prototyping/audit/README.md +++ b/subjects/ux/the-olympics/prototyping/audit/README.md @@ -1,6 +1,12 @@ #### Audit -###### Is there a paper prototype? +###### 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 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? diff --git a/subjects/ux/the-olympics/test/README.md b/subjects/ux/the-olympics/test/README.md index 317132f..cce3eee 100644 --- a/subjects/ux/the-olympics/test/README.md +++ b/subjects/ux/the-olympics/test/README.md @@ -11,6 +11,10 @@ This exercise is to be made individually. - A PDF document with the usability test script - Pictures of the ongoing tests - A PDF docuemnt with a report on what you learnt and a list of the 5 main iterations that you'd like to do on the next 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”. +- 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:** diff --git a/subjects/ux/the-olympics/test/audit/README.md b/subjects/ux/the-olympics/test/audit/README.md index 911c139..447401f 100644 --- a/subjects/ux/the-olympics/test/audit/README.md +++ b/subjects/ux/the-olympics/test/audit/README.md @@ -1,5 +1,11 @@ #### 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 the test script? ###### Does the test script include a greeting and onboarding paragraph? ###### Does the test script include a scenario the user has to complete? diff --git a/subjects/ux/the-olympics/user-flow/README.md b/subjects/ux/the-olympics/user-flow/README.md index a73998f..6624183 100644 --- a/subjects/ux/the-olympics/user-flow/README.md +++ b/subjects/ux/the-olympics/user-flow/README.md @@ -8,7 +8,11 @@ This exercise is to be made individually. **Deliverables:** -- A comprehensive user flow on a board (digital or physical) +- A comprehensive user flow on a board (digital or pictures of a physical one) +- 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:** diff --git a/subjects/ux/the-olympics/user-flow/audit/README.md b/subjects/ux/the-olympics/user-flow/audit/README.md index 70e63ce..800c548 100644 --- a/subjects/ux/the-olympics/user-flow/audit/README.md +++ b/subjects/ux/the-olympics/user-flow/audit/README.md @@ -1,6 +1,12 @@ #### Audit -###### Is there a document (digital or on paper) with the user flow? +###### 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 document (digital or pictures of a paper one) with the user flow? ###### Does the user have a specific goal? ###### Is there a starting point and and ending point? ###### Is the ending point the goal of the user?