Comments on: Crowdsourced Usability Testing Rnd 1 – Investigating Information Architecture

By: Rapport stage

Rapport stage — Thu, 18 Jun 2009 17:22:22 +0000

[...] Crowd-sourced Usability Testing: help us get the D7UX tested all over the world and get some usability testing experience under your belt – the first testing ’session’ is happening right now! [...]

By: Flimm

Flimm — Mon, 13 Apr 2009 17:33:44 +0000

What about non-English speakers? Are you interested in interviewing them?

By: Sutharsan

Sutharsan — Wed, 08 Apr 2009 07:10:52 +0000

Are we testing the very top line (content … help) only or also the second (add … dashboard)? In my first two test I did test the second line. I certainly did not harm, and the response to Find content and Dashboard was interesting.

By: yoroy

yoroy — Tue, 07 Apr 2009 22:58:38 +0000

Dutch version of this prototype and script is here: http://www.yoroy.com/2009/drupal-7-ux-usability-test-1 and cross posted there: http://drupal.nl/node/2016

By: Drupal 7 User Experience Project » Blog Archive » Current Activities - What you can do NOW!

Tue, 07 Apr 2009 11:31:47 +0000

By: Leisa Reichelt

Leisa Reichelt — Tue, 07 Apr 2009 08:25:52 +0000

re: the script order and whether you do the ‘tasks’ or the ‘what ifs’ first… I don’t really mind and I don’t think it makes a huge difference either way at this stage.

The point of this round of research is to understand how the navigation items are working (or not) whether people can make sense of what would be beneath them and where they would accomplish different sets of tasks. The reason I put the script in this order is because I’m actually more interested in the ‘What If’ questions that the tasks for the moment, so I’m more interested in people trying to interpret them than in seeing whether they can complete the tasks.

Certainly, if the prototype and project was more evolved I would agree 100% that the tasks should come first…

Since David left this comment I’ve actually run two more interviews switching between the two script structures and I didn’t find a huge difference in the way the interview played out or the findings… so, feel free to experiment a little if you like.

Just make sure you’re getting a good sense of people’s expectations and how they’re trying to understand what certain terms on the navigation mean and represent (and perhaps, if they are existing Drupal users) how they are trying to map this navigation back to their knowledge of how Drupal works.

thanks again for your interest and feedback!

By: Leisa Reichelt

Leisa Reichelt — Tue, 07 Apr 2009 08:21:22 +0000

@Alina, yes, for this round we are only testing the header which you can find in the PDF file I’ve linked to. Just a simple exercise to get us started and to iron out any bumps in the process. As we move further through the project the prototypes will get a lot more complicated and move from paper/pdf to interactive/HTML.

let me know if you have any questions

By: Alina

Alina — Tue, 07 Apr 2009 07:34:28 +0000

I don’t know if I’m missing something or not as I’m new in this initiative, but the testing is done only with this header in pdf?

Are there any other materials in this first round?

Thanks!

By: David

David — Mon, 06 Apr 2009 13:57:53 +0000

Please do not ask participants “what if” questions before you do the tasks, as you will obviously influence the participants performance.

E.g. if you point at an “Add new staff biography” link, and then ask the participant “What do you think this does”, when you ask the user to do Task 1. – “You need to add a new staff biography to your website”, they will immediately know where to find the answer, which would not be their natural behaviour.