Presenting Your Work (plus odds & ends)

Presenting Your Work (plus odds & ends) November 20, 2007

Pet names in the news

iPhone touch keyboard study • 60 participants (20 experienced users each on iPhone, “Blackberry”, phone texters) • Entered 6 messages on own phone • Non iPhone users also tested iPhone • Rated preferences

iPhone touch keyboard study results • iPhone had more errors (5.6 / msg.) than hard mini-QWERTY (2.1 / msg.) or phone keypad (1.4 / msg.) • Rate of entry on iPhone and mini-QWERTY same • Practice improves speed but not error rate • Hard QWERTY keyboard preferred http://www.usercentric.com/news.asp?ID=391

About the Google footer • The story behind why Google has a footer on their page…

Perception tricks • How much difference does < 0.5 second make?

Anthropometrics and Ergonomics • Anthropometrics -- the measurement of the size and proportions of the human body. • Ergonomics -- The applied science of equipment design, as for the workplace, intended to maximize productivity by reducing operator fatigue and discomfort.

Anthropometric data • http://0-www.cdc.gov.mill1.sjlibrary.org/nchs/about/major/nhanes/Anthropometric%20Measures.htm

Dress code anthropometrics

Dress code anthropometrics (2)

Ergonomic data http://www.humanics-es.com/recc-ergonomics.htm http://www.cdc.gov/niosh/docs/94-110/

Steering wheel ergonomics • Tilt steering wheel invented by GM in 1963 • Spreading popularity in late ’60s • Except Mercedes-Benz

Anatomical data Tech Museum, San Jose Through January 26, 2008 http://www.thetech.org/

About intellectual property • Intellectual property = the ideas behind your project • As far as I know…

NEEDS DESIGN EVALUATE IMPLEMENT Finishing the design cycle • We still have a couple more steps to complete the design cycle! • Goal for the class was to get you through the design cycle • Evaluation

User study plan • I’ve emailed feedback • Feel free to ask me more at office hours today, 2:00-3:30, 6th Floor alcove in Soda • We need to talk about this more

More specific detail • What is starting point? • How will you instruct the participant to achieve the desired endpoint? • What is the list of questions you will ask? • Neutral wording • Anchor words for Likert scales

Meaningful tasks and measures • Installing and making sense of application may be important • Install this application, explore, tell me what you think it does • Compare with complete list of features • Completion time may not make sense for “thinking” or “creating” tasks

Study logistics • Realistically, no more than 5 tasks • Preferably, no more than 12 survey questions • Preferably, no more than 10 open-ended interview questions • Keeping the study interesting, not tedious for the participants • You only have 2 weeks

Study logistics (2) • Most studies will require facilitator and separate observer • Many consent forms were missing contact info (for questions later) • Sample form link on web site, Nov. 8 • “Think aloud” requires at least one practice task • Volunteer to participate in other groups’ studies

Almost all were missing… • Any plan for pilot testing!!!! • When will you do pilot testing? (at least a day for modifications before collecting real data) • How many pilot subjects? (at least one, but a couple would be better) • Will be looking for how you pilot tested, changes you made in final report Go Stanford!

More detail on user study • Need to think specifically about user tasks • What is starting point? • Script of what you are asking them to do • Write out questions for survey • If Likert scale, also write out anchors http://apps.facebook.com/dodge_ball/

Final report + project presentation • Due week of Dec. 4 & 6 • Convince project manager to give this project the “green light” • Final report on user study • Project presentation on project • Final individual assessments • Make sure teaching team has access to facebook application by 5:00 Nov. 30

Final report • Report how you conducted the user study and summarize what you learned from it • Focus on what changes you would make based on the user study • Next steps in the development

Final report sections • Brief review of need and introduction of project • Evaluation • Methodology • Activities studied (illustrate with application screenshots) • Pilot test and changes made from pilot • Summarized data • Analysis and Conclusions • Changes based on user study • Future Work—what should be done next • Next steps for development • Appendices (only if necessary!) • Informed consent form • Detailed user data if referred to in report

Project presentation • Every member of team must present! • Summarize project (video record?) • 11-minutes (plus 2 minutes for questions and switchover) • Include need (skit possibility) • Recorded demo (no more than 2 minutes) • Brief implementation description (architecture diagram) • Focus on user study, what you learned from it, design changes • Future work

Architecture diagram (Recent Shortcuts) User interface Lotus Notes Mail templatemodification DB Mozilla Thunderbird Extension My Recent Documents Lotus Sametime Plug-in C# applicationJavaJavaScriptLotusScriptVisual Basic Directory listener Corporate directory

facebook architecture diagram • What information you are collecting from whom • What information presented in canvas, profile, other devices • Flow from collecting information to presenting information in facebook

Iterating on the design process cycle • Focusing on design changes • Next steps NEEDS DESIGN EVALUATE IMPLEMENT

Presentation logistics • Wozniak Lounge • Inviting outside guests to attend • Dress is business casual • Refreshments will be there at 10:20 • Would like to start at 10:30 • We’ll publish a schedule (volunteers for first of the day?)

Final presentation scheduling • If your group presents on Tuesday, Dec. 4, your final report is due on Thursday, Dec. 6 • If your group presents on Thursdays, Dec. 6, your final report is due on Tuesday, Dec. 4 • Send email with your preferences to cs160—first come, first served (volunteer for first session slot)

Presenting Your Work (plus odds & ends)