226
back in User Experience Putting the User @jeremyjohnson

Putting the "User" back in User Experience (Dallas Techfest Edition)

Embed Size (px)

DESCRIPTION

If you ask an organization "Are you customer centric?" - of course they say "yes", but as you peel back the layers too many organizations have teams of people building software - and the user is nowhere in sight. This talk will go over a number of ways to include users in your product design process, from start to finish. It's time we truly live up to the term "User Experience".

Citation preview

Page 1: Putting the "User" back in User Experience (Dallas Techfest Edition)

back in User ExperiencePutting the User

@jeremyjohnson

Page 2: Putting the "User" back in User Experience (Dallas Techfest Edition)

@jeremyjohnson

(yes, we’re hiring)

Page 3: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.slideshare.net/jeremy/presentations

Page 4: Putting the "User" back in User Experience (Dallas Techfest Edition)

WORKED FOR

Page 5: Putting the "User" back in User Experience (Dallas Techfest Edition)

WORKED WITH

Page 6: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 7: Putting the "User" back in User Experience (Dallas Techfest Edition)

Uncover user needs, Design great solutions,

and build out solutions to launch.

Page 8: Putting the "User" back in User Experience (Dallas Techfest Edition)

USER EXPERIENCE

Page 9: Putting the "User" back in User Experience (Dallas Techfest Edition)

we make things for

Page 10: Putting the "User" back in User Experience (Dallas Techfest Edition)

we make things for

http://500px.com/jeremyjohnson/sets/buenos_aires_2012

Page 11: Putting the "User" back in User Experience (Dallas Techfest Edition)

We work in ecosystems

http://500px.com/jeremyjohnson/sets/london_2012

Page 12: Putting the "User" back in User Experience (Dallas Techfest Edition)

we think visually

Page 13: Putting the "User" back in User Experience (Dallas Techfest Edition)

We learn through observation

http://500px.com/jeremyjohnson/sets/london_2012

Page 14: Putting the "User" back in User Experience (Dallas Techfest Edition)

we’re curious

http://500px.com/jeremyjohnson/sets/london_2012

Page 15: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 16: Putting the "User" back in User Experience (Dallas Techfest Edition)

USER EXPERIENCE

Page 17: Putting the "User" back in User Experience (Dallas Techfest Edition)

USER EXPERIENCE

Page 18: Putting the "User" back in User Experience (Dallas Techfest Edition)

Mr. User

Page 19: Putting the "User" back in User Experience (Dallas Techfest Edition)

Mr. User Software Development Product Decisions

“Hey, what’s going on over there?”

Page 20: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I know the users!” “They’ll love this when we release next year!!”

Page 21: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.amazon.com/The-Inmates-Are-Running-Asylum/dp/0672326140

Page 22: Putting the "User" back in User Experience (Dallas Techfest Edition)

2 I’ve got…

Page 23: Putting the "User" back in User Experience (Dallas Techfest Edition)

#1 You don’t really know your

customers as well as you think you do

(usually)…

Page 24: Putting the "User" back in User Experience (Dallas Techfest Edition)

#2 If you’re launching twelve

months from now, and are not involving

your customer, that’s a big gamble…

Page 25: Putting the "User" back in User Experience (Dallas Techfest Edition)

Getting everything right the first time,

is hard.

Page 26: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://weandthecolor.com/back-to-the-future-poster-trilogy-by-phantom-city-creative/11727

Page 27: Putting the "User" back in User Experience (Dallas Techfest Edition)

2000

Page 28: Putting the "User" back in User Experience (Dallas Techfest Edition)

The Elements of User ExperienceA basic duality: The Web was originally conceived as a hypertextual information space;but the development of increasingly sophisticated front- and back-end technologies hasfostered its use as a remote software interface. This dual nature has led to much confusion,as user experience practitioners have attempted to adapt their terminology to cases beyondthe scope of its original application. The goal of this document is to define some of theseterms within their appropriate contexts, and to clarify the underlying relationships amongthese various elements.

Jesse James [email protected]

Visual Design: graphic treatment of interfaceelements (the "look" in "look-and-feel")

Information Architecture: structural designof the information space to facilitateintuitive access to content

Interaction Design: development ofapplication flows to facilitate user tasks,defining how the user interacts withsite functionality

Navigation Design: design of interfaceelements to facilitate the user's movementthrough the information architectureInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Functional Specifications: "feature set":detailed descriptions of functionality the sitemust include in order to meet user needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

Content Requirements: definition ofcontent elements required in the sitein order to meet user needs

Interface Design: as in traditional HCI:design of interface elements to facilitateuser interaction with functionalityInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Web as software interface Web as hypertext system

