Difference between revisions of "UsabilityTesting"

From Inkscape Wiki
Jump to: navigation, search
(cat)
 
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
This is a stub.  Please help. 
+
= Usability Testing =
 
+
 
+
Usability Testing
+
 
+
 
There are various ways to test usability some of which overlap with straighforward bug finding, accessibility testing and internationalisation work.   
 
There are various ways to test usability some of which overlap with straighforward bug finding, accessibility testing and internationalisation work.   
Usability inevitably involves certain tradeoffs but for Inkscape is is important to make basic tasks easy and difficult tasks possible.  Inkscape is a drawing tool designed for the mass market.  Artists should be considered the primary audience.  Techincal drawing is a secondary audience and there are many things we will want to make possible but Inkscape is not intended for Computer Aided Design (CAD) and although we should be able to make many of these things possible it would be counter productive to overwhelm our target audience and this complexity must be balanced.   
+
Usability inevitably involves certain tradeoffs but for Inkscape it is important to make basic tasks easy and difficult tasks possible.  Inkscape is a drawing tool designed for the mass market.  Artists should be considered the primary audience.  Technical drawing is a secondary audience and there are many things we will want to make possible but ''Inkscape'' is not intended for Computer Aided Design (CAD) and although we should be able to make many of these things possible it would be counter productive to overwhelm our target audience and this complexity must be balanced.   
 
The first most important lesson is if Inkscape is difficult to understand it is *not your fault* and if there is any way we can improve things we are interested in exploring them.   
 
The first most important lesson is if Inkscape is difficult to understand it is *not your fault* and if there is any way we can improve things we are interested in exploring them.   
 
However we must also look at the big picture, we must avoid microoptimisations (scripting and automation tools will inevitably be needed at some point).   
 
However we must also look at the big picture, we must avoid microoptimisations (scripting and automation tools will inevitably be needed at some point).   
  
On the testing mailing list AlanHorkan outlines some task based Usability tests which any user could try out for themselves.   
+
On the testing mailing list [[AlanHorkan]] outlines some task based Usability tests which any user could try out for themselves.   
 
The tasks are generic and their general purpose is to see if the basic behaviour of the tools is straight forward enough for relatively simple tasks.   
 
