Data analysis and interpretation Quantitative and qualitative l

Data analysis and interpretation

Quantitative and qualitative l l l Quantitative data – expressed as numbers Qualitative data – difficult to measure sensibly as numbers, e. g. count number of words to measure dissatisfaction Quantitative analysis – numerical methods to ascertain size, magnitude, amount Qualitative analysis – expresses the nature of elements and is represented as themes, patterns, stories Be careful how you manipulate data and numbers!

Descriptive Statistics l For all variables, get a feel for results: – – – Total scores, times, ratings, etc. Minimum, maximum Mean, median, ranges, etc. e. g. “Twenty participants completed both sessions (10 males, 10 females; mean age 22. 4, range 18 -37 years). ” v e. g. “The median time to complete the task in the mouse-input group was 34. 5 s (min=19. 2, max=305 s). ” v

Simple quantitative analysis l Averages – – – l l Mean: add up values and divide by number of data points Median: middle value of data when ranked Mode: figure that appears most often in the data Percentages versus numbers Graphical representations give overview of data

Subgroup Stats l Look at descriptive stats (means, medians, ranges, etc. ) for any subgroups – – e. g. “The mean error rate for the mouse-input group was 3. 4%. The mean error rate for the keyboard group was 5. 6%. ” e. g. “The median completion time (in seconds) for the three groups were: novices: 4. 4, moderate users: 4. 6, and experts: 2. 6. ”

Plot the Data l Look for the trends graphically

Other Presentation Methods Scatter plot Box plot low Middle 50% Age high Mean 0 20 Time in secs.

Visualizing log data Interaction profiles of players in online game Log of web page activity

Simple qualitative analysis l Recurring patterns or themes – l Categorizing data – l Emergent from data Categorization scheme may be emergent or pre-specified Looking for critical incidents – Helps to focus in on key events

Presenting the findings l Only make claims that your data can support l The best way to present your findings depends on the audience, the purpose, and the data gathering and analysis undertaken l Graphical representations may be appropriate for presentation l Other techniques are: – Using stories, e. g. to create scenarios based on the data – Summarizing the findings

Interviews l Raw data: – l Initial processing – l – – Group answers to same question (small # of questions and people) Label interesting phrases or words Put labels on post-its or in software and group labels Quantitative processing – – l Transcribe audio, or expand upon notes Qualitative processing – l Audio or video recordings, interviewer notes Gather quantitative responses such as age, etc. Categorize and count responses (5 liked, 3 disliked, etc. ) Presentation – – Summarize responses, tell stories and patterns Use descriptive quotes

Questionnaire l Raw data: – l Quantitative processing – – l Calculate descriptive stats (means, percentages, etc. ) for each question Can break into subgroups or use statistics to look for relationships between items (does age correlate to stronger preferences? ) Qualitative processing – l Tables of questions and numbers or text answers Group answers to same question Presentation – – Present tables & charts of means, percentages, etc. Explain overall meaning of all the responses

Observation l Raw data: – l Initial processing: – l – Record metrics such as errors, times, clicks, etc. Produce descriptive stats and charts of those metrics Qualitative processing – l Transcribe audio, expand notes or take more based on video, synchronize logs with recordings Quantitative processing – l Audio or video recording, log files, notes Note places where problems occurred, interesting behaviors, common behaviors Presentation – – – Descriptions of common or interesting problems Videos demonstrating issues, or descriptive quotes Charts describing quantitative data

Sample Think-aloud categorization 1. Interface problems 1. 2. 3. 4. 5. 6. 7. Verbalizations show evidence of dissatisfaction about an aspect of the interface. Verbalizations show evidence of confusion/uncertainty about an aspect of the interface. Verbalizations show evidence of confusion/surprise at the outcome of an action. Verbalizations show evidence that they are having problems achieving a goal. Verbalizations show evidence that the user has made an error. The participant I unable to recover from error without external help from the experimenter. The participant makes a suggestion for redesign of the interface. See pg 380 for more complete example

Experimental Results l How does one know if an experiment’s results mean anything or confirm any beliefs? l Example: 40 people participated, 28 preferred interface 1, 12 preferred interface 2 What do you conclude? l

Goal of analysis l Get >95% confidence in significance of result – that is, null hypothesis disproved l Ho: Timecolor = Timeb/w – OR, there is an influence – ORR, only 1 in 20 chance that difference occurred due to random chance

Means Not Always Perfect Experiment 1 Experiment 2 Group 1 Mean: 7 Group 2 Mean: 10 1, 10 3, 6, 21 6, 7, 8 8, 11

Inferential Stats and the Data Are these really different? What would that mean?

Hypothesis Testing l Tests to determine differences – – – l t-test to compare two means ANOVA (Analysis of Variance) to compare several means Need to determine “statistical significance” “Significance level” (p): – – The probability that your null hypothesis was wrong, simply by chance p (“alpha” level) is often set at 0. 05, or 5% of the time you’ll get the result you saw, just by chance

Errors l l Errors in analysis do occur Main Types: – – l Type I/False positive - You conclude there is a difference, when in fact there isn’t Type II/False negative - You conclude there is no difference when there is And then there’s the True Negative…

Drawing Conclusions l Make your conclusions based on the descriptive stats, but back them up with inferential stats – l e. g. , “The expert group performed faster than the novice group t(1, 34) = 4. 6, p >. 01. ” Translate the stats into words that regular people can understand – e. g. , “Thus, those who have computer experience will be able to perform better, right from the beginning…”

Tools to support data analysis l Spreadsheet – simple to use, basic graphs – Can even do basic statistical analysis l Statistical packages, e. g. SPSS l Qualitative data analysis tools – Categorization and theme-based analysis, e. g. NVivo, Atlas. ti – Quantitative analysis of text-based data

Analysis and Presentation for Part 3 l l List of problems from HE with severity ratings List of problems found in CW Basic quantitative analysis from your observation Basic qualitative analysis from your observation – l Places where problems occur, general story of what and how people did, etc. Basic quantitative and qualitative analysis from the questionnaire or interview – Tables of responses, averages, etc. as appropriate

Interpreting your results l l l Go through each usability criteria – do results demonstrate support for meeting this criteria or not? How do they? Discuss any other problems with aspects of the design that your results demonstrate. Discuss how you would modify the design based on these results.

Reminder: Wednesday’s plan l l 3: 30 -4: 05 Cognitive Walkthrough 1 member of design team (D) will facilitate 4 members of the evaluating team D walks through each task, evaluating team asks and answers the 4 questions for every action D makes sure all feedback is written down and takes back to rest of design team

Cognitive Walkthrough pairs l l Rabid Bunnies – User One The Team - Satisfaction Inventive Innovators – No Spoon Awesome - No. Name

Monday’s plan l l 4: 10 -4: 45 Heuristic evaluation 1 member of the Design team (D 2) demos the prototype to the evaluating team D 2 provides the set of heuristics Evaluating team individually writes down all problems they see and gives it to D 2

Heuristic evaluation teams l l Rabid Bunnies – The Team User Won - Satisfaction Inventive Innovators - Awesome No. Spoon – No. Name

Come Prepared! l l l Bring your prototype, have it ready to go at 3: 30 Choose facilitator (D 1 & D 2) for both Bring task & action lists for cognitive walkthrough Bring heuristics for heuristic evaluation As an evaluator – be detailed, thorough, and constructive