Visual Design: visual treatment of text,graphic page elements and navigationalcomponents

Concrete

Abstract

time

Conception

Completion

FunctionalSpecifications

ContentRequirements

InteractionDesign

InformationArchitecture

Visual Design

Information DesignInterface Design Navigation Design

Site ObjectivesUser Needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

This picture is incomplete: The model outlined here does not account for secondary considerations (such as those arising during technical or content development)that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within auser experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.

task-oriented information-oriented

30 March 2000

© 2000 Jesse James Garrett http://www.jjg.net/ia/

Page 29: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.smashingmagazine.com/2014/09/01/think-your-app-is-beautiful-not-without-user-experience-design/

Page 30: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Beauty is wasted when our products don’t address real user

needs in a usable manner”http://www.smashingmagazine.com/2014/09/01/think-your-app-is-beautiful-not-without-user-experience-design/

Page 31: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://t.co/vzaW4WSJil

Page 32: Putting the "User" back in User Experience (Dallas Techfest Edition)

We’re not just painters!

Page 33: Putting the "User" back in User Experience (Dallas Techfest Edition)

SO MUCH MORE

COMPLEX.

Page 34: Putting the "User" back in User Experience (Dallas Techfest Edition)

UX

Page 35: Putting the "User" back in User Experience (Dallas Techfest Edition)

User Experience

Page 36: Putting the "User" back in User Experience (Dallas Techfest Edition)

The Elements of User ExperienceA basic duality: The Web was originally conceived as a hypertextual information space;but the development of increasingly sophisticated front- and back-end technologies hasfostered its use as a remote software interface. This dual nature has led to much confusion,as user experience practitioners have attempted to adapt their terminology to cases beyondthe scope of its original application. The goal of this document is to define some of theseterms within their appropriate contexts, and to clarify the underlying relationships amongthese various elements.

Jesse James [email protected]

Visual Design: graphic treatment of interfaceelements (the "look" in "look-and-feel")

Information Architecture: structural designof the information space to facilitateintuitive access to content

Interaction Design: development ofapplication flows to facilitate user tasks,defining how the user interacts withsite functionality

Navigation Design: design of interfaceelements to facilitate the user's movementthrough the information architectureInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Functional Specifications: "feature set":detailed descriptions of functionality the sitemust include in order to meet user needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

Content Requirements: definition ofcontent elements required in the sitein order to meet user needs

Interface Design: as in traditional HCI:design of interface elements to facilitateuser interaction with functionalityInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Web as software interface Web as hypertext system

Visual Design: visual treatment of text,graphic page elements and navigationalcomponents

Concrete

Abstract

time

Conception

Completion

FunctionalSpecifications

ContentRequirements

InteractionDesign

InformationArchitecture

Visual Design

Information DesignInterface Design Navigation Design

Site ObjectivesUser Needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

This picture is incomplete: The model outlined here does not account for secondary considerations (such as those arising during technical or content development)that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within auser experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.

task-oriented information-oriented

30 March 2000

© 2000 Jesse James Garrett http://www.jjg.net/ia/

Page 37: Putting the "User" back in User Experience (Dallas Techfest Edition)

2010

Page 38: Putting the "User" back in User Experience (Dallas Techfest Edition)

We own so much more than the website!

Page 39: Putting the "User" back in User Experience (Dallas Techfest Edition)

SERVICE DESIGN

Page 40: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 41: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 42: Putting the "User" back in User Experience (Dallas Techfest Edition)

#$%!

Page 43: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 44: Putting the "User" back in User Experience (Dallas Techfest Edition)

WOOT

Page 45: Putting the "User" back in User Experience (Dallas Techfest Edition)

Systems Thinking Ecosystems

Service Design

Page 46: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 47: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 48: Putting the "User" back in User Experience (Dallas Techfest Edition)

“SEAT AT THE

TABLE”

Page 49: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 50: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.forbes.com/sites/anthonykosner/2013/11/23/how-design-and-user-experience-translates-to-the-bottom-line/

Page 51: Putting the "User" back in User Experience (Dallas Techfest Edition)

We’ve #WON

Page 52: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://blogs.hbr.org/2014/04/design-can-drive-exceptional-returns-for-shareholders/

Page 53: Putting the "User" back in User Experience (Dallas Techfest Edition)

It’s not that easy.

Page 54: Putting the "User" back in User Experience (Dallas Techfest Edition)

There are still 100s of companies that make

revenue off software in the $100s of millions that don’t

have a user experience team.

Page 55: Putting the "User" back in User Experience (Dallas Techfest Edition)

“The problem from a user experience perspective is that enterprise systems are generally procured and

