1 / 15

Administrivia

This article discusses the importance of critical thinking in user-centered design, specifically in framing the problem. It provides examples, rationale, and justification to support the design decisions made. The article also covers challenges and complexities in applying user-centered design in real-world contexts and strategies to persuade others to engage in these activities.

rsomers
Download Presentation

Administrivia

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Administrivia • Final Exam • Due Date – Thursday, March 17 • Q & A • Deliverable 2 • Q & A

  2. Critical Thinking • Situation: Framing the problem • Why? • Think critically • May seem obvious • May be thinking it, but not writing it • Applying Grounds, Claims & Warrants to UCD

  3. Rationale & Justification • Context of your work • The following are good examples from student work for Deliverable 1 • Rationale • Citations • Justification

  4. 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

  5. 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

  6. Design Activity • Redesign the Feedback page • Document • Rationale to support design decisions (explicit) • Trade-offs

  7. Project Sharing • Team discussions • Share results of usability testing • Discuss your choice of methods and results • Class-level discussion • Each spokesperson share • One challenge • One surprise • One lesson learned • Paper Prototyping in the Street

  8. 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. Rob MacDonald2. Sammy Woogerd 3. Tiffany Fehr

  9. Topic I: Presenting solutions in the context of user-centered design Arguing for UCD Driving Questions: • What challenges and complexities are associated with UCD in the “real” world? How does this affect how you talk about user-centered design processes and proposed solutions? • What are contexts in which you might be asked to engage in user-centered design activities? What strategies can one use in order to persuade and/or convince others to engage in user-centered design activities?

  10. 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 can’t use products efficiently and effectively? • Search button • Enter key to invoke Search • Web-based tab menus • Expense reporting • Cost of frustration and dissatisfaction???

  11. 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

  12. 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 Discussion

  13. Project Deliverable 2 Solution Recommendation • In this report, students will present their final solution along with their justification of 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. Where we’ve 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 we’re 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. Michael Harding 2. Ursula Wright 3. Walter Boelter Looking back / Looking ahead

More Related