CMSC434 Week 02 | Lecture 03 | Sept 10, 2013 Wrapping up … · 2013-09-11 · That’s why we study the design process To know what we do and how we do it To understand it and improve

Human Computer Interaction Laboratory

@jonfroehlich Assistant Professor Computer Science

CMSC434 Introduction to Human-Computer Interaction

Week 02 | Lecture 03 | Sept 10, 2013

Wrapping up Design Processes

Beginning Understanding Users I

Hall of Fame Hall of Shame

Source: CMSC434 Student Joe Stout




It is hard to tell if it is a back end issue or not because I am not being conveyed any information. The UI has failed me by not telling me the problem, and the back end has failed by not processing my information and sending me an email. Another issue could be that the verify button isn't posting any information at all and simply directs me back to the same webpage. Possible fixes to this is to ensure that the verify button is set up correctly, give some general troubleshooting advice on the page or at least a link to more information, and perhaps to send some sort of email with further instructions in case something like this ever happens.

IF YOU BUILD IT, THEY WILL COME Reflecting on the Successes (and Failures) of Building a Collaborative Workspace

to Support Creativity, Experimentation, and Making

HCIL Brown Bag Discussion

September 12th, 2013: 12:30-1:30PM

Human Computer Interaction Laboratory

@jonfroehlich Assistant Professor Computer Science

@jonfroehlich Assistant Professor CS

DSST 2013 Workshop

July 30th, 2013

My Talk on Building the HCIL Hackerspace

2119 Hornbake Building, S Wing

Time: Thursday, Sept 12th, 1:30-2:30PM

Today

1. Project pitches and voting

2. RR01 : ABC News Nightline IDEO Video

3. Idea generation

4. Design processes

5. Start on understanding users

http://cmsc434-f13.wikispaces.com/IA03+Pitch+Vote

IDEO ABC Nightline, July 1999

Source: http://goo.gl/eyTsLU

generation idea

The best way to have a good

idea is to have lots of ideas.

Linus Pauling Professor of Chemistry

Caltech, UC San Diego, Stanford

Only person awarded two unshared Nobel Prizes

Elaboration

Design Process

Original source: Paul Laseau,Graphic Thinking for Architects & Designers, 1980; Ref from Greenberg et al., Sketching User Experiences, 2012

Elaboration and Reduction

Design Process


Source: http://www.slideshare.net/ugleah/how-to-be-a-ux-team-of-one

Design Process

Elaboration and Reduction

Design Process Design Process


IDEOBrainstormingRules 1. Be visual

2. Defer judgment

3. Encourage wild ideas

4. Build on the ideas of others

5. Go for quantity

6. One conversation at a time

7. Stay focused on the topic

Tom Kelley and Jonathan Littman, The Art of Innovation: Lessons in Creativity from IDEO, 2001

IDEOBrainstormingKillers 1. The boss gets to speak first

2. Everybody gets a turn

3. Experts only please

4. Do it “off-site”

5. No silly stuff

6. Writing down everything

[Kelley, The Art of Innovation]

CandleProblem

[Duncker, 1945]

Who has seen this

problem before?

How to fix a lit candle on a wall in a way so the candle wax won't drip onto the table

below. To do so, one may only use a book of matches and a box of thumbtacks

CandleProblem

[Duncker, 1945]

CandleProblem

[Duncker, 1945]

FunctionalFixedness

[Duncker, 1945]

Functional fixedness is a cognitive bias that limits a person to using

an object only in the way it is traditionally used

A “mental block against using

an object in a new way that is

required to solve a problem”

FunctionalFixedness

[Adamson, 1952]

Group 1:

Preutilization Boxes presented as a

container with

materials inside them

Group 2:

No Preutilization Boxes were presented

empty

“Try stuff and ask forgiveness rather

than asking permission is the way

that people come up with new

ideas.”

DavidKelley Founder and Chairman of IDEO

BeDaring

“Being playful is of huge importance

in being innovative. If you go into a

culture, and there’s a bunch of stiffs

going around, they are not likely to

invent anything.”

DavidKelley Founder and Chairman of IDEO

Playfulness

design processes

some

The point is that we’re not actually experts in

any given area. We’re experts in the

process of how you design stuff. We don’t

care if you give us a toothbrush, a tractor, a

space shuttle, or a chair.