implemented with the focus purely on solving problems for the business with little attention paid to who the

users are and how they want to work.”

http://www.foolproof.co.uk/thinking/the-user-experience-of-enterprise-technology/

Page 56: Putting the "User" back in User Experience (Dallas Techfest Edition)

Solving Problems by Automating Solutions

Page 57: Putting the "User" back in User Experience (Dallas Techfest Edition)

Is it harder than doing it manually?

(I didn’t say “is it easy?”)

https://www.flickr.com/photos/33989236@N00/4214027902/

Page 58: Putting the "User" back in User Experience (Dallas Techfest Edition)

software users have raised the

their expectations have changed.

bar

Page 59: Putting the "User" back in User Experience (Dallas Techfest Edition)

Sunday. Monday.

Page 60: Putting the "User" back in User Experience (Dallas Techfest Edition)

“We’re focusing on User Experience”

Page 61: Putting the "User" back in User Experience (Dallas Techfest Edition)

I hired a UX guy! (or gal)

“We’re focusing on User Experience”

Page 62: Putting the "User" back in User Experience (Dallas Techfest Edition)

# of developers

# of UX designers

Page 63: Putting the "User" back in User Experience (Dallas Techfest Edition)

# of developers

# of UX designers

Page 64: Putting the "User" back in User Experience (Dallas Techfest Edition)

UX Magic

Page 65: Putting the "User" back in User Experience (Dallas Techfest Edition)

UX is complex. UX is everywhere.

UX is business.

Page 66: Putting the "User" back in User Experience (Dallas Techfest Edition)

2015

Page 67: Putting the "User" back in User Experience (Dallas Techfest Edition)

forgetting…

Page 68: Putting the "User" back in User Experience (Dallas Techfest Edition)

UX is complex. UX is everywhere.

UX is business. UX is for people.

Page 69: Putting the "User" back in User Experience (Dallas Techfest Edition)

“users”

Page 70: Putting the "User" back in User Experience (Dallas Techfest Edition)

“users”“people”

Page 71: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 72: Putting the "User" back in User Experience (Dallas Techfest Edition)

The Elements of User ExperienceA basic duality: The Web was originally conceived as a hypertextual information space;but the development of increasingly sophisticated front- and back-end technologies hasfostered its use as a remote software interface. This dual nature has led to much confusion,as user experience practitioners have attempted to adapt their terminology to cases beyondthe scope of its original application. The goal of this document is to define some of theseterms within their appropriate contexts, and to clarify the underlying relationships amongthese various elements.

Jesse James [email protected]

Visual Design: graphic treatment of interfaceelements (the "look" in "look-and-feel")

Information Architecture: structural designof the information space to facilitateintuitive access to content

Interaction Design: development ofapplication flows to facilitate user tasks,defining how the user interacts withsite functionality

Navigation Design: design of interfaceelements to facilitate the user's movementthrough the information architectureInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Functional Specifications: "feature set":detailed descriptions of functionality the sitemust include in order to meet user needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

Content Requirements: definition ofcontent elements required in the sitein order to meet user needs

Interface Design: as in traditional HCI:design of interface elements to facilitateuser interaction with functionalityInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Web as software interface Web as hypertext system

Visual Design: visual treatment of text,graphic page elements and navigationalcomponents

Concrete

Abstract

time

Conception

Completion

FunctionalSpecifications

ContentRequirements

InteractionDesign

InformationArchitecture

Visual Design

Information DesignInterface Design Navigation Design

Site ObjectivesUser Needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

This picture is incomplete: The model outlined here does not account for secondary considerations (such as those arising during technical or content development)that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within auser experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.

task-oriented information-oriented

30 March 2000

© 2000 Jesse James Garrett http://www.jjg.net/ia/

Page 73: Putting the "User" back in User Experience (Dallas Techfest Edition)

“user needs”

Page 74: Putting the "User" back in User Experience (Dallas Techfest Edition)

The Elements of User ExperienceA basic duality: The Web was originally conceived as a hypertextual information space;but the development of increasingly sophisticated front- and back-end technologies hasfostered its use as a remote software interface. This dual nature has led to much confusion,as user experience practitioners have attempted to adapt their terminology to cases beyondthe scope of its original application. The goal of this document is to define some of theseterms within their appropriate contexts, and to clarify the underlying relationships amongthese various elements.

Jesse James [email protected]

Visual Design: graphic treatment of interfaceelements (the "look" in "look-and-feel")

Information Architecture: structural designof the information space to facilitateintuitive access to content

Interaction Design: development ofapplication flows to facilitate user tasks,defining how the user interacts withsite functionality

