The Cone Trees network The UX Bookmark UX Quotes UX Jobs in Singapore Nice one yeah!

The Usability Testing Process (diagram)

The usability testing process

Chinese translation of the diagram and article (by Ryana). Russian translation of the diagram and article (by Dmitry Satin).

Download
Usability Testing Process Poster (A4 PDF) (2265 downloads)

Send me a pic: Did you put it up at work? Is it looking good? Take a pic and mail it to me or upload the pic and send me a link. I’d love to know where you’ve put it up and how it looks. You can mail me at hello at conetrees dot com

A usability test consists of the following steps:

1- Usability test planning
2.1- Participant Recruitment
2.2 Scenario & Task creation
3- Execute the usability test/ conduct usability test sessions
4- Data Analysis
5- Reporting
6- Usability test recommendation incorporation checkpoint

I will follow up with another post to explain the steps in detail, but for now, here is some detail on step 6. Step 6 is not mentioned in most generic usability testing processes, but I want to stress upon it since it is plays a good role in optimizing the usability test process.

After you report the usability test findings and recommendations, stakeholders will agree to incorporate a certain number of recommendations. After the period for incorporating usability test recommendations has passed, you should hold a checkpoint meeting for the following purpose:

  • To see how many of those suggestions agreed upon have actually been incorporated. There is no point of conducting usability test after test if recommendations (that everyone agrees will improve the usability of the product tested) are not incorporated. You don’t want to keep conducting usability tests where you come out with recommendations, stakeholders agree on incorporating some, and then everybody forgets about it. And in the next test, you come out with many of them same old ones— this is simply not a very optimal way of doing things. This checkpoint thus helps you mitigate what I think is a concern worth addressing.
  • Using data, conclude whether those suggestions did or did not improved the usability of your product (or the portion/ section you tested upon), recommendation by recommendation. In case they did, you may want to find out if there is any further scope of improvement. And in case they did not, you may want to understand what wrong assumptions were made while giving particular recommendations and learn from them so you can avoid them in similar cases in the future.
Creative Commons License
The Usability Testing Process Diagram by Abhay Rautela is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 2.5 India License.

The only derivative work that I allow of this diagram is translation. Once you are done, let me know and I’ll link back to it.

  • http://www.uxstudy.com Ryana

    Hi Abhay,

    Thank you for creating such great diagram! And I love it so much that I have translated it into Chinese:
    http://www.uxstudy.com/?p=264

    Ryana

  • http://www.conetrees.com Abhay (Cone Trees)

    Glad you like it Ryana. Hmmm, I did say no derivatives in the license but I see you’ve kept the credits intact. So, nice job with the translation. Thanks for doing it. I’ve linked to it in the post.

  • http://usability-bulletin.ru Dmitry Satin

    Abhay, good diargam and thoughts about checkpoint meeting!

    We translated your post to Russian
    http://usability-bulletin.ru/2010/03/the-usability-testing-process-diagram/

    (with your kind permission, of course)

    Thank you!

  • http://www.conetrees.com Abhay (Cone Trees)

    Glad you like it Dmitry. Nice work with the translation. Thanks for doing it. I’ve linked to it as well.

  • melinda

    Any chance you’d update the text on 2.2 to say, “Recruit Participants”? (It would be consistent with the rest of the copy.)

    Nice, simple diagram!

  • http://www.conetrees.com Abhay (Cone Trees)

    Good job with catching the typo. Fixed.

  • http://www.xicroninfotech.co.cc vipin

    Great stuff, thanks for sharing this with us.

    http://soft-engineering.blogspot.com

  • http://chrisrouman.com Chris Rouman

    Nice looking diagram; simple and to the point. It’s a good addition to documentation in general but also if you are in a position where selling user testing is an issue… and sometimes it is for me.

  • http://www.rosettatranslation.com alice

    Nice post.Hoping this could be translated on Swedish translation as well.

  • http://www.conetrees.com ConeTrees

    Thanks for your comment Chris, and I’m glad you can use it.

  • http://www.conetrees.com ConeTrees

    @alice: Go for it, let me know when you do it and I’ll link out to it.