David Kelley Co-Founder of IDEO and Stanford Design Professor

Quote from: ABC Nightline The Deep Dive with Ideo

A soufflé is eggs, butter, milk, and flour but

the difference between soaring and sinking

is in the execution.

Björn Hartmann Professor of Human-Computer Interaction

Computer Science, University of California, Berkeley

As with most things, following a vetted process

and practicing will improve performance

If we wish to improve our products,

We must improve our processes;

We must continually redesign

Not just our products

But also the way we design

That’s why we study the design process

To know what we do and how we do it

To understand it and improve it

To become better

Hugh Dubberly, How do you design?, Dubberly Design Office, San Francisco

Getting the design right and the right design.

Bill Buxton Principal Researcher at Microsoft Research

One of the more influential figures in IxD Quote from: Buxton, Sketching User Experiences, 2007

A Design Process

A problem A solution

Hugh Dubberly, How do you design?, Dubberly Design Office, San Francisco, http://www.dubberly.com/articles/how-do-you-design.html

A Design Process


A problem

A solution

Tim Brennan Apple (Creative Services Department)

“Somebody calls up with a project; we do

some stuff; and the money follows”

Process Model Benefits Has potential for playfulness/fun

Is similar to a random walk

Has a feeling of iteration…

All Design Processes


Process Input Output

(Most) Design Processes


Process Input Output

Feedback

One of the simplest and most common

observations about designing… is that it

includes the three essential stages of

analysis, synthesis, and evaluation.

John Chris Jones Quote from: Jones, Design Methods, p. 63

Design

Build

Evaluate

A Design Process The Iterative Design Process

Design

Build

Evaluate

A Design Process The Iterative Design Process

Dix et al., Human-Computer Interaction, 3rd edition, 2004, p 196

A Design Process Dix et al.’s Interaction Design Process

1. Requirements: what is needed? Use formative inquiry

methods such as interviews, surveys, observation

2. Analysis: how to use formative data? Methods to analyze

qualitative and quantitative data to inform design

3. Design: moving from what you want to how to do it. There are

a number of rules, guidelines, and principles to help us.

4. Iteration and prototyping: We can’t expect to get the design

right the first time. Build prototypes, evaluate, adapt prototypes

5. Implementation and deployment: Deploy most successful

design, which involves writing code, making hardware, writing

manuals, etc.

Analysis

Implement

and deploy

Affinity diagraming

Task analysis

Scenarios

Based on Dix et al., Human-Computer Interaction, 3rd edition, 2004, p 195

What is

wanted

Design Ethnography

Surveys

Interviews

Evaluation

Design Critique

Heuristics

Prototype

Guidelines

Principles

Specification Design

A Design Process Dix et al.’s Interaction Design Process

Evaluate

Final product

A Design Process Roger’s et al. IxD Lifecycle Model

Rogers et al., Interaction Design, 3rd edition, 2011, p 332

Design / Redesign

Identify needs/ establish

requirements

Build an interactive

version

http://www.slideshare.net/nielschrnilsson/lifecycle-models-needs-and-requirements-and-prototyping


Traditional Waterfall

Lifecycle Design

Process


Traditional Waterfall

Lifecycle Design

Process

The design practice we observed in the late 1970s

was more complex than contemplated by

psychology and software engineering, but it was still

woefully oversimplified. “User testing” was generally

seen as a validation process tacked onto the very

end of system development.

John M. Carroll Professor of HCI at Penn State

One of the early pioneers of the field Quote from: Carroll, Reconstructing minimalism, SIGDOC’97

The design practice we observed in the late 1970s

was more complex than contemplated by

psychology and software engineering, but it was still

woefully oversimplified. “User testing” was generally

seen as a validation process tacked onto the very

end of system development. In those days, the

objective of user testing was to identify glitches that

could be “papered over” before the system was

delivered. Indeed, users played almost no role at

all in system design.

John M. Carroll Professor of HCI at Penn State

One of the early pioneers of the field Quote from: Carroll, Reconstructing minimalism, SIGDOC’97

Beck, K. Embracing change with extreme programming. Computer, 32(10), 70–77. doi:10.1109/2.796139

Extreme Programming

All begin with “understanding needs” to help establish design requirements

users understanding

users understanding

UserResearchMethods

Formative Evaluative Build

Ethnography

Interviews