The tasks are generic and their general purpose is to see if the basic behaviour of the tools is straight forward enough for relatively simple tasks.   
http://sourceforge.net/mailarchive/message.php?msg_id=12667354
 
  
Another form of usability testing is Competitive Analysis. There are valuable lessons we can learn from OtherProjects  particularly commercial products such as Adobe Illustrator and Macromedia Freehand which currently dominate the graphic design market.   
+
[http://sourceforge.net/mailarchive/message.php?msg_id=12667354 E-mail Archive]
 +
 
 +
Another form of usability testing is Competitive Analysis. There are valuable lessons we can learn from [[OtherProjects]] particularly commercial products such as ''Adobe Illustrator'' and ''Macromedia Freehand'' which currently dominate the graphic design market.   
  
  
 
There are various forms of usability testing, this is only one.
 
There are various forms of usability testing, this is only one.
 
   
 
   
What I have attempted to do here is outline a task you might ask an
+
What I have attempted to do here is outline a task you might ask an
oridinary user to do.  I hope to put this somewhere in the Wiki where it
+
ordinary user to do.  I hope to put this somewhere in the Wiki where it
can be refineded and others can try it out for themselves.  Testers
+
can be refined and others can try it out for themselves.  Testers
already familiar with Inkscape could also do the test but intimate
+
already familiar with Inkscape could also do the test but intimate
knowledge of how Inkscape works will obviously skew the results so a high
+
knowledge of how Inkscape works will obviously skew the results so a high
level of self awareness is needed.  Talking aloud while doing the test and
+
level of self awareness is needed.  Talking aloud while doing the test and
attempting to vocalise what you are thinking can be very helpful (but a
+
attempting to vocalise what you are thinking can be very helpful (but a
little awkward and embarassing sometimes).  The introduction is supposed
+
little awkward and embarassing sometimes).  The introduction is supposed
to help put users in the right frame of mind.  The task is intended to be
+
to help put users in the right frame of mind.  The task is intended to be
as simple and unambigious as possible and should be abstract enough to
+
as simple and unambiguous as possible and should be abstract enough to
apply to any vector graphics program.
+
apply to any vector graphics program.
 
   
 
   
=====
 
 
   
 
   
Inkscape Usability Testing
+
== Inkscape Usability Testing ==
 
   
 
   
The Inkscape developers understand Inkscape is not perfect.
+
The Inkscape developers understand Inkscape is not perfect.
If a task seems difficult or awkward it is not your fault.
+
If a task seems difficult or awkward it is not your fault.
If it is not immediately obvious what you are meant to do then perhaps we
+
If it is not immediately obvious what you are meant to do then perhaps we
can improve it.  Please make a note of anything you find difficult to
+
can improve it.  Please make a note of anything you find difficult to
understand.  Find any problems or inefficiencies and try to describe them
+
understand.  Find any problems or inefficiencies and try to describe them
as best you can.  Do not worry too much about suggesting ways to fix
+
as best you can.  Do not worry too much about suggesting ways to fix
problems, it is up to the developer to step back and look at the bigger
+
problems, it is up to the developer to step back and look at the bigger
picture and see how things might best be improved.
+
picture and see how things might best be improved.
Even if you are able to figure it out ask yourself if could it be better?
+
Even if you are able to figure it out ask yourself if could it be better?
 +
 
 +
These are the kinds of questions you need to ask to help improve the
 +
usability of Inkscape.
 +
 
 +
:Is here the place to ask? Or is there somewhere else?
 +
:I've been using Inkscape to make [http://images4.wikia.nocookie.net/borderlands/images/c/ce/LegendStyles.svg Maps of the Borderlands]. An issue that comes up while I'm tracing a path: Sometimes I accidentally finish a path. Sometimes that happens because of my MX Revolution mouse registering a double-click, sometimes because my coffee buzzed fingers spaz, and sometimes because I realize after the fact that I want to continue on that path. Not sure about it, but it might also be happening when some badly behaved tray application steals the focus.
 +
:This is different from splitting a segment into two segments with an in-between point. What I want to do is select an endpoint and continue adding points to that path. Also, along the same lines, some way to back up while placing a path. Maybe control-clicking last nodes backs up.[[User:AngleWyrm|AngleWyrm]] 21:18, 4 December 2009 (UTC)
 
   
 
   
These are the kinds of questions you need to ask to help improve the
+
 
usability of Inkscape.
+
=== Task 1 ===
 +
 
 +
 
 +
Draw a picture of a House.
 
   
 
   
 +
Use at least one Ellipse
 +
Include a linear gradient in your drawing.
 +
Inlcude the text "Home Sweet Home"
 +
 +
Save your drawing with the name ''house-01.svg''
 
   
 
   
  *** Task 1 ***
+
[Notes: might break this task up into stages, suggesting different
 +
modifications at each stage to encourage testers to discover particular
 +
tools and save different versions of the files. Perhaps also include
 +
saving the final version of the file so that it can be put on a web page]
 
   
 
   
Draw a picture of a House.
+
=== Task 2 ===
 
   
 
   
Use at least one Ellipse
+
Draw a picture of a face.
Include a linear gradient in your drawing.
+
 
Inlcude the text "Home Sweet Home"
+
== Suggestions for improvement ==
+
 
Save your drawing with the name house-01.svg
+
(none)
+
 
[Notes: might break this task up into stages, suggesting different
+
== References ==
modifications at each stage to encourage testers to discover particular
+
 
tools and save different versions of the files. Perhaps also include
+
[http://developer.gnome.org/projects/gup/hig/ Gnome Human Interface Guidelines]
saving the final version of the file so that it can be put on a web page]
+
 
+
[http://developer.gnome.org/projects/gup/ui-review/checklist.html Gnome User Interface Review Checklist]
*** Task 2 ***
+
 
+
[[Category:Needs Work]]
Draw a picture of a face.
+

Latest revision as of 17:21, 1 March 2012

Usability Testing

There are various ways to test usability some of which overlap with straighforward bug finding, accessibility testing and internationalisation work. Usability inevitably involves certain tradeoffs but for Inkscape it is important to make basic tasks easy and difficult tasks possible. Inkscape is a drawing tool designed for the mass market. Artists should be considered the primary audience. Technical drawing is a secondary audience and there are many things we will want to make possible but Inkscape is not intended for Computer Aided Design (CAD) and although we should be able to make many of these things possible it would be counter productive to overwhelm our target audience and this complexity must be balanced. The first most important lesson is if Inkscape is difficult to understand it is *not your fault* and if there is any way we can improve things we are interested in exploring them. However we must also look at the big picture, we must avoid microoptimisations (scripting and automation tools will inevitably be needed at some point).

On the testing mailing list AlanHorkan outlines some task based Usability tests which any user could try out for themselves. The tasks are generic and their general purpose is to see if the basic behaviour of the tools is straight forward enough for relatively simple tasks.

E-mail Archive

Another form of usability testing is Competitive Analysis. There are valuable lessons we can learn from OtherProjects particularly commercial products such as Adobe Illustrator and Macromedia Freehand which currently dominate the graphic design market.


There are various forms of usability testing, this is only one.

What I have attempted to do here is outline a task you might ask an ordinary user to do. I hope to put this somewhere in the Wiki where it can be refined and others can try it out for themselves. Testers already familiar with Inkscape could also do the test but intimate knowledge of how Inkscape works will obviously skew the results so a high level of self awareness is needed. Talking aloud while doing the test and attempting to vocalise what you are thinking can be very helpful (but a little awkward and embarassing sometimes). The introduction is supposed to help put users in the right frame of mind. The task is intended to be as simple and unambiguous as possible and should be abstract enough to apply to any vector graphics program.


Inkscape Usability Testing

The Inkscape developers understand Inkscape is not perfect. If a task seems difficult or awkward it is not your fault. If it is not immediately obvious what you are meant to do then perhaps we can improve it. Please make a note of anything you find difficult to understand. Find any problems or inefficiencies and try to describe them as best you can. Do not worry too much about suggesting ways to fix problems, it is up to the developer to step back and look at the bigger picture and see how things might best be improved. Even if you are able to figure it out ask yourself if could it be better?

These are the kinds of questions you need to ask to help improve the usability of Inkscape.

Is here the place to ask? Or is there somewhere else?
I've been using Inkscape to make Maps of the Borderlands. An issue that comes up while I'm tracing a path: Sometimes I accidentally finish a path. Sometimes that happens because of my MX Revolution mouse registering a double-click, sometimes because my coffee buzzed fingers spaz, and sometimes because I realize after the fact that I want to continue on that path. Not sure about it, but it might also be happening when some badly behaved tray application steals the focus.
This is different from splitting a segment into two segments with an in-between point. What I want to do is select an endpoint and continue adding points to that path. Also, along the same lines, some way to back up while placing a path. Maybe control-clicking last nodes backs up.AngleWyrm 21:18, 4 December 2009 (UTC)


Task 1

Draw a picture of a House.

Use at least one Ellipse Include a linear gradient in your drawing. Inlcude the text "Home Sweet Home"

Save your drawing with the name house-01.svg

[Notes: might break this task up into stages, suggesting different modifications at each stage to encourage testers to discover particular tools and save different versions of the files. Perhaps also include saving the final version of the file so that it can be put on a web page]

Task 2

Draw a picture of a face.

Suggestions for improvement

(none)

References

Gnome Human Interface Guidelines

Gnome User Interface Review Checklist