1 min read Usability testing

Report the cause of issues

Report the cause of issues

When reporting usability issues to your stakeholders:

DON'T: Users are not sure how export works.

DO: Users are not sure if the export button exports the file details as a file, or it exports the file itself. The user expects the latter but the layout suggests the former to him.

The first example tells that there is a usability issue and nothing else. The Designer wouldn't know how to fix it. The second example tells the reason why users experience it as an issue. That's something a Designer can go and fix. This is actionable. The other is useless.

Published by:

Zsombor Varnagy-Toth

You might also like...

Mar
24
Populate prototype with realistic content - part 2, dummy content

Populate prototype with realistic content - part 2, dummy content

Populating UIs with realistic data can be a pain in the ass. But it's worth it because we don't distract
1 min read
Mar
17
Populate prototype with realistic content - part 1, cultural references

Populate prototype with realistic content - part 1, cultural references

When users work through a task, the more realistic the prototype is, the more realistic the users’ behavior will be,
1 min read
Mar
07
Rescreen participants to contextualize results

Rescreen participants to contextualize results

Why does this matter? When kicking off usability sessions we tend to start with a couple of "get to know
2 min read
Feb
27
Don't assume the reason for struggle

Don't assume the reason for struggle

When usability testing it sometimes feels very obvious why the user misunderstood something. But the human mind is a mystery
1 min read
Feb
17
Train participants to think aloud

Train participants to think aloud

When usability testing I instruct my participants to think out loud. However, despite their best effort, they would still forget
1 min read

Member discussion