Create guide-to-observational-usability-testing.md#59
Create guide-to-observational-usability-testing.md#59SirLouen merged 3 commits intoWordPress:trunkfrom
Conversation
Add Guide to Observational Usability Testing (Issue WordPress#43)
nikunj8866
left a comment
nikunj8866
left a comment
There was a problem hiding this comment.
Please review the whole document some commas are being replaced with dashes, bold formatting is missing, and links are not included.
|
|
||
| This is a short guide to help anyone who would like to run a usability test. No prior experience is assumed, so if you are new to usability testing, you may find the tips and tricks section at the end of this post useful. Happy testing! | ||
|
|
||
| --- |
There was a problem hiding this comment.
Remove this horizontal line; it's not needed
|
|
||
| When running an observational user test, the most important thing to remember is that… **the test is not really a test!** Setting the scene to make your participant feel comfortable to provide open and honest feedback is the key role of the moderator. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Remove this horizontal line; it's not needed
| 5. **Reset the environment:** | ||
| After each participant finishes, refresh (reset) the two browser windows to ensure that each participant starts the test from the same baseline point. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Remove this horizontal line; it's not needed
|
|
||
| > “… this is not a test, there are no right or wrong answers. We are just really interested to hear your thoughts on …” | ||
|
|
||
| --- |
There was a problem hiding this comment.
Remove this horizontal line; it's not needed
|
|
||
| This tip is a little counter-intuitive. The real value of usability testing is that it can give us insight into the areas of a product’s design that can be improved. Product improvements often originate at the source of friction between the technology and the user. As a moderator, you are doing a great job if you can find the sources of friction — and not necessarily if your participant successfully completes a given task. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Remove this horizontal line; it's not needed
|
|
||
| Signaling that your participant is doing well can be done by using phrases such as: | ||
|
|
||
| - “Right, yes…” |
There was a problem hiding this comment.
change content format to > “Right, yes…”
| Signaling that your participant is doing well can be done by using phrases such as: | ||
|
|
||
| - “Right, yes…” | ||
| - “OK, I see…” |
There was a problem hiding this comment.
change content format to > “OK, I see…”
|
|
||
| - “Right, yes…” | ||
| - “OK, I see…” | ||
| - “Yes…” |
There was a problem hiding this comment.
change content format to > “Yes…”
|
|
||
| These small phrases will put the participant at ease, and shift their focus from trying to get the answers “right” to simply completing the task. | ||
|
|
||
| If your participant gets stuck — perhaps on something that is not related to the things you are testing for, or something that is still a work in progress and not the focus of the test — you will need to guide them gently back to the main task. You can do this by using a variation of this: |
There was a problem hiding this comment.
Please replace — with the comma like origin post content.
|
|
||
| ### Look for Points of Friction, Not Success | ||
|
|
||
| This tip is a little counter-intuitive. The real value of usability testing is that it can give us insight into the areas of a product’s design that can be improved. Product improvements often originate at the source of friction between the technology and the user. As a moderator, you are doing a great job if you can find the sources of friction — and not necessarily if your participant successfully completes a given task. |
There was a problem hiding this comment.
As a moderator, you are doing a great job if you can find the sources of friction
Make the above text bold.
|
Hi @nikunj8866, I have just updated the PR. Please check it. Thank you. |
|
Hi @SirLouen please review this PR. |
3 participants
Mirror: guide-to-observational-usability-testing.md (Issue #43)