Group
Subject
Your subject is "".
Teammates
Tutor
Your tutor is .
Your appointment is on .
Part 3 Rules Reminder
Click here to review rules
Before the meetings:
-
Know the subject of your appointment.
You must have read the course modules and prepared the questions you wish to discuss with the tutor. -
Know how to locate the progress of your team.
Take the time to formulate the difficulties encountered and the positive points. Don't wait several weeks before reporting problems. -
Organize a meeting.
Except in exceptional cases, find yourself in the same place. A suitable place (quiet) with a good internet connection, for the smooth running of your interview.
During meetings:
-
Your presence is mandatory at all meetings.
Any absence must be justified to your tutor before the meeting in the Slack channel of your group. -
Your camera must be on.
The tutor is there to accompany you synchronously, not to talk to an avatar. -
Behave like a professional.
Adopt an employee posture in a company in all circumstances: holding in front of the camera, appropriate language, listening skills, correct clothing. -
Lead this project in good spirit.
Your participation in the meetings is mandatory and is part of the course. You are not a cruise passenger. Remember to react to the comments made to your group but also to interact with the other groups present.
When the tutor gives the speech, everyone must speak! -
Take advantage of your appointments collectively.
You must divide up the roles: designate as many "scribes" as necessary for each meeting. It is mandatory to write a group interview report and post it in the group channel at the end of the meeting.
Outside of meetings:
-
Collaborate with the tools at your disposal:
-
Slack:
The group communication must be done on Slack in your group channel.
→ If you discuss elsewhere, your tutor cannot accompany you, it is a waste of time, resources and especially advice.
→ Make reports and post them on Slack to get feedback from your tutor.
→ Individual maluses will weight your final score according to your participation.Any student who is not on Slack at the beginning of Part 3 will be graded 0 for Part 3.
Any student who does not participate in the Slack channel of their group will be graded 0 for Part 3.
-
Zoom:
You can use Zoom in group at any time to chat in video and share your screens: type/zoom
in your Slack group channel, a button will appear in the channel to join a Zoom room.When launching a Zoom room for the first time, you will have to validate your account by clicking on the "Authorize Zoom" link, then connect with SSO ("Sign in with SSO").
→ In the field "Your company domain", enter "em-lyon".
→ Finally, authenticate on the emlyon portal.
-
-
Be there for others.
Reactivity towards your tutor and your collaborators on Slack is essential. Put yourself in the shoes of a professional who leads a project as a team. -
Document
You must constantly document what you are doing. Keep as much record as possible of the exchanges and work done so that you can analyze what worked in the project and what didn't.
Your weekly goals
- Test previous week prototypes with two users
- Iterate based on feedback
- Pick the most promising project
Why testing a prototype?
- Testing a prototype with end-users is essential, it will allow you to discover real issues.
- Finding issues is the only way to improve a proposal or make a smart iteration of a prototype.
- Bad feedback on a prototype is good news! This means that there is a real pain point. This is valuable in order to iterate and design an interesting proposal. On the other hand, a test that gives only good feedback is suspicious.
- Perfect ideas often lead to poor projects! Phase two is an iterative time based on the proposals you made during phase one.
This is a team activity!
Although the work is collective, the evaluation will be individual and mainly based on your involvement in the project and in the group's dynamics
Brief
This week, you will have to test and iterate your prototypes from the previous week.
By presenting your project to your end-users, you will collect crucial feedback, advice to improve your prototype and leave behind preconceived ideas.
Be rigorous during your user tests, focus on user experience (UX) and how users will interact with AI in your project.
- If they have a question, write them down, it probably means that something in your proposal needs to be simplified
- If they struggle to do something, you probably need to improve your UX
- Write down the way they talk about your project and try to reuse their own words from now on
WRITE. DOWN. EVERYTHING.
User feedback is a treasure, keep them and refer to them during a moment of doubts
Assignments
Keep in mind that the goal of this phase is to improve your prototypes using end-users feedback.
Watch the video below then follow the instructions to test your prototypes:
1. Test your two prototypes
- Find representative users of your proposals and ask them for a meeting.
Start the meeting by following the interview guide provided on Notion. Introduce yourself, explain the goals of the test, and take time to learn more about your tester (How well do they know the subject? What alternative are they currently using? etc.) - Test each prototype with at least 2 users. Set up impartial tests! User’s actions should not be influenced in ways that lead to a biased result
- Check your usage scenario, does it match the experience of your tester?
- Write accurately the learning & insights you have gained from the tests
- List the actions and decisions you'll have to make for the next iteration
Observe users' reactions and report your discussions, especially their questions and things that you didn't expect.
You have to test each one of your two proposals with at least 2 end-users: so you will have to do four tests in total, make sure to plan your test sessions carefully!
Never give advice or instructions for use! You are trying to see the spontaneous use of your prototype. Just observe and be empathic.
Document each test in the User Research page on Notion
Resources
To learn more about user testing:
- How to conduct user interviews by Patrick Thornton
- User Test by Jake Knapp with the Google Design Sprint
- Strategies for Qualitative Interviews from Harvard
2. Improve your two proposals
- Examine tests results with your team to determine the improvements required for your two proposals and their materializations. What features need to be improved / removed / added for each prototype?
- Make an iteration for each one of your two prototypes.
An iteration is a new version of your prototype that integrates observations made during user tests to improve usage.
Check if your iteration still answers your ethical guidelines!
Create a copy of your work (Figma, etc.) before making changes to keep a backup of where you started!
Describe your iterations to your Notion.
4. Argue your final choice
- Examine the results with your team to determine the improvements needed and evaluate the desirability & feasibility of your different proposals. Which proposal do you think is the most interesting to develop during next week and why?
- Prepare an argumentation on your Notion explaining your choice, but keep in mind that your tutor will be the one to decide which project you will be working on next week.
Explain your Final choice argumentation on Notion
Evaluation criteria
- For each of the two projects (7 pts each = 14 pts)
-
Test process rigor (4 pts)
You picked your testers in coherence with your project and your reports for these tests are qualitative.
Your Notion page for this phase is correctly filled and makes sense. -
Iteration (3 pts)
You have correctly iterated your project regarding the feedback you obtained.
Your prototype is well-built. - Final choice (4 pts)
- Communication (2 pts)
Your argumentation is clear and logical.
You were able to identify the key features of your final project according to users' feedback.
You communicated professionally and efficiently with your group members and your tutor both on Slack and during the meeting.