Run usability tests on drupal admin
Run at least three sessions to test the usability of drupal's customization and configuration admin user-interfaces.
To do this you will need 3 or more volunteers who will evaluate drupal. It is important that everyone understands that Drupal is being tested, not the evaluator (your volunteers). The evaluator can not pass or fail.
Ask each of the volunteers to do some basic configuring and customizing on a newly installed Drupal site. Give them a scenario that will inspire them to do it realistically. e.g. "Your soccer club needs a web site with about pages and news articles or a blog". You might like to give them more detailed instructions and/or specific tasks. See the UMN formal usability testing plan for ideas on how to do this. Your tasks and instructions need not be as detailed or complex, but they should give the evaluator a clear goal and help inspire creative things like colors, setting the site name and slogan.
To familiarize yourself with the tasks and usability tests, it is useful to do you're own test and report, before running the tests with evaluators. This will help you gain confidence with finding issues and taking notes on them.
While observing new users, take note of:
* what the evaluator wants to do first.
* where the evaluator gets lost or confused.
* where the evaluator spends their time in the first 30 minutes of the session
* where the evaluator spends their time in the first few seconds of each new UI / page
* when and where they search for help
* where they search for help
Write a report that summarizes your findings. We're looking for a level of
detail and format similar to Factory Joe's Usability report on drupal 6 beta 1. See also the reports from GHOP tasks #8 and #7.
There are two completed GHOP tasks that are usability tests like this one; #7 (d.o), and #8 (d.o). Those tasks focussed on drupal installation. This task focuses on site configuration and customization.
Before planning your usability tests read about how to do usability testing:
* http://www.uxmatters.com/MT/archives/000183.php
* http://openusability.org/
* http://keycontent.org/tiki-index.php?page=Usability+Tools
* http://factoryjoe.pbwiki.com/FeedbackForDrupal6
This task is complete when the report has been submitted by the student, and reviewed and approved by the mentor or other appropriate drupal community member.
Bevan is the owner / mentor of this task.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | GHOP usability test.txt | 4.31 KB | Bevan |
| #7 | GHOP usability test.html_.txt | 4.39 KB | Bevan |
Comments
Comment #1
Bevan commentedOnce this task is confirmed I'd like to make another one of the same format that is based on lower-level tasks, like browsing, commenting, registering, changing password or user name, node creation and editing.
Comment #2
aclight commentedIn the "ask each of the volunteers..." paragraph, can you emphasize that all customizations should be through the UI, and not via template or css files, just to make sure this is absolutely clear.
Please add a "Deliverables:" section. You have the deliverables themselves, but it's easiest for us if you have a separate section that we can glance at. Also, please specify that the report should be in a standards compliant and widely available format (I prefer .pdf, possibly in addition to something that's editable) and that the report should be uploaded to this issue (which will be the issue you create once the task is approved).
Other than these things, this looks good to me.
Sorry I didn't review this earlier--I must have archived the original message in my gmail view and therefore it wasn't on my list of things to look at.
Comment #3
ximo commentedI can only say that this looks good to me.
Comment #4
Bevan commentedTake 2. If there are no other recommendations I'll GHOPify it and create one or two more task ideas of the same format for different user roles.
========================
Run usability tests on drupal admin
Run at least three sessions to test the usability of drupal's customization and configuration admin user-interfaces.
To do this you will need 3 or more volunteers who will evaluate drupal. It is important that everyone understands that Drupal is being tested, not the evaluator (your volunteers). The evaluator can not pass or fail.
Ask each of the volunteers to do some basic configuring and customizing on a newly installed Drupal site. Give them a scenario that will inspire them to do it realistically. e.g. "Your soccer club needs a web site with about pages and news articles or a blog".
You might like to give them more detailed instructions and/or specific tasks. See the UMN formal usability testing plan for ideas on how to do this. Your tasks and instructions need not be as detailed or complex, but they should give the evaluator a clear goal and help inspire creative things like colors, setting the site name and slogan.
To familiarize yourself with the tasks and usability tests, it is useful to do you're own test and report, before running the tests with evaluators. This will help you gain confidence with finding issues and taking notes on them. The evaluator must be able to do all the tasks through drupal's UI and not need to write any code or change files.
While observing new users, take note of:
Write a report that summarizes your findings. We're looking for a level of
detail and format similar to Factory Joe's Usability report on drupal 6 beta 1. See also the reports from GHOP tasks #8 and #7.
There are two completed GHOP tasks that are usability tests like this one; #7 (d.o), and #8 (d.o). Those tasks focussed on drupal installation. This task focuses on site configuration and customization.
Before planning your usability tests read about how to do usability testing:
Deliverables: This task is complete when the report has been submitted to by the student, and reviewed and approved by the mentor or other appropriate drupal community member. The report should be made available in a widely available format like plain text, html or PDF.
You can include screenshots for bonus points. These could be annotated using flickr's annotate tool. (Tag them with drupalui if using flickr.)
Bevan is the owner / mentor of this task.
Comment #5
aclight commentedLooks good to me. Go ahead and create an official task for this.
Comment #6
dman commentedOK. +1 I like the idea
The most actionable improvements (sorta mentioned in the notes) is trying to capture what the user expected. What option/action they needed next, where they went looking for it.
Only then can we start to guess what would have been easier. :-)
Comment #7
Bevan commentedThanks for your comments Dan. I've attached the two text files with a new paragraph including your suggestion and some tips on debriefing. I created the google issue: http://code.google.com/p/google-highly-open-participation-drupal/issues/... and a d.o issue in the user experience project: http://drupal.org/node/211072
Comment #8
dman commentedNice write-up.
It makes usability almost understandable. Refreshingly light on jargon!
Comment #9
Bevan commentedhe he!! Thanks! :)
Comment #10
aclight commentedClosing this and changing title back so we don't get confused and think this is the official issue.
The real task is at http://drupal.org/node/211072 and http://code.google.com/p/google-highly-open-participation-drupal/issues/...