UCDIntroduction

sequence

sequencecontext define q&a

2 requests

cheers and jeers pls save questions for q&a

source:

source: alan cooper

indelible

context

software quality

software quality

over time

daily use

improvement?

dog’s breakfast?

tolerance for bad design

impatience / friction

our context

an engineer should:code

test do the interface

prototype manage

scope spec

document communicate

be fast pontificate

know everything

TOO MUCH

TOO MUCH not fun

TOO MUCH inefficient

– scramble – – too much –

– don’t support – – crap –

– scramble – – too much –

– don’t support – – crap –

( repeat )

break the cycle

shake shit up

shake shit up (literally)

get out of our comfort zone

what’s UCD?

3 powerful tools

personas goals

interactions

IxD

How we experience software

How we experience softwareloops

IxD

user centric

not user driven

not user driven

not user driven

not user drivennot user interface

objects

not user drivennot user features

timing

not user drivennot user features

timing

help!

riding the tiger

goals

tasks aren’t goals

specificity

personal

professional

practical

false

sufficient specs >conversations

sanity

dancing bear

nature of the work

challenging

virtual builder math

composer

expensive

movie production

3 phases

3 phasespre-production

production post-production

benefits

benefitsagility

fun quality

how do we evaluate?

1. if it makes better software 2. the development process

1. if it makes better software 2. the development process more

1. if it makes better software 2. the development process more

fun creative exciting

designing an entire experience from sit-down to stand-up

best in breed examples: !

Amazon check-out Gmail read/reply

Etsy find Facebook browse

JIRA column browser

good artists copy

good artists copy great artists steal

repeat:

user centric

personas > goals > interactions

crisp spec

agility

sanity

expectations

designed, not incidental software

coherence

where can we take this?

what do we have?

can’t be done by one

can’t be done by one personskill set

grouplayer

define our environment

get out of our comfort zone

evolve how we do things

–Ernest Hemmingway

“Write drunk, edit sober.”

q&a