My favorites | Sign in
Project Logo
          
New issue | Search
for
| Advanced search | Search tips
Issue 8: Improve initial user experience
4 people starred this issue and may be notified of changes. Back to list
Status:  Closed
Owner:  dries.buytaert
Closed:  Dec 2007
Research
Usability
ClaimedBy-StallonSelvan
DrupalIssue-197221
AdminChecked


Sign in to add a comment
 
Reported by webchickenator, Nov 18, 2007
Watch at least 3 new Drupal users (like friends or family) install and
configure Drupal, and submit a report that identifies problem areas, with
recommendations on how they can be improved. This work will directly help
Drupal to become a more usable system and make it accessible to a wider
range of people.

Before beginning, spend a couple of hours reading about how to do usability
testing. When observing new users, things to watch for include:

    * what does he/she want to do first
    * where does the user get lost or confused
    * where does he/she spend his/her time in the first 30 minutes
    * when and where does he/she have to Google/search for more information

Write a report that summarizes your findings. We're looking for a level of
detail and format similar to http://factoryjoe.pbwiki.com/FeedbackForDrupal6.

Resources:

    * http://openusability.org/
    * http://keycontent.org/tiki-index.php?page=Usability+Tools
    * http://factoryjoe.pbwiki.com/FeedbackForDrupal6


Estimated time:
  5 days

Comment 1 by webchickenator, Nov 18, 2007
(No comment was entered for this change.)
Labels: Usability
Comment 2 by b.rudge, Nov 28, 2007
I don't think the scope of the usability tests shouldn't include creating a database,
database user or giving that user privileges -- that is not within the scope of the
drupal installer.  So remember to provide and test the database details before
commencing each usability test that includes the drupal installer.

Alternatively, if the person participating in the test doesn't know what a database
is, or understand that drupal has to connect to a database, it's probably a good idea
to skip the installation process and ask them to do more common tasks, like
configuring drupal, or simply creating content, taxonomy terms and other more common
tasks.

I think it's okay to exchange one 'full' (install, configure, add content) usability
test for two or three 'common tasks' usability tests.

Remember that a usability does NOT test the user, it tests USABILITY.  It's important
that everyone (especially the volunteer participating) understand that drupal is
being tested, and not the user.  The user will NOT get a mark, be approved nor pass
nor fail.  Drupal get's 'marked' in this test!  :)

On that note, don't be afraid to get you're grandma to be a tester.  The only
prerequisite for testers should be that they use the internet at least fortnightly. 
It's also important that the tester be comfortable and relaxed, so it's probably best
to do the testing on their computer in their office or home.

Now I'm covering scope of the above-linked articles...  Effective usability tests are
not as easy as they seem.  It might also be useful to do you're own report like
Factory Joe did, before running tests with volunteers.  This will help you gain
confidence with finding and reporting findings (results).

Here's another great article on how to get the most out of usability tests
http://www.uxmatters.com/MT/archives/000183.php
Comment 3 by dries.buytaert, Nov 29, 2007
Feel free to exclude the actual install procedure from the tests.  However, it is
probably a good idea to start from an empty site.

