Data Tracking

With the UTS we will be tracking data as clicks, data entered and time spend. At the moment UTS its aim is to only track written data feedback such as answers to questions asked before a study, before a task, after a task and after a study. However ideally we want to track more in order to help developers more easily track where users are struggling and how important it is to fix.

Data tracking

• Logging pages (Done!)
• Logging form clicks
• Logging time (spent between forms, and overall)
• Logging path(s) taken to complete steps
• Data entered in forms

We hope to in-depth on tracking data, so that we can easily track what happened between page 1, form 1 and page 1, form 2. Did the user decide to go back to try to complete the task in a different way? Skipped the form, or did it take him very long to comprehend the meaning of the form (very subjective) and did he succeed understanding it(ie failed task)? Or did he chose the wrong selection in order to complete the task?

You can get some convincing data out of this, there is a certain risk (http://www.useit.com/alertbox/20040301.html) however we can identify user behaviour and slightly filter out expectations. We will focus on presenting the data, that allows for the "right" interpretation. So, not displaying averages but a graph showing, most of the people being centred around 45 seconds for that specific task and a few being at the 145 seconds line.

So the UTS will show this and leave the interpretation to the UTE. He can easily conclude that 90% is around the 45 second mark and only 5/6% around the 145 second line. The idea here is that the UTS cant put out statistical significant data(foolish to pursue), it can however show user behaviour.

Convincing data
Between page 1, form 1 and page 1, form 2 the amount of participants that failed is 65%.
Before people got to form 2, a 75% of the participants looked in a weird not related section, saying which one(s).

At the moment its not sure, how much of this is possible within the timeframe of the UTS. So therefore this issue que :)