Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create etiquette-principles-for-moderating-a-usability-testing.md #183

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Create etiquette-principles-for-moderating-a-usability-testing.md #183

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
35 changes: 35 additions & 0 deletions _examples/etiquette-principles-for-moderating-a-usability-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
title: Etiquette Principles for Moderating a Usability Testing
author: Nicoletta Bruno
overview:
link: [https://www.hedron.it/articolo/etichetta-comportamento-moderazione-usability-testing]
principles:
- principle: Be gentle
summary: |
Welcome the participants, introduce yourself, ask for confirmation of their name and thank them for their participation.
- principle: Break the ice
summary: |
Explain the testing methodology, specify that you’re not going to test the participants but you’re conducting a research to evaluate the product. Start with a short interview to understand your interlocutors habits and their familiarity with the product or service being tested.
- principle: Avoid unexpected events and distractions
summary: |
Check the prototype and the test manual with a smaller sample of users before starting the test campaign. Ask to silence notifications before starting the testing session.
- principle: Be honest
summary: |
Inform the tester about the recording and request consent to proceed.
- principle: Avoid bias
summary: |
Do not test your own product, let other researchers do it. Do not recruit people who are too experienced in testing. Do not recruit people who already had experience with the same product.
- principle: Encourage criticism
summary: |
Declare that you are not the designer of the product. Require maximum openness and sincerity from the user. Do not assume a position of superiority over the interlocutor and don’t blame him for being inexperienced. Don't crowd the session with unnecessary observers.
- principle: Do not influence the tester
summary: |
Be as invisible as possible, do not suggest actions. Don't judge the tester preferences and opinions. Avoid telling your own experience or opinion, unless needed to put the tester at ease and make him better understand the task to be carried out.
- principle: Don't require an excessive effort
summary: |
Propose one task at a time. Do not exceed the timing and the number of use cases.
- principle: Learn more
summary: |
Observe first, then ask why. You must distinguish usability problems from user bias.
tags: [universal, people]
---