Labs/Ubiquity/Usability/Usability Testing/UI Triangulation: Difference between revisions

← Older edit

Labs/Ubiquity/Usability/Usability Testing/UI Triangulation (view source)

Revision as of 21:57, 3 February 2009

54 bytes added , 3 February 2009

m

Tweaks to triangulation text per Zac's ping

Andyed

61

edits

@@ Line 1: / Line 1: @@
-UI Triangulation is the categorization of usability issues by their severity as a problem and the frequency at which they occur.
+Triangulation helps categorize usability issues by their severity as a problem and the frequency at which they occur by looking for the problem across multiple datasources.
 It also raises the visibility of problems by making sure that it is reported in all the appropriate areas, cross referencing usability studies, bug trackers, and customer facing issue trackers.  This helps to ensure that they receive earlier and higher priority in the overall development cycle at least equal to programming bugs.  It also increases the value of each of these development tools beyond their specific, isolated purposes.
@@ Line 5: / Line 5: @@
 == UI Triangulation ==
-UI Triangulation is generally done using data collection points such as Trac tickets, Get Satisfaction tickets, traditional usability testing, mailing group messages, server statistics and cross referencing them.
+Triangulation involves comparing observations across data collection points such as Trac tickets, Get Satisfaction tickets, traditional usability testing, mailing group messages, server statistics and cross referencing them.
-Generally analytics (server stats, volume of Trac tickets, volume of GSFN complaints, % of usability testers, etc) are used to quantify the frequency of the problem.
+Generally analytics (server stats, volume of Trac tickets, volume of GSFN complaints, % of usability testers, etc) are used to quantify the frequency of the problem. The raw data can also be used for severity (exit points on web sites for example) but the content must be examined as well to determine how detrimental the issue is.
-The raw data can also be used for severity (exit points on web sites for example) but the content must be examined as well to determine how detrimental the issue is.  Traditional usability testing allows for very focused, clear understanding of the problem and for root analysis of deeper issues.  Bug reports allow for not only identification of the problem but for how users expect the issue to be resolved.
+Traditional usability testing allows for very focused, clear understanding of problems and for root analysis of deeper issues.  Bug reports allow for not only identification of the problem but for how users expect the issue to be resolved.
 The cross referencing is the tying together disparate system in either an automated manner (DB sync) semi-automated manner (forwarding new ticket notification to bug tracker) or manually (managers log bugs as they receive them into multiple systems).