Wednesday, April 22, 2009

Final Reports & Presentation

You’ve Done Design Briefs
  • Team Members
  • Statement of Problem/Challenge
  • Activities to Date
  • Summary of User Interviews & Participant Profiles
  • Design Priorities and Issues
  • Quick Review of Related Products/Systems
  • Persona(s)
  • Task Statements
  • Evaluation Plan
  • Exposures
  • Schedule of Design & Evaluation Activities

Final Reports: Goals
  • Present a problem/challenge
  • Show how you used HCI methods to arrive at a solution
    • Discuss design alternatives
    • Motivate design decisions
  • Choices were not arbitrary
  • Choices move design closer to “optimal”

Final Report: Required Sections: Part 1
  • Team Members*
  • Statement of Problem/Challenge*
  • Review of Related Products/Systems*
  • Summary of Interviews and Participant Profiles*
  • Key Design Issues and Priorities*
  • Personas* (may be primary and secondary)
  • Task Statements* (OK if revised)

*Included in Design Brief. Revise as necessary for Final Report

Final Report Required Sections: Part 2
  • Selection Among Design Alternatives
    • Mockups (What were the key findings for each method? How did the findings change your design? Screen shots are helpful, if available)
    • Cognitive Walkthrough
    • Heuristic Analysis
  • User Testing
    • Design for User Testing (What was the design you used for user testing?)
    • Experimental Protocol (What was the procedure you used during testing? Includes instructions, practice tasks, etc.)
    • Tasks (What tasks did participants complete?)
    • Participants (Summarize the general characteristics of participants)
    • Summary of Results/Overview of Findings (summarize the results from user testing. Give examples of comments, and provide screen shots of problematic elements...making a table is helpful or making list of actual aspects of the system and then what were the problems that were found).
***Screenshots in Apple are Apple, shift & #4

Final Report Required Sections: Part 3
  • Recommendations/Revisions from User Testing
    • High Priority (Explain who your prioritization of design issues and the design changes you made as a result)
    • Moderate Priority
  • •Final Design (What was your final design? How does it resolve issues identified during user testing. How does your design meet the needs of your users? Finally, how well does the final design resolve the challenge/problem you identified at the beginning of the report).
  • •Future Issues
Final Report Questions
  • Does your report clearly show the evolution of your design from beginning to end?
  • Do you show how HCI methods informed your initial design and subsequent changes? (Show what was learned in class and how it helped you arrive at your design)
  • Have you made it clear how your user testing informed your final design?
  • Is it clear how your final design will meet your users’ needs and resolve the challenge/problem you identified?
***Final Report can be submitted by May 6th at 5:00pm on WebCT by either PDF or Word***



Presentations
  • 20 minutes per project
    • We have 9 projects total
    • Teams: Each person should present a portion of your project
  • 15-17 minutes for presentation
  • 3-5 minutes for answering questions
    • Audience members: Be active & ask questions!
Presentation Goals
  • Communicate the problem/challenge you were trying to solve
    • Convince your audience that it’s important!
  • User Needs
    • What were the user needs that you identified?
    • What was the initial design?
  • HCI Methods ->Final Design
    • How did HCI methods inform decision decisions?
    • What were the major design changes and why did you make them (e.g., what HCI results convinced you?) (user testing or earlier analysis)
    • How well does your final design meet users’ needs?
Presentation Questions
(can you answer yes at the end)
  • Did you clearly state the problem/challenge and its importance?
  • Is it clear what your users’ needs are?
  • Did you clearly connect the outcomes of HCI methods (e.g., Cognitive Walkthrough, Heuristic Analysis) to major design changes/decisions?
  • Did you make a case for your final design meeting users’ needs?

Wednesday, April 1, 2009

Parts of a Test Protocol

-Welcome
-Explain rights as a participant
-Study is completely voluntary
-You may stop at any time, or opt out of any task, for any reason.
-Instructions (general)
-Invitation for Questions
-Think Aloud Practice...Perform practice
-Task 1 instructions...Perform task
-Task 2 instructions...perform task
-When done, debrief and thank participant
-Give them an overview of the goals of the study
-Ask if they have any questions
-Invite them to contact you if they have questions in the future
-(Often, ask if they would like to participate in future studies)