UKOLN%20is%20supported%20by:

1
Usability on a Shoestring Budget (2) Emma Tonkin
Adam Hardy Software Systems, UKOLN HCI
Department, University of Bath
UKOLN is supported by
www.bath.ac.uk
2
Analysing the results

• Data analysis
• What problems appeared?
• Which were recurrent?
• Place them in context why did they appear?
• Consider personal variables age, experience,
  motivation, education, level of interest, stress
  (especially if videoed)

3
Reporting the results

• Document what you did and why explain why you
  made your decisions
• Justify your interpretations
• Include output data (if possible remember data
  protection, etc!)
• Provide summaries of results

4
Now what?

• Youre aware that there are problems.
• What next?
• Consider the following
• The stage the project is in
• The available resources
• The complexity of the problem solutions
• Ideally, user testing should occur frequently
  during a projects lifecycle. (But this is not an
  ideal world).

5
Why do projects fail?

• Project Impaired Factors of the Responses
• 1. Incomplete Requirements 13.1
• 2. Lack of User Involvement 12.4
• 3. Lack of Resources 10.6
• 4. Unrealistic Expectations 9.9
• 5. Lack of Executive Support 9.3
• 6. Changing Requirements Specifications 8.7
• 7. Lack of Planning 8.1
• 8. Didn't Need It Any Longer 7.5
• 9. Lack of IT Management 6.2
• 10. Technology Illiteracy 4.3
• 11. Other 9.9

6
Applying the results
Low-hanging fruit?
Bug fixes
Strange interaction flow
Misnamed element
Confusing colours
Feature requests
It would be much easier if this textbox
autocompletedthe system remembered my email
preferences
Major objections
I dont like type of applicationI prefer
totally different type of application
(Oh)