Erika Hall

take into account how core the related task is to your application

take into account how core the related task is to your application

Once you’ve conducted the tests, and rated the issues, sort them into three tiers. Each represents the combination of severity and frequency

Tier 1: high-impact problems that often prevent a user from completing a task. If you don’t resolve these you have a high risk to the success of your product.
Tier 2: either moderate problems with low frequency or low problems with moderate frequency.
Tier 3: low-impact problems that affect a small number of users. There is a low risk to not resolving these

Start with Tier 1 issues. Identify potential fixes with the lowest level of technical effort

Implement these fixes, then test again.

Watching actual users struggle with the system is more convincing than reading a report, and offers all the agitation of a suspense film

So if you’re starting to see frequent repeated usability issues, try to schedule sessions when it’s convenient for important people to observe

Why doesn’t he see the button? It’s right there!)

Verbatim quotes and video clips of failure presented in conjunction with a report can also be effective