Surveys

Cultural Probes

Focus Groups

Diary Studies

Experience Sampling Studies

Studying Similar Products

Interaction Logging of Past Product /

Early Prototype

Studying Past Product Documentation

…

Ethnography

Interviews

Surveys

Focus Groups

Diary Studies

Experience Sampling Studies

Interaction Logging

…

Surveys Video Ethnography

Focus Groups Observational

Techniques

Statistical

Macro techniques

(many people)

Micro techniques

(few people)

Interpretive

Saying Doing Explicit opportunities and needs Latent opportunities and needs

[Designing Interactions by Bill Moggridge, 2007]

[Designing Interactions by Bill Moggridge, 2007]

All user research techniques

have their own limitations

Use multiple techniques to

fully understand a design

scenario o Choose techniques that account for

the weaknesses of each other

o Choose techniques to cover both

depth and breadth of the user

experience

KeyPoint: Triangulation

observation

importance of

Design Thinking 60 Minutes, January 2013

Source: http://goo.gl/SPwdPE

YogiBerra MLB Player / Quote Machine

“You can observe a

lot by just watching”

Pimentel, Big Blue to expand viewpoint / Research center to add nontechnical specialists to staff, San Francisco Chronicle, Oct 21, 2003

Pimentel, Big Blue to expand viewpoint / Research center to add nontechnical specialists to staff, San Francisco Chronicle, Oct 21, 2003

Why can’t we

just ask users

what they

want?

Users’ Words are Unreliable

People are notoriously bad at predicting what

they would use or would prefer when it is only

hypothetical

They can much better respond to actual,

concrete things, or make comparisons

This highlights the importance

of observation and of prototypes!

Plus x2…

“It’s not the consumers’

job to know what they

want.”

SteveJobs Designer / Inventor / Creative Genius

“If I had asked my

customers what they

wanted, they would

have said a faster

horse.”

HenryFord Inventor / Car Salesman

So, often it’s better to

watch what people do

than to only design

solely for what they

say

What’s wrong with the measuring cup?

Alex Lee , Oxo Design Process and Products, GEL2008, http://vimeo.com/3200945

Nobody mentioned that this is a

problem because this is an accepted

part of the process of measuring.

Alex Lee OXO International, President


Nobody mentioned that this is a

problem because this is an accepted

part of the process of measuring.

We are happy when we see this

problem, this clear inefficiency that

nobody articulates.

Alex Lee OXO International, President


Show us how you measure.


The Role of Ethnography in Design

In anthropology, ethnography developed as a

way to explore the everyday realities of

people living in small-scale, non-Western

societies and to make understandings of those

realities available to others.

Mark Burrell Psychologist

Microsoft Corporation

Blomberg and Burrell, An Ethnographic Approach to Design, The HCI Handbook, 2007, p966

Jeanette Blomberg Anthropologist

IBM Research

Today, the ethnographic approach is not limited

to investigations of small-scale societies, but

instead is applied to the study of people and

social groups in specific settings within large

industrialized societies, such as workplaces, senior

centers, and schools…





IBM Research

The 3 principles of Ethnography

Holistic: tiny details into big picture context;

attempt to look at things broadly—understand

context

Natural settings: Directly observe in the things

that you’re trying to study

Desciptive: focus on recording behavior—

analysis comes later

Ellen Isaacs Ethnography at TEDxBroadway

Source: http://youtu.be/nV0jY5VgymI

Dennis Ritchie (beard) with a PDP-11, circa ~1970s, http://thetamnews.org/2011/10/dennis-ritchie-computer-scientist-dies-at-70/

System 360 Model 75, Oak Ridge National Laboratory Supercomputer, IBM 1960s

There was a realization that the designers and

developers of these technologies could no

longer rely exclusively on their own

experiences as a guide for the user requirements

of these new systems.





IBM Research

There was a realization that the designers and

developers of these technologies could no

longer rely exclusively on their own

experiences as a guide for the user requirements

of these new systems. Instead, designers and

developers needed a way to gain an

understanding of the everyday realities of

people working within these diverse settings.





IBM Research

Feedback on Project Proposals

Documents

CMSC434 Week 02 | Lecture 03 | Sept 10, 2013 Wrapping up … · 2013-09-11 · That’s why we study the design process To know what we do and how we do it To understand it and improve