Transcript
Page 1: This Product Sucks! for Midwest UX Conference

“This Product Sucks!”A Sampler of Product Design Issues

20-minute version for Midwest UX 10Apr2011

Darren [email protected]

@darrenkall#midwestux

KALL ConsultingCustomer and User Experience Design and Strategy

© Kall Consulting 2011

Page 2: This Product Sucks! for Midwest UX Conference

Where was this?

Page 3: This Product Sucks! for Midwest UX Conference

Audience Test

Does this product suck?

Page 4: This Product Sucks! for Midwest UX Conference

This product

is disturbing

but

does not suck.

Photo Credit

Page 5: This Product Sucks! for Midwest UX Conference

This product

is broken

but

does not suck.

Photo Credit

Page 6: This Product Sucks! for Midwest UX Conference

This product

is annoying

but

does not suck.

Photo Credit

Page 7: This Product Sucks! for Midwest UX Conference

This product

is ugly

but

does not suck.

Photo Credit

Page 8: This Product Sucks! for Midwest UX Conference

• .This product

is a lie

but

does not suck.

Photo Credit

Page 9: This Product Sucks! for Midwest UX Conference

YES.

This product sucks.

Photo Credit

Page 11: This Product Sucks! for Midwest UX Conference

One Dozen Products that Suck

Problem

Root Cause

Prevention

Photo Credit

Page 12: This Product Sucks! for Midwest UX Conference

Problem 1: Triathlon scenario = running, biking, swimming.

Photo Credit

Watch is ruined if you press buttons underwater.

Page 13: This Product Sucks! for Midwest UX Conference

Root Cause: Implementation or technology did not meet up with user scenario.

Photo Credit

Page 14: This Product Sucks! for Midwest UX Conference

Prevention:

•User scenarios

•Task flow analysis

•Usability test

•Beta test

•Customer concept validation

Photo Credit

Page 15: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 2: Adaptive transmission not designed for a shared car or variable driving style.

Page 16: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause: Designed for ideal-world case not real-world case.

Page 17: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention*:

•User research

•Workflow

•Task flow

•Activity cycles

•Beta test

* To credit VW, they redesigned and eventually dropped this feature.

Page 18: This Product Sucks! for Midwest UX Conference

Photo Credit

Pull or Push? Can you tell?

Page 19: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 3:

Even with signs users bang into doors.

Page 20: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause:

Handle affordances not distinguishable.

Page 21: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention: Design for affordances. Things that look the same should act the same.

•Heuristic evaluation

•Usability checklist

•Remembering your own experiences

Page 23: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 4: Frustrating experience to pay for parking.

Page 24: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause: Bad information architecture, bad visual design, bad task flow …

Page 25: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention: •Intentional IA design

•Task flow analysis

•Usability study

•Participatory Design

•Guerilla UX

Page 26: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 5: Scalding or freezing shower.

Page 27: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause: Fixing bad UI in help, the manual, or in training.

Page 28: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention: Fix the product, not the user.

Page 30: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause:

•Did not anticipate expected user behavior.

•Did not prevent fatal errors.

Page 31: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention:

•Do not design against engrained user behaviors

•Usability test

•Task flow analysis

Page 33: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 7: Believing “Don’t worry, we’ll fix it later.”

Page 34: This Product Sucks! for Midwest UX Conference

Photo Credit

Root cause: “Later” never happens.

Page 35: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention: Prioritize user-impacting “bugs”.

Page 36: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 8: Breaking user trust.

Page 37: This Product Sucks! for Midwest UX Conference

Photo Credit

Root cause:

•Telling lies

•Making mistakes

•Assuming customers can’t do math

Page 38: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention:

•Don’t lie

•Correct even minor mistakes – they accumulate

•Remember users are smarter than you think

Page 39: This Product Sucks! for Midwest UX Conference

Problem 9: The self-locking hotel internal bedroom suite door.

Photo Credit: Darren Kall

Page 40: This Product Sucks! for Midwest UX Conference

Root Cause: Things are not used in a vacuum – missed system design.

Photo Credit: Darren Kall

Page 41: This Product Sucks! for Midwest UX Conference

Photo Credit: Darren Kall

Prevention:•Interactive system analysis•Beta testing•Fix stuff customers complain about

Page 43: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 10: No sidewalk where people want to walk.

“I’m the user damn it!”

Page 44: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause: Prohibition does not work.

Page 45: This Product Sucks! for Midwest UX Conference

Photo Credit

•Prevention:

•Participatory design

•Catch the user

•Democratize design

Page 47: This Product Sucks! for Midwest UX Conference

Photo Credit

Problem 11: Can’t set alarm. Can’t follow directions. Don’t trust product.

Page 48: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause: Product not designed for use. Instruction is a poor substitute for good design.

Page 49: This Product Sucks! for Midwest UX Conference

Photo Credit

Prevention: Usability test. Products should be easy to use.

Page 51: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause: “We lost sight of our customers” James Lentz

Page 52: This Product Sucks! for Midwest UX Conference

Photo Credit

Root Cause: “Complaint investigations focused too narrowly on technical without considering HOW consumers USED their vehicles.”

James

Lentz

Page 53: This Product Sucks! for Midwest UX Conference

Photo Credit

•Prevention: •Listen to customers

•Check if solution explains the user data (70% not the pedal)

•Test for worked “as used” not “as designed”

•Ethnographic research into drivers

•Analytics on real users to build test scenarios

•Listen to experts

• …

Page 54: This Product Sucks! for Midwest UX Conference

In Conclusion:

Don’t tolerate products that suck.

Don’t buy products that suck

And …

Photo Credit

Page 55: This Product Sucks! for Midwest UX Conference

Don’t

design

products

that

suck.Photo Credit

Page 56: This Product Sucks! for Midwest UX Conference

Don’t design products that suck:

1. Meet (advertised) user scenarios with capabilities2. Design for real-world use not ideal-world3. Distinguish affordances 4. Design with conscious intention5. Fix the product, not the user6. Don’t design against engrained behaviors7. Prioritize user-impacting “bugs”8. Correct even minor mistakes9. Remember your product is part of a whole system10. Prohibition does not work – democratize design11. Products should be easy to use12. Don’t lose sight of HOW customers USE your product

Page 57: This Product Sucks! for Midwest UX Conference

Darren Kall• [email protected]• http://www.linkedin.com/in/darrenkall• @darrenkall• +1 (937) 648-4966• http://www.slideshare.net/DarrenKall

Thank you.

KALL ConsultingCustomer and User Experience Design and Strategy

Darren Kall• [email protected]• http://www.linkedin.com/in/darrenkall• @darrenkall• +1 (937) 648-4966• http://www.slideshare.net/DarrenKall