Interpreting Tests Results of Usability Testing

Let’s assume I arranged an usability test for a new project and my team came out with ideas how to improve the assignment. What to do now? According to a book “Don’t make me think” by Steve Krug, I should review the results right away.

The team has to analyze the problems and decide how to fix them. The biggest question in this point is – should the team work on changes or absolutely redesign the whole system? Before I make any drastic decision, it is a good idea to implement as quickly as possible the least changes which could fix the problem, then test the project again. To do so, my team has to focus on precise points. The comment “The colors of navigation are not matching with rest of the page” is much more useful than simple observation “Navigation sucks.” No general complains are excepted! A precise explanation of problems and valuable suggestions allow me make quick and accurate changes to the project, so I can very fast see if we are on the right track with a current design. However, in most cases any “not bad” design can be fixed, and it takes less time than a complete redesign. Typical problems are: wrong arrangement of elements on the page, not correct names chosen to describe categories in a navigation, some elements on the page are too much or not enough visible, a wrong color palette.