Navigation Design: design of interfaceelements to facilitate the user's movementthrough the information architectureInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Functional Specifications: "feature set":detailed descriptions of functionality the sitemust include in order to meet user needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

Content Requirements: definition ofcontent elements required in the sitein order to meet user needs

Interface Design: as in traditional HCI:design of interface elements to facilitateuser interaction with functionalityInformation Design: in the Tuftean sense:designing the presentation of informationto facilitate understanding

Web as software interface Web as hypertext system

Visual Design: visual treatment of text,graphic page elements and navigationalcomponents

Concrete

Abstract

time

Conception

Completion

FunctionalSpecifications

ContentRequirements

InteractionDesign

InformationArchitecture

Visual Design

Information DesignInterface Design Navigation Design

Site ObjectivesUser Needs

User Needs: externally derived goalsfor the site; identified through user research,ethno/techno/psychographics, etc.Site Objectives: business, creative, or otherinternally derived goals for the site

This picture is incomplete: The model outlined here does not account for secondary considerations (such as those arising during technical or content development)that may influence decisions during user experience development. Also, this model does not describe a development process, nor does it define roles within auser experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.

task-oriented information-oriented

30 March 2000

© 2000 Jesse James Garrett http://www.jjg.net/ia/

Page 75: Putting the "User" back in User Experience (Dallas Techfest Edition)

What UX isn’thttps://medium.com/@jamieskella/what-ux-isnt-dee0436a194d

Page 76: Putting the "User" back in User Experience (Dallas Techfest Edition)

Designing for yourself is an easy trap to fall into. Even when wielding taste and best practice acknowledgement, doing so is a sure fire way to get it wrong for your target demographic.

… good UX is the result of understanding the customer, seizing technological opportunity, and pursuing simplicity.

Making informed and intelligent design decisions means the inclusion of user research and usability testing.

Good design requires a deep understanding of your target demographic, only attained through quality data, being a result of unbiased research and testing.

UX is the consideration of the many aspects of a user’s interactions with a product or service. It’s concern for the relationship between those interactions, which ultimately define a user’s perception of a brand as a whole.

…acutely empathize with the audience they’re designing for.

Page 77: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.nngroup.com/articles/ux-without-user-research/

Page 78: Putting the "User" back in User Experience (Dallas Techfest Edition)

User experience cannot exist without users. Creating user interfaces involves intricate and complex decisions. User research is a tool that can help you achieve your goals.

Even the most well thought out designs are assumptions until they are tested by real users. Different types of research can answer different types of questions. Know the tools and apply them accordingly. Leaving the user out is not an option.

UX - U = X

Page 79: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://blogs.wsj.com/accelerators/2014/02/19/braden-kowitz-why-you-should-listen-to-the-customer/

Page 80: Putting the "User" back in User Experience (Dallas Techfest Edition)

Investing in user research is just about the only way to consistently generate a rich stream of data about customer needs and behaviors. As a designer, I can’t live without it. And as data about customers flows through your team, it informs product managers, engineers, and just about everyone else. It forms the foundation of intuitive designs, indispensable products, and successful companies. So what are you waiting for? Go listen to your customers!

Page 81: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.jeffgothelf.com/blog/agile-doesnt-have-a-brain/

Page 82: Putting the "User" back in User Experience (Dallas Techfest Edition)

“…methodologies like Scrum — have no mechanism for determining if they’re building the right feature and whether that implementation is designed well and/or

worth improving.”

http://www.jeffgothelf.com/blog/agile-doesnt-have-a-brain/

Page 83: Putting the "User" back in User Experience (Dallas Techfest Edition)

Let’s talk about Listening to customers

Page 84: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Hey, I want you to go and understand our

user’s needs.”

Page 85: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I’ve read stories about our users online”

Marketing Data / Segmentation / Surveys

Page 86: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I’ve watched some videos about our users”

Focus Groups / Past Usability Studies / Marketing Research

Page 87: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I’ve seen our users in the lab”

Usability Testing / Concept Testing / Customer Councils

Page 88: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I went to our users and observed them”

Contextual Inquires / Field Studies / Interviews

Page 89: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I understand best practices, and I’m a

student of psychology"I have experience / I’m great at what I do

Page 90: Putting the "User" back in User Experience (Dallas Techfest Edition)

aka Shut up, I’m a design genius.

Page 91: Putting the "User" back in User Experience (Dallas Techfest Edition)

Q. Which one accurately answers the question:

Page 92: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Hey, I want you to go and understand our

user’s needs.”

Page 93: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I want to know them so well, the system we

design “just works” for them.”

Page 94: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 95: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 96: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 97: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 98: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 99: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 100: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 101: Putting the "User" back in User Experience (Dallas Techfest Edition)

User Experience

