Administrivia

1
Administrivia

• Final Exam
• Due Date Thursday, March 16
• Q A
• Deliverable 3
• Q A
• Feedback on Heuristic Eval

2
Grading Criteria
3
Critical Thinking

• Situation Framing the problem
• Why?
• Think critically
• May seem obvious
• May be thinking it, but not writing it

4
(No Transcript)
5
Design Activity

• User Information
• Problems with any of the different systems
  operating behind the scenes are perceived as
  problems with the primary application
• 25 of feedback received was not categorized by
  the user and another 26 was categorized as
  Other Problem
• Feedback does not always pertain to the page that
  the user is on when they click the Feedback link
• Some people enter sensitive information

6
Design Activity

• Requirements
• Keep it simple to provide feedback
• Provide acknowledgement and confirmation
• The system is working properly at the time they
  submit feedback
• A message containing the text of their feedback
• Preserve the ability to remain anonymous
• Offer a means of providing candid feedback
  without fear of repercussion
• Commitment of 2 business days for a response
• Urgent matters should be directed to the help
  desk
• People can change their e-mail address

7
Design Activity

• Redesign the Feedback page
• Think on your own
• Pair up with someone not on your team
• Share with the class
• Document
• Rationale to support design decisions (explicit)
• Trade-offs

8
Project Sharing

• Team discussions
• Share results of heuristic evaluations
• Discuss your choice of methods and results
• Class-level discussion
• Volunteers to share especially challenging or
  surprising insights
• Lessons learned
• Paper Prototyping in the Street

9
Cost-Justifying Usability

• Reluctance even with low-cost methods
• Costs 100 times more to make a change in the next
  release (Nielsen)
• How much is lost when employees cant use
  products efficiently and effectively?
• Search button
• Enter key to invoke Search
• Web-based tab menus
• Expense reporting
• Cost of frustration and dissatisfaction???

10
Cost-Justifying Usability

• Measures
• Training time
• Task time/Workload capacity
• Error rate
• Time to recover
• Help desk/Tech support
• Helping coworkers (OJT)
• Revenue
• Projections
• Cost of NOT testing
• Benefits of testing

11
Discussion of Readings

• Insights from supplemental readings.
• Facilitate class discussion of topics / ideas /
  themes garnered from the online discussion,
  related to assigned readings.
• Discussion Leaders
• 1. Jaana Linsenmayer2. Kris Anderson3. Carol
  Taylor

12
Discussion

• What challenges and complexities are associated
  with UCD in the real world?
• What similarities?
• What differences?
• What surprises?
• What implications?
• What makes it hard?
• What constitutes success of UCD?
• Where can you be flexible?
• Where do you have to stand firm?
• What options do you have for applying and
  adapting UCD methods?
• Note Hackos Redish, pp 112-114, for good
  examples of the benefits of site visits

13
Project Deliverable 3 Solution Recommendation

• In this report, students will present their final
  solution along with their justification for that
  solution.
• Project deliverables are due at the beginning of
  class.
• Bring copies of the deliverable to class (one
  copy for the instructor) and also post it to your
  design portfolio.
• Due next Thursday

14
Looking back / Looking ahead

• Where weve been
• Topics Readings and discussion
• What is UCD?
• Collecting and summarizing info about users,
  tasks and context
• Problem definition
• Design
• Evaluations
• Project
• Insights about users, tasks, and contextual
  issues
• Actual data from observing real users
• Problem definition
• Proposal
• Design
• Evaluation (heuristic usability)

• Where were going
• Revisiting UCD
• Challenges
• What supports UCD?
• Readings
• Usability vs. Testing vs. UCD
• UCD processes ISO 13407 (Supp)
• Key principles of UCD
• Upcoming Work
• Solution Recommendation
• Final Exam
• Issue Statement A reminder
• 1. Gülay Birand2. Thea Lehming 3. Ben Turner