I would also recommend using Drupal 6, not Drupal 5.
Comment 4 by StallonSelvan, Nov 29, 2007
I claim this task.
Comment 5 by webchickenator, Nov 29, 2007
Awesome! Really excited about this one. :)
Labels: ClaimedBy-StallonSelvan
Comment 6 by addi.berry, Nov 29, 2007
Just marking this claimed.
Status: Claimed
Comment 7 by b.rudge, Dec 02, 2007
StallonSelvan, see http://groups.drupal.org/node/7352#comment-21974
Comment 9 by StallonSelvan, Dec 04, 2007
2 tests done, 1 remaining...
Comment 10 by webchickenator, Dec 04, 2007
Great. Thanks for the status update! When your results are complete, could you please
post them to http://drupal.org/node/197221 ?
Comment 11 by StallonSelvan, Dec 06, 2007
Sure... i have almost finished the report, on completion i will upload it at the
above site.
Comment 12 by webchickenator, Dec 06, 2007
A polite poke. ;) This task is a bit overdue.
Status: ActionNeeded
Comment 13 by webchickenator, Dec 07, 2007
(No comment was entered for this change.)
Labels: DueDate-20071207
Comment 14 by webchickenator, Dec 07, 2007
(No comment was entered for this change.)
Labels: -DueDate-20071207 DueDate-2007-12-07
Comment 15 by StallonSelvan, Dec 08, 2007
Sorry for the delay, i will be uploading my report today or at the latest tomorrow.
Apologizing for the delay again.
Comment 16 by addi.berry, Dec 08, 2007
Extending deadline to tomorrow.
Labels: -DueDate-2007-12-07 DueDate-2007-12-09
Comment 17 by addi.berry, Dec 09, 2007
Please post your work to the drupal issue at http://drupal.org/node/197221 as well.
Labels: DrupalIssue-197221
Comment 18 by StallonSelvan, Dec 09, 2007
Report is done, just finalizing it and posting in another couple of hours.
Comment 19 by StallonSelvan, Dec 09, 2007
http://swizzy.frih.net/projects/drupal-usability-test-report

Hope its alright, and that it helps.
Comment 20 by addi.berry, Dec 09, 2007
marking for review
Status: NeedsReview
Comment 21 by StallonSelvan, Dec 10, 2007
Can somebody review this soon?
Comment 22 by webchickenator, Dec 10, 2007
I just pinged the devel list with this and 4 other issues which are pending review >
24 hours. I'm hopeful that help is on the way!
Comment 23 by eindgebruiker, Dec 11, 2007
This is a great test report. Not only did you describe the problems encountered, you
also gave some very helpful ideas. Excellent!

Gaele
Comment 24 by aclight, Dec 11, 2007
To make this a little easier to track, I created a separate issue for this task at
http://drupal.org/node/199885

StallonSelvan:  Could you please post a comment at the above link with a link to your
report (or, even better, you could copy and paste your report into a comment in that
issue).  Then, set the status of the issue as "patch (code needs review)".  That
should help you get more comments on your work.
Labels: -DrupalIssue-197221 DrupalIssue-199885
Comment 25 by StallonSelvan, Dec 11, 2007
Will the task will be closed now? 

Can I claim another task if this is still labeled NeedsReview ?
Comment 26 by aclight, Dec 11, 2007
Whoops, there was already a d.o issue for this.  That's at http://drupal.org/node/197221
Labels: -DrupalIssue-199885 DrupalIssue-197221
Comment 27 by aclight, Dec 11, 2007
This looks good.  Thanks for the hard work.  I'm marking this as closed so that you
can claim another task.  Keep up the good work.
Status: Closed
Labels: -DueDate-2007-12-09
Comment 28 by aclight, Jan 21, 2008
In order to get credit for this task, please upload your final work to this issue.
See the wiki page at
http://code.google.com/p/google-highly-open-participation-drupal/wiki/HowToGetCreditForYourTask
for more information.
Comment 29 by StallonSelvan, Jan 21, 2008
"Issue attachment storage quota exceeded." :(
Comment 30 by StallonSelvan, Jan 21, 2008
http://swizzy.frih.net/file_download/36/drupal.zip - contains usability test report,
and a html file.

(uploaded the work here, because of above error!)
Comment 31 by webchickenator, Jan 21, 2008
Unfortunately, it has to be here. We put in a support request was put into Google.
Please try again tomorrow, if you could!
Comment 32 by aclight, Jan 22, 2008
The quota problem should be fixed now, so please try to upload again.  Thanks!
Comment 33 by StallonSelvan, Jan 22, 2008
Cheers. File is uploaded :)
drupal.zip
3.5 KB Download
Comment 34 by aclight, Jan 22, 2008
thanks, you're all set now.
Labels: AdminChecked
Sign in to add a comment

Hosted by Google Code