Page 102: Putting the "User" back in User Experience (Dallas Techfest Edition)

User Experience

Page 103: Putting the "User" back in User Experience (Dallas Techfest Edition)

Web Design vs. User Experience

Page 104: Putting the "User" back in User Experience (Dallas Techfest Edition)

User Experience

Page 105: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://money.cnn.com/pf/best-jobs/2012/snapshots/43.html

“Top Job”

Page 106: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://money.cnn.com/pf/best-jobs/2012/snapshots/43.html

“Top Job”

Page 107: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.uxutd.com/

Page 108: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 109: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Give me three skills a ux designer needs today and

for the future”

Page 110: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 111: Putting the "User" back in User Experience (Dallas Techfest Edition)

HTML

PHOTOSHOPILLUSTRATOR

Page 112: Putting the "User" back in User Experience (Dallas Techfest Edition)

“empathy”

Page 113: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 114: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://poetpainter.com/

Page 115: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://poetpainter.com/

“EASY”

HARD

Page 116: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://poetpainter.com/

Page 117: Putting the "User" back in User Experience (Dallas Techfest Edition)

“personal significance” “works like I think”

Page 118: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Hey, I want you to go and understand our user’s needs, wants,

and desires.”

Page 119: Putting the "User" back in User Experience (Dallas Techfest Edition)

You get there by understanding

your users.

Page 120: Putting the "User" back in User Experience (Dallas Techfest Edition)

5 WAYS Getting to know your

users helps YOU.

Page 121: Putting the "User" back in User Experience (Dallas Techfest Edition)

Learn the unexpected

Page 122: Putting the "User" back in User Experience (Dallas Techfest Edition)

https://twitter.com/jmspool/statuses/421414065496289280

Page 123: Putting the "User" back in User Experience (Dallas Techfest Edition)

1.

Business needs data to backup decisions.

Page 124: Putting the "User" back in User Experience (Dallas Techfest Edition)

2.

Mind-blowing, astonishing, insights.

Page 125: Putting the "User" back in User Experience (Dallas Techfest Edition)

3.

Something in-between…

Page 126: Putting the "User" back in User Experience (Dallas Techfest Edition)

Observations will speak volumes for

your users.

Page 127: Putting the "User" back in User Experience (Dallas Techfest Edition)

User Quotes

Page 128: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I like the idea, but I’d never use this.”

Page 129: Putting the "User" back in User Experience (Dallas Techfest Edition)

“What I really need is a way to save this for later.”

Page 130: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I have no idea how to use this, so I just skip

that whole step”

Page 131: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I usually just print it out and file it away.”

Page 132: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I use this because it makes me feel like I’m mastering something”

Page 133: Putting the "User" back in User Experience (Dallas Techfest Edition)

Affinity Diagramming

Page 134: Putting the "User" back in User Experience (Dallas Techfest Edition)

Solving the right problems

Page 135: Putting the "User" back in User Experience (Dallas Techfest Edition)

“I know”

Product Owner

CEO

Designer

CMO

Developer

Page 136: Putting the "User" back in User Experience (Dallas Techfest Edition)

Institutional Knowledge

Page 137: Putting the "User" back in User Experience (Dallas Techfest Edition)

The 8 Monkeys

http://speakingofresearch.com/category/news/campus-activism/

Page 138: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.nbcnews.com/feature/making-a-difference/striking-out-als-ice-bucket-challenge-brings-flood-donations-n177896

Page 139: Putting the "User" back in User Experience (Dallas Techfest Edition)

The 8 Monkeys

http://speakingofresearch.com/category/news/campus-activism/

Page 140: Putting the "User" back in User Experience (Dallas Techfest Edition)

Institutional Knowledge

Page 141: Putting the "User" back in User Experience (Dallas Techfest Edition)

Go observe, talk to, and interact with your users!

Get first hand experience of your user’s problems!

Page 142: Putting the "User" back in User Experience (Dallas Techfest Edition)

Show you care

Page 143: Putting the "User" back in User Experience (Dallas Techfest Edition)

#1 reaction when observing users of

business-to-business software?

Page 144: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Wow, you care about us? I thought we were

abandoned to the depths of bad software!”

Page 145: Putting the "User" back in User Experience (Dallas Techfest Edition)

+ Signed longer contracts + Bought new software + Excited user base

Page 146: Putting the "User" back in User Experience (Dallas Techfest Edition)

#1 reaction when observing users.

Page 147: Putting the "User" back in User Experience (Dallas Techfest Edition)

Hugs.

Page 148: Putting the "User" back in User Experience (Dallas Techfest Edition)

You’re the expert

Page 149: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Hey, who do I go to, I have a question about what we

should do here?”

Page 150: Putting the "User" back in User Experience (Dallas Techfest Edition)

Amou

nt y

ou k

now

abo

ut y

our u

sers

Number of questions you’ll get about the direction of your product

Page 151: Putting the "User" back in User Experience (Dallas Techfest Edition)

“SEAT AT THE

TABLE”

Page 152: Putting the "User" back in User Experience (Dallas Techfest Edition)

+ You know what will set you apart + Quotes are Business Ammo + You understand the problems + You’re users love you + You’re now the expert

Page 153: Putting the "User" back in User Experience (Dallas Techfest Edition)

Design Research (or User Research)

Page 154: Putting the "User" back in User Experience (Dallas Techfest Edition)

https://twitter.com/jmspool/statuses/409433591643246592

Page 155: Putting the "User" back in User Experience (Dallas Techfest Edition)

https://twitter.com/userfocus/status/519437111540584449

Page 156: Putting the "User" back in User Experience (Dallas Techfest Edition)

Usability Testing vs. User Research

Page 157: Putting the "User" back in User Experience (Dallas Techfest Edition)

Today

6 months

3 years

Page 158: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.fastcodesign.com/3031942/google-ventures-on-8-shortcuts-for-better-faster-design-research

Page 159: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.slideshare.net/jeremy/failing-fast-learning-along-the-way-big-design-2013

Page 160: Putting the "User" back in User Experience (Dallas Techfest Edition)

8 Design Research practices to kick start your

user knowledge!

Page 161: Putting the "User" back in User Experience (Dallas Techfest Edition)

Understand Design Refine

Contextual Inquiries

Persona Development

Concept Validation

Workflow Modeling

Affinity Diagramming

KANO Feature Prioritization

Participatory Design

Card Sorting

404 testing

User Journals / Diaries

Page 162: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://michaelvhurley.com/2013/01/04/my-worthless-degree/

Page 163: Putting the "User" back in User Experience (Dallas Techfest Edition)

Psychology, cognitive science, etc…

Page 164: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.shmula.com/jeff-bezos-5-why-exercise-root-cause-analysis-cause-and-effect-ishikawa-lean-thinking-six-sigma/987/

Why did the associate damage his thumb?

Because his thumb got caught in the conveyor.

Why did his thumb get caught in the conveyor?

Because he was chasing his bag, which was on a running conveyor.

Why did he chase his bag?

Because he placed his bag on the conveyor, but it then turned-on by surprise

Why was his bag on the conveyor?

Because he used the conveyor as a table

So, the likely root cause of the associate’s damaged thumb is that he simply needed a table, there wasn’t one around, so he used a conveyor as a table. To eliminate further safety incidences, we need to provide tables at the appropriate stations or provide portable, light tables for the associates to use and also update and a greater focus on safety training. Also, look into preventative maintenance standard work.

Page 165: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.uxmatters.com/mt/archives/2009/07/laddering-a-research-interview-technique-for-uncovering-core-values.php

Page 166: Putting the "User" back in User Experience (Dallas Techfest Edition)

Contextual Inquiries

Page 167: Putting the "User" back in User Experience (Dallas Techfest Edition)

A contextual inquiry interview is usually structured as an approximately two-hour,

one-on-one interaction in which the researcher watches the user do their normal activities and discusses what they see with

the user.

http://en.wikipedia.org/wiki/Contextual_inquiry

Page 168: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 169: Putting the "User" back in User Experience (Dallas Techfest Edition)

Observing Users.

Page 170: Putting the "User" back in User Experience (Dallas Techfest Edition)

Persona Development

Page 171: Putting the "User" back in User Experience (Dallas Techfest Edition)

DavidCorporate Employee, 40 yrs old

Primary Persona

Health Conscious

“I workout a couple times a week, and want to make sure I’m as

healthy as I can be”

Number of doctor visits a year:

5

Years without major health issue:

8

About David:

Health Motivators:

Experience:

Goals:

Ideal State:

Technology Adoption:

David’s Edge:

Lorem ipsum dolor sit amet, consectetur

adipiscing elit. Praesent eu ligula est.

Pellentesque a dolor molestie, vestibulum

metus a, luctus dolor. Cras est dui, lobortis et

nisi quis, viverra vehicula purus. Vestibulum

ultrices ut eros a egestas. Phasellus egestas

ligula sit amet nulla vehicula egestas. Maecenas

interdum porta faucibus. Sed id mauris ac turpis

pretium pretium. Praesent euismod vitae sem

vitae tincidunt. Mauris interdum.

• Lorem ipsum dolor sit amet, consectetur

• adipiscing elit. Praesent eu ligula est.

• Pellentesque a dolor molestie, vestibulum

• metus a, luctus dolor. Cras est dui, lobortis et

• nisi quis, viverra vehicula purus. Vestibulum

• ]ultrices ut eros a egestas. Phasellus egestas

Lorem ipsum dolor sit amet, consectetur

adipiscing elit. Praesent eu ligula est.

Pellentesque a dolor molestie, vestibulum

metus a, luctus dolor.

Lorem ipsum dolor sit amet, consectetur

adipiscing elit. Praesent eu ligula est.

Pellentesque a dolor molestie, vestibulum

metus a, luctus dolor. Cras est dui, lobortis

et nisi quis, viverra vehicula purus.

Vestibulum ultrices ut eros a egestas.

Phasellus egestas ligula sit amet nulla

vehicula egestas. Maecenas interdum porta

faucibus. Sed id mauris ac turpis pretium

pretium. Praesent euismod vitae sem vitae

tincidunt. Mauris interdum.

Lorem ipsum dolor sit amet, consectetur

adipiscing elit. Praesent eu ligula est.

Pellentesque a dolor molestie, vestibulum

metus a, luctus dolor. Cras est dui, lobortis et

nisi quis, viverra vehicula purus. Vestibulum

ultrices ut eros a egestas. Phasellus egestas

ligula sit amet nulla vehicula egestas.

Maecenas interdum porta faucibus. Sed id

mauris ac turpis pretium pretium. Praesent

euismod.

55%90% 100%

Page 172: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://blog.mailchimp.com/new-mailchimp-user-persona-research/

Page 173: Putting the "User" back in User Experience (Dallas Techfest Edition)

As a user…Jane needs to…

Page 174: Putting the "User" back in User Experience (Dallas Techfest Edition)

Concept Validation

Page 175: Putting the "User" back in User Experience (Dallas Techfest Edition)

User-centered design can be characterized as a multi-stage problem solving process that not only requires designers to analyze and foresee how users are likely to use a product, but also to test the validity of their assumptions with regard to user behavior in real world tests with actual users. Such testing is necessary as it is often very difficult for the designers of a product to understand intuitively what a first-time user of their design experiences, and what each user's learning curve may look like.

http://en.wikipedia.org/wiki/User-centered_design

Page 176: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 177: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Starbucks Testing”

Page 178: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 179: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 180: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 181: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 182: Putting the "User" back in User Experience (Dallas Techfest Edition)

x

x

Page 183: Putting the "User" back in User Experience (Dallas Techfest Edition)

Core team makes decisions

Done!

the core team

Page 184: Putting the "User" back in User Experience (Dallas Techfest Edition)

Affinity Diagramming

Page 185: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 186: Putting the "User" back in User Experience (Dallas Techfest Edition)

Participatory Design

Page 187: Putting the "User" back in User Experience (Dallas Techfest Edition)

“Participatory design aims to bring users into the design process by facilitating conversations through the creation and completion of a wide

range of activities.”

http://designmind.frogdesign.com/blog/bringing-users-into-your-process-through-participatory-design.html

Page 188: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.slideshare.net/frogdesign/bringing-users-into-your-process-through-participatory-design

Page 189: Putting the "User" back in User Experience (Dallas Techfest Edition)

Card Sorting

Page 190: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.optimalworkshop.com/treejack.htm

Page 191: Putting the "User" back in User Experience (Dallas Techfest Edition)

404 testing

Page 192: Putting the "User" back in User Experience (Dallas Techfest Edition)

Comics, fast!

Want comics delivered to your home, fast? Download our app!

www.ubercomics.com

Page 193: Putting the "User" back in User Experience (Dallas Techfest Edition)

The Wizard Of Oz Techniques For Social Prototyping – You don’t need to build everything at first. You can be the man behind the curtain. Krieger says him and Systrom tested an early version of a feature which would notify you when friends joined the service. Instead of building it out, they manually sent people notifications “like a human bot” saying ‘your friend has joined.’ It turned out not to be useful. “We wrote zero lines of Python, so we had zero lines to throw away.”

http://techcrunch.com/2012/11/30/instagram-co-founder-mike-kriegers-8-principles-for-building-products-people-want/

- Mike Krieger, Instagram’s founder

Page 194: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://jeremyjohnsononline.com/2012/12/19/answering-the-question-would-they-use-it-before-you-build-it/

Page 195: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 196: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.leemunroe.com/lean-product-development-validate-feature-ideas/

Page 197: Putting the "User" back in User Experience (Dallas Techfest Edition)

It was an MVP (Minimal Viable Product). I skipped a bunch of features I figured I would implement later. First I wanted to see if people would use it and how they would use it.

Implementing user accounts (in Rails) would take me 2 weekends of work; registration, accounts, saving lists, removing lists, tracking, designing screens, edge cases etc.

I didn’t want to spend the time if it turned out no one signed up so I ran an experiment.

I dropped in a link on the top of the page that said “Sign up to save multiple lists.” and tracked the number of clicks it got with Mixpanel.

(...)

http://www.leemunroe.com/lean-product-development-validate-feature-ideas/

Page 198: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.leemunroe.com/lean-product-development-validate-feature-ideas/

Page 199: Putting the "User" back in User Experience (Dallas Techfest Edition)

User Journals / Diaries

Page 200: Putting the "User" back in User Experience (Dallas Techfest Edition)

“In interviews, it can be difficult to get a sense of behavior over time because you have to rely on the

participant’s memory of past activities or circumstances, and artifacts can only do so much to

prompt that.”

http://www.uxbooth.com/articles/jumpstart-design-research-with-a-diary-study/

Page 201: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.slideshare.net/jaremfan/the-goodness-of-diary-studies

Page 202: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.trackyourhappiness.org/

Page 203: Putting the "User" back in User Experience (Dallas Techfest Edition)

“46.9 percent of the time the responders said their minds were wandering when the iPhone

rang to query their thoughts.”

http://blogs.discovermagazine.com/80beats/2010/11/11/iphone-users-report-that-daydreams-make-them-sad/

Page 204: Putting the "User" back in User Experience (Dallas Techfest Edition)

8 Design Research practices to kick start your

user knowledge!

Page 205: Putting the "User" back in User Experience (Dallas Techfest Edition)

Rockstars!

Page 206: Putting the "User" back in User Experience (Dallas Techfest Edition)

Tomer Sharon https://plus.google.com/+TomerSharon/about

User Experience Researcher at Google Search

Page 207: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://rosenfeldmedia.com/books/lean-user-research/

Page 208: Putting the "User" back in User Experience (Dallas Techfest Edition)

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

Google I/O 2014 - Perfectly executing the wrong plan

Page 209: Putting the "User" back in User Experience (Dallas Techfest Edition)

Research +

Lean Startup

Page 210: Putting the "User" back in User Experience (Dallas Techfest Edition)

Leisa Reichelthttp://www.disambiguity.com/

Head of User Research at the Government Digital Service in the Cabinet Office

Page 211: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://www.disambiguity.com/help-joy-help-you/

Page 212: Putting the "User" back in User Experience (Dallas Techfest Edition)

https://twitter.com/leisa

Page 213: Putting the "User" back in User Experience (Dallas Techfest Edition)

https://userresearch.blog.gov.uk/

Page 214: Putting the "User" back in User Experience (Dallas Techfest Edition)

Big Government +

Empathy

Page 215: Putting the "User" back in User Experience (Dallas Techfest Edition)

http://inside.mygov.scot/2014/09/09/five-principles-user-research/

1. Research with project teams, not for them 2. Research with users, as opposed to

carrying out research on users 3. Usability testing should be (as) light, fast

and frequent (as possible) 4. Research practices and contexts, as well

as use 5. Research needs to be visible and shared

quickly

Page 216: Putting the "User" back in User Experience (Dallas Techfest Edition)

Peter EckertCo-Founder & CXOhttp://projekt202.com/

Page 217: Putting the "User" back in User Experience (Dallas Techfest Edition)

10+ Years

Page 218: Putting the "User" back in User Experience (Dallas Techfest Edition)

Enterprise / Complex Software

+ Design Research

Page 219: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 220: Putting the "User" back in User Experience (Dallas Techfest Edition)
Page 221: Putting the "User" back in User Experience (Dallas Techfest Edition)

Last…

Page 222: Putting the "User" back in User Experience (Dallas Techfest Edition)

https://www.behance.net/gallery/PRESENTATION-User-Research/4890075

Page 223: Putting the "User" back in User Experience (Dallas Techfest Edition)

https://www.behance.net/gallery/PRESENTATION-User-Research/4890075

Page 224: Putting the "User" back in User Experience (Dallas Techfest Edition)

@jeremyjohnson

Thanks!

Page 225: Putting the "User" back in User Experience (Dallas Techfest Edition)

“If you’re not involving your users, you’re not a User Experience Designer” #techfest #designresearch via: @jeremyjohnson

Who needs users! I’m a design genius! @jeremyjohnson doesn’t know what he’s talking about #iknowbest #forgetusers #techfest

Page 226: Putting the "User" back in User Experience (Dallas Techfest Edition)

Thanks!

Questions?

@jeremyjohnson

Jeremy Johnson Director of User Experience @

214-228-2894

.com

[email protected]@projekt202