CS102: Monsoon 2015

CS 102 Human-Computer Interaction

Lecture 6: Human-centered design (3)

1

CS102: Monsoon 2015

Course progressQuiz later today (no make up if you miss)

Please use Moodle forums to discuss class material, post related links, etc.

Idea logs?

https://phrp.nihtraining.com (certs due next Monday, Sept. 21st)

2

CS102: Monsoon 2015

Project teams

3

Mohit Deva

Koishore Aania

Ayushree Himanshu

Rhea

Yash Dhairyya

Arjun

Shivangi Apuroop Samriddh

Minchu Anirban

Urvin

Kshitij Kamal Ishika

Vijay Yaswanth Manisha

Mihika Anvi

Paras

Sankalp Paul

Shreyash

CS102: Monsoon 2015

Project teams

Projects should have a big component of human-centered design and follow the process systematically

Do not design for (just) yourself

Do not jump into implementation

Ask why? Look for alternate possibilities

4

CS102: Monsoon 2015

Recap

5

CS102: Monsoon 2015

Debrief: interview exercise

6

CS102: Monsoon 2015

Contextual enquiry

7 Don’t ask your customer by Karen Holtzblatt

CS102: Monsoon 2015

Studying the findingsStructured interpretation sessions

Other team members ask questions

Be aware of biases

Go back for clarifications

Create a rubric as a pattern emerges

Which feature is needed?

How important is it to each user?

8 Don’t ask your customer by Karen Holtzblatt

CS102: Monsoon 20159 http://incontextdesign.com/articles/beyond-the-tower-of-babel/

CS102: Monsoon 2015

User personasOne way to summarize research

A portrait of a user based on user understanding

A “fleshed-and-blooded-out” person for whom the interface is designed

Represent important classes of users

e.g. my mother-in-law for old people

Could be real or fictitious

10 Personas: Practice and Theory

CS102: Monsoon 2015

User personas

11 How to create personas

CS102: Monsoon 2015

Understanding usersStudying and understanding users is one of the most important things HCI designers do

Many specific techniques:

Surveys

Observation

Probes

Diary/pager studies

Interviews

Contextual enquiry

Ethnographic methods

…

12

CS102: Monsoon 2015

Human-centered designHuman needs, capabilities and behaviors are put first, and then a product is designed to support them

1. Understand user

2. Build prototypes

3. Test

Avoid specifying the exact problem too early to avoid narrow framing

13

CS102: Monsoon 2015

Prototyping

14

human

CS102: Monsoon 2015

Why prototype?

Inexpensive and quick way to test ideas

Often people have one idea and one design. Prototyping lets designers try out multiple ideas

15

CS102: Monsoon 2015

Key variablesForm: On-paper, physical, software, mock-up, …

Fidelity: informal to polished

Functionality: minimal to detailed

Aspect: which aspect of the design?

Throw-away or iterative?

16

CS102: Monsoon 2015

Lo-fi prototypesExcellent to test high-level UX issues

Many details are missing (user very aware that it is a prototype)

Cartoonish representation ensures that peripheral aspects do not overshadow core functions

Allows non-programmers to participate. If possible, different people build different ones (avoids fixation)

17

CS102: Monsoon 2015

Paper prototypesMade with materials like paper, index cards, tape, glue, markers, correction fluid, ….

Different screens on different sheets

Crudely made widgets

Simulate interaction

Person acts as a computer

18 https://www.youtube.com/watch?v=9wQkLthhHKA

CS102: Monsoon 2015

Prototyping exercise

First part of your project (per team):

Build prototype for an Ashoka shuttle app using Balsamiq (or similar online prototyping tools). Your prototype should have 4-5 screens

Submit files/screenshots before class on Sept. 28th

19