186
back in User Experience Putting the User @jeremyjohnson

Putting the "User" back in User Experience

Embed Size (px)

DESCRIPTION

If you ask a 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 products - 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

back in User ExperiencePutting the User

@jeremyjohnson

Page 2: Putting the "User" back in User Experience

@jeremyjohnson

(yes, we’re hiring)

Page 3: Putting the "User" back in User Experience

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

Page 4: Putting the "User" back in User Experience

WORKED FOR

Page 5: Putting the "User" back in User Experience

WORKED WITH

Page 6: Putting the "User" back in User Experience
Page 7: Putting the "User" back in User Experience

Contextual InquiriesObserve & document user in context/environment

Participatory DesignCo-creation explorations with users.

User Journals / DiariesUsers document their experiences over time.

Card SortExplore users’ mental models for content and labeling.

Discovery Ideation

Revealing Reality Focused Innovation

Only a subset of these activities will be appropriate for any given project.

Engagement Readiness Analysis Foundational Analysis

Stakeholder InterviewsUnderstand staheholders’ business goals & strategy.

Scenario-based System WalkthroughsDemo of existing solution.

Application / IA MapDocument the structure of the existing solution.

Strategic Ideation

Concepts Validation with UsersValidate design prototypes through user feedback.

KANO Feature PrioritizationPrioritize features with users through KANO analysis.

Qualitative & Quantitative Data SynthesisAnalyze validation data..

Design Research

Qualitative Observation

Affinity DiagrammingConstruct themes from qualitative data.

Persona DevelopmentCreate customer types based on behaviors and values.

Current Journey MapVisualize the user’s perspective of the current experience.

Research PlanDesign activities to meet research goals.

Technical Organization Capability AnalysisExisting skills and toolsets.

Solution Architecture AssessmentExisting application architecture.

Enterprise Architecture Capability AssessmentExisting enterprise infrastructure.

Content InventoryCatalog the content of the website.

Heuristic EvaluationIdentify initial breakdowns and opportunities.

Competitive AnalysisEvaluate competitors and comparables on specific axes.

Client Data AnalysisMarket research, website feedback, corporate strategy, etc.

Brand AnalysisEvaluate the state of the brand.

Metrics EvaluationEstablish quantitative baseline of engagement & conversion data.

Technology Digital Marketing

User Workflow ModelingVisually document workflows & work systems.

SurveysSolicit structured feedback from users.

Quantitative

Quantitative Data VisualizationPresent data visually.

Conceptual User Scenari-osExplanation TBD.

Conceptual User ScenariosWrite high level narratives of an ideal future flow.

StoryboardsIllustrate graphical representa-tions of scenarios.

Concepts: Paper / Interactive / VideoDevelop concepts for testing.with users.

Experience Strategy

Opportunities Prioritization MatrixPrioritize in three dimensions, including user experience impact.

Consolidated User States DiagramAbstracted from individual user workflows.

Future Journey MapVisualize the user’s future, improved experience.

Design PrinciplesSummarize the vision for the product/service in statements to guide the design.

Product / Experience RoadmapPlan how great UX can be achieved through the design.

Experience Success MetricsAgree on business metrics for a successful user experience.

Elaboration

Refined, Validated ConceptsRefine the validated prototype based on findings.

Analysis & Synthesis

Deep Dive WorkshopsImmerse stakeholders in data and brainstorm opportunities.

Opportunities Generation & EvaluationOpportunities & prototype choice.

Marketing OpportunitiesStrategic planning of owned, earned, & paid online tactics.

Beyond Conversion Optimization

Consolidated Workflow DiagramAggregate individual user workflows into one diagram.

Content Creation Process FlowDesign the content creation processes for the organization.

Content ArchitectureVisualize all the content created, including creators and locations.

Digital Marketing CreativeConcepts to support search, display, social media, landing.

Content Governance PlanCollaborative design how created content will be governed.

Page 8: Putting the "User" back in User Experience

Uncover user needs, Design great solutions,

and build out solutions to launch.

Page 9: Putting the "User" back in User Experience

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

Page 10: Putting the "User" back in User Experience

2000

Page 11: Putting the "User" back in User Experience

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 12: Putting the "User" back in User Experience

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

Page 13: Putting the "User" back in User Experience

“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 14: Putting the "User" back in User Experience

http://t.co/vzaW4WSJil

Page 15: Putting the "User" back in User Experience

We’re not just painters!

Page 16: Putting the "User" back in User Experience

SO MUCH MORE

COMPLEX.

Page 17: Putting the "User" back in User Experience

UX

Page 18: Putting the "User" back in User Experience

User Experience

Page 19: Putting the "User" back in User Experience

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 20: Putting the "User" back in User Experience

2010

Page 21: Putting the "User" back in User Experience

We own so much more than the website!

Page 22: Putting the "User" back in User Experience

SERVICE DESIGN

Page 23: Putting the "User" back in User Experience
Page 24: Putting the "User" back in User Experience
Page 25: Putting the "User" back in User Experience
Page 26: Putting the "User" back in User Experience

“SEAT AT THE

TABLE”

Page 27: Putting the "User" back in User Experience
Page 28: Putting the "User" back in User Experience

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

Page 29: Putting the "User" back in User Experience

We’ve #WON

Page 30: Putting the "User" back in User Experience

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

Page 31: Putting the "User" back in User Experience

It’s not that easy.

Page 32: Putting the "User" back in User Experience

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 33: Putting the "User" back in User Experience

“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 34: Putting the "User" back in User Experience

Solving Problems by Automating Solutions

Page 35: Putting the "User" back in User Experience

Is it harder than doing it manually?

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

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

Page 36: Putting the "User" back in User Experience

software users have raised the

their expectations have changed.

bar

Page 37: Putting the "User" back in User Experience

Sunday. Monday.

Page 38: Putting the "User" back in User Experience

“We’re focusing on User Experience”

Page 39: Putting the "User" back in User Experience

I hired a UX guy! (or gal)

“We’re focusing on User Experience”

Page 40: Putting the "User" back in User Experience

# of developers

# of UX designers

Page 41: Putting the "User" back in User Experience

# of developers

# of UX designers

Page 42: Putting the "User" back in User Experience

UX Magic

Page 43: Putting the "User" back in User Experience

UX is complex. UX is everywhere.

UX is business.

Page 44: Putting the "User" back in User Experience

2015

Page 45: Putting the "User" back in User Experience

forgetting…

Page 46: Putting the "User" back in User Experience

UX is complex. UX is everywhere.

UX is business. UX is for people.

Page 47: Putting the "User" back in User Experience

“users”

Page 48: Putting the "User" back in User Experience

“users”“people”

Page 49: Putting the "User" back in User Experience
Page 50: Putting the "User" back in User Experience

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 51: Putting the "User" back in User Experience

“user needs”

Page 52: Putting the "User" back in User Experience

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 53: Putting the "User" back in User Experience

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

Page 54: Putting the "User" back in User Experience

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 55: Putting the "User" back in User Experience

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

Page 56: Putting the "User" back in User Experience

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 57: Putting the "User" back in User Experience

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

Page 58: Putting the "User" back in User Experience

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 59: Putting the "User" back in User Experience

Let’s talk about Listening to customers

Page 60: Putting the "User" back in User Experience

“Hey, I want you to go and understand our

user’s needs.”

Page 61: Putting the "User" back in User Experience

“I’ve read stories about our users online”

Marketing Data / Segmentation / Surveys

Page 62: Putting the "User" back in User Experience

“I’ve watched some videos about our users”

Focus Groups / Past Usability Studies / Marketing Research

Page 63: Putting the "User" back in User Experience

“I’ve seen our users in the lab”

Usability Testing / Concept Testing / Customer Councils

Page 64: Putting the "User" back in User Experience

“I went to our users and observed them”

Contextual Inquires / Field Studies / Interviews

Page 65: Putting the "User" back in User Experience

“I understand best practices, and I’m a

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

Page 66: Putting the "User" back in User Experience

aka Shut up, I’m a design genius.

Page 67: Putting the "User" back in User Experience

Q. Which one accurately answers the question:

Page 68: Putting the "User" back in User Experience

“Hey, I want you to go and understand our

user’s needs.”

Page 69: Putting the "User" back in User Experience

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

design “just works” for them.”

Page 70: Putting the "User" back in User Experience
Page 71: Putting the "User" back in User Experience
Page 72: Putting the "User" back in User Experience
Page 73: Putting the "User" back in User Experience
Page 74: Putting the "User" back in User Experience
Page 75: Putting the "User" back in User Experience
Page 76: Putting the "User" back in User Experience
Page 77: Putting the "User" back in User Experience

User Experience

Page 78: Putting the "User" back in User Experience

User Experience

Page 79: Putting the "User" back in User Experience

Web Design vs. User Experience

Page 80: Putting the "User" back in User Experience

User Experience

Page 81: Putting the "User" back in User Experience

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

“Top Job”

Page 82: Putting the "User" back in User Experience

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

“Top Job”

Page 83: Putting the "User" back in User Experience

http://www.uxutd.com/

Page 84: Putting the "User" back in User Experience
Page 85: Putting the "User" back in User Experience

“Give me three skills a ux designer needs today and

for the future”

Page 86: Putting the "User" back in User Experience
Page 87: Putting the "User" back in User Experience

HTML

PHOTOSHOPILLUSTRATOR

Page 88: Putting the "User" back in User Experience

empathy

Page 89: Putting the "User" back in User Experience
Page 90: Putting the "User" back in User Experience

http://poetpainter.com/

Page 91: Putting the "User" back in User Experience

http://poetpainter.com/

“EASY”

HARD

Page 92: Putting the "User" back in User Experience

http://poetpainter.com/

Page 93: Putting the "User" back in User Experience

“personal significance” “works like I think”

Page 94: Putting the "User" back in User Experience

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

and desires.”

Page 95: Putting the "User" back in User Experience

You get there by understanding

your users.

Page 96: Putting the "User" back in User Experience

5 WAYS Getting to know your

users helps YOU.

Page 97: Putting the "User" back in User Experience

Learn the unexpected

Page 98: Putting the "User" back in User Experience

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

Page 99: Putting the "User" back in User Experience

1.

Business needs data to backup decisions.

Page 100: Putting the "User" back in User Experience

2.

Mind-blowing, astonishing, insights.

Page 101: Putting the "User" back in User Experience

3.

Something in-between…

Page 102: Putting the "User" back in User Experience

Observations will speak volumes for

your users.

Page 103: Putting the "User" back in User Experience

User Quotes

Page 104: Putting the "User" back in User Experience

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

Page 105: Putting the "User" back in User Experience

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

Page 106: Putting the "User" back in User Experience

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

that whole step”

Page 107: Putting the "User" back in User Experience

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

Page 108: Putting the "User" back in User Experience

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

Page 109: Putting the "User" back in User Experience

Affinity Diagramming

Page 110: Putting the "User" back in User Experience

Solving the right problems

Page 111: Putting the "User" back in User Experience

“I know”

Product Owner

CEO

Designer

CMO

Developer

Page 112: Putting the "User" back in User Experience

Institutional Knowledge

Page 113: Putting the "User" back in User Experience

The 8 Monkeys

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

Page 114: Putting the "User" back in User Experience

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

Page 115: Putting the "User" back in User Experience

The 8 Monkeys

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

Page 116: Putting the "User" back in User Experience

Institutional Knowledge

Page 117: Putting the "User" back in User Experience

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

Get first hand experience of your user’s problems!

Page 118: Putting the "User" back in User Experience

Show you care

Page 119: Putting the "User" back in User Experience

#1 reaction when observing users of

business-to-business software?

Page 120: Putting the "User" back in User Experience

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

abandoned to the depths of bad software!”

Page 121: Putting the "User" back in User Experience

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

Page 122: Putting the "User" back in User Experience

#1 reaction when observing users.

Page 123: Putting the "User" back in User Experience

Hugs.

Page 124: Putting the "User" back in User Experience

You’re the expert

Page 125: Putting the "User" back in User Experience

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

should do here?”

Page 126: Putting the "User" back in User Experience

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 127: Putting the "User" back in User Experience

“SEAT AT THE

TABLE”

Page 128: Putting the "User" back in User Experience

+ 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 129: Putting the "User" back in User Experience

Design Research (or User Research)

Page 130: Putting the "User" back in User Experience

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

Page 131: Putting the "User" back in User Experience

Usability Testing vs. User Research

Page 132: Putting the "User" back in User Experience

Contextual InquiriesObserve & document user in context/environment

Participatory DesignCo-creation explorations with users.

User Journals / DiariesUsers document their experiences over time.

Card SortExplore users’ mental models for content and labeling.

Discovery Ideation Go to MarketReleaseDesign & DevelopmentPre-Discovery

Revealing Reality Building & EvolvingFocused Innovation

Only a subset of these activities will be appropriate for any given project.

Engagement Readiness Analysis Foundational Analysis

Innovation Training

Design Thinking WorkshopTeach the design thinking framework.

Stakeholder InterviewsUnderstand staheholders’ business goals & strategy.

Scenario-based System WalkthroughsDemo of existing solution.

Application / IA MapDocument the structure of the existing solution.

Strategic Ideation

Concepts Validation with UsersValidate design prototypes through user feedback.

KANO Feature PrioritizationPrioritize features with users through KANO analysis.

Qualitative & Quantitative Data SynthesisAnalyze validation data..

Align & Assess Workshop Assess readiness across 7 capabilites.

Design Research

Qualitative Observation

Affinity DiagrammingConstruct themes from qualitative data.

Persona DevelopmentCreate customer types based on behaviors and values.

Current Journey MapVisualize the user’s perspective of the current experience.

Research PlanDesign activities to meet research goals.

Technical Organization Capability AnalysisExisting skills and toolsets.

Solution Architecture AssessmentExisting application architecture.

Enterprise Architecture Capability AssessmentExisting enterprise infrastructure.

Content InventoryCatalog the content of the website.

Heuristic EvaluationIdentify initial breakdowns and opportunities.

Competitive AnalysisEvaluate competitors and comparables on specific axes.

Client Data AnalysisMarket research, website feedback, corporate strategy, etc.

Brand AnalysisEvaluate the state of the brand.

Metrics EvaluationEstablish quantitative baseline of engagement & conversion data.

Research UX Design Technology Digital Marketing

User Workflow ModelingVisually document workflows & work systems.

SurveysSolicit structured feedback from users.

Quantitative

Quantitative Data VisualizationPresent data visually.

Conceptual User Scenari-osExplanation TBD.

Conceptual User ScenariosWrite high level narratives of an ideal future flow.

StoryboardsIllustrate graphical representa-tions of scenarios.

Concepts: Paper / Interactive / VideoDevelop concepts for testing.with users.

Experience Strategy

Opportunities Prioritization MatrixPrioritize in three dimensions, including user experience impact.

Consolidated User States DiagramAbstracted from individual user workflows.

Future Journey MapVisualize the user’s future, improved experience.

Design PrinciplesSummarize the vision for the product/service in statements to guide the design.

Product / Experience RoadmapPlan how great UX can be achieved through the design.

Experience Success MetricsAgree on business metrics for a successful user experience.

Elaboration

Detailed User ScenariosWrite detailed narratives for user experience flows.

Workflow ConceptsDraw high-level wireframes for key workflows.

Application / Navigation Framework ConceptsCreate models for the framework of the application.

Digital Marketing Go LiveCampaign launch.

Ongoing User ResearchTargeted analysis of subsequent releases.

Periodic Strategy and Execution Review Assess progress towards goals.

Skills TransferEducate client development team.

Ideation / ValidationCreate testable concepts and validate them with users.

Qualitative ResearchInvestigate ongoing opportunities and concepts with users.

Unit TestingTest system units in isolation.

DevelopmentWrite code and tests to complete sprint tasks.

Requirements / User Stories DefinitionWrite user stories based on detailed user scenarios.

Look & Feel StudiesExplore different visual treatments and styles.

Application Map / Information Architecture Map the product from the users’ point of view.

Refined, Validated ConceptsRefine the validated prototype based on findings.

Zero Feature ReleaseDemonstrate CI, automated testing, core solution setup.

High Level Technical ArchitectureDescribe high level architecture, including packaged components.

PrototypesBuild paper or coded prototypes to validate interactions.

DeployRelease to production.

Sprint PlanningCommit to stories, break down tasks.

RetrospectiveRefine approach based on what was effective.

Sprint DemoDemo completed work to stakeholders.

Backlog GroomingReprioritize backlog, add new stories.

Identify new & emerging opportunitiesAnalyze research / validation results to yield new stories.

Launch

Analysis & Synthesis

Deep Dive WorkshopsImmerse stakeholders in data and brainstorm opportunities.

Opportunities Generation & EvaluationOpportunities & prototype choice.

Marketing OpportunitiesStrategic planning of owned, earned, & paid online tactics.

Campaign OptimizationTesting of creative, media, bids & landing experiences.

Campaign MeasurementIn-depth analysis of campaign results and trends.

Campaign RefinementIterative enhancement of campaign tactics.

Beyond Conversion Optimization

Digital Marketing SWOT AnalysisIdentify strengths, weaknesses, opportunities & threats.

Usability TestingEvaluate the product’s designs or code through user testing.

Continuous IntegrationContinuously build, test, deploy, and integration test the system.

Integration TestingTest subsystems and their integration.

Run Book CreationCreate & update artifacts for maintenance & monitoring.

Non-functional Requirements TestingTest performance & scalability.

QA TestingValidate completed stories against acceptance criteria.

Visual DesignApply visual designs to the wireframes and generate assets.

IXD / WireframingCreate high fidelity wireframes of the design.

Visual Design LibraryDetermine & document visual design patterns.

Interaction Design LibraryDetermine & document interaction patterns.

User Education & TrainingConduct training sessions, create help content.

Sprint Execution Campaign ExecutionDeploy

Continuous Refinement

Production-Ready Completed FeaturesBuilt and tested features.Consolidated Workflow

DiagramAggregate individual user workflows into one diagram.

Content Creation Process FlowDesign the content creation processes for the organization.

Content ArchitectureVisualize all the content created, including creators and locations.

Digital Marketing CreativeConcepts to support search, display, social media, landing.

Content Governance PlanCollaborative design how created content will be governed.

Design ValidationFor example, a RITE study.

Development Infrastructure ConfigurationContinuous Integration setup.

Technical Package Identification / EvaluationPerform product evaluations for package solution components.

Architecture Spikes / Proofs of ConceptProve candidate architectures via top to bottom spikes.

Page 133: Putting the "User" back in User Experience

“The perspective and processes ————— is focusing on and perfecting will, over time, become standard operating procedure for

any application development project.”

Page 134: Putting the "User" back in User Experience
Page 135: Putting the "User" back in User Experience

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

Page 136: Putting the "User" back in User Experience

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

Page 137: Putting the "User" back in User Experience

Today

6 months

3 years

Page 138: Putting the "User" back in User Experience

8 Design Research practices to kick start your

user knowledge!

Page 139: Putting the "User" back in User Experience

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 140: Putting the "User" back in User Experience

Contextual Inquiries

Page 141: Putting the "User" back in User Experience

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 142: Putting the "User" back in User Experience
Page 143: Putting the "User" back in User Experience

Observing Users.

Page 144: Putting the "User" back in User Experience

Persona Development

Page 145: Putting the "User" back in User Experience

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 146: Putting the "User" back in User Experience

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

Page 147: Putting the "User" back in User Experience

As a user…Jane needs to…

Page 148: Putting the "User" back in User Experience

Concept Validation

Page 149: Putting the "User" back in User Experience

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 150: Putting the "User" back in User Experience
Page 151: Putting the "User" back in User Experience
Page 152: Putting the "User" back in User Experience

Affinity Diagramming

Page 153: Putting the "User" back in User Experience
Page 154: Putting the "User" back in User Experience

Participatory Design

Page 155: Putting the "User" back in User Experience

“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 156: Putting the "User" back in User Experience

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

Page 157: Putting the "User" back in User Experience

Card Sorting

Page 158: Putting the "User" back in User Experience

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

Page 159: Putting the "User" back in User Experience

404 testing

Page 160: Putting the "User" back in User Experience

Comics, fast!

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

www.ubercomics.com

Page 161: Putting the "User" back in User Experience

User Journals / Diaries

Page 162: Putting the "User" back in User Experience

“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 163: Putting the "User" back in User Experience

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

Page 164: Putting the "User" back in User Experience

http://www.trackyourhappiness.org/

Page 165: Putting the "User" back in User Experience

“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 166: Putting the "User" back in User Experience

8 Design Research practices to kick start your

user knowledge!

Page 167: Putting the "User" back in User Experience

Rockstars!

Page 168: Putting the "User" back in User Experience

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

User Experience Researcher at Google Search

Page 169: Putting the "User" back in User Experience

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

Page 170: Putting the "User" back in User Experience

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

Google I/O 2014 - Perfectly executing the wrong plan

Page 171: Putting the "User" back in User Experience

Research +

Lean Startup

Page 172: Putting the "User" back in User Experience

Leisa Reichelthttp://www.disambiguity.com/

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

Page 173: Putting the "User" back in User Experience

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

Page 174: Putting the "User" back in User Experience

https://twitter.com/leisa

Page 175: Putting the "User" back in User Experience

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

Page 176: Putting the "User" back in User Experience

Big Government +

Empathy

Page 177: Putting the "User" back in User Experience

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

Page 178: Putting the "User" back in User Experience

10+ Years

Page 179: Putting the "User" back in User Experience

Enterprise / Complex Software

+ Design Research

Page 180: Putting the "User" back in User Experience

Contextual InquiriesObserve & document user in context/environment

Participatory DesignCo-creation explorations with users.

User Journals / DiariesUsers document their experiences over time.

Card SortExplore users’ mental models for content and labeling.

Discovery Ideation Go to MarketReleaseDesign & DevelopmentPre-Discovery

Revealing Reality Building & EvolvingFocused Innovation

Only a subset of these activities will be appropriate for any given project.

Engagement Readiness Analysis Foundational Analysis

Innovation Training

Design Thinking WorkshopTeach the design thinking framework.

Stakeholder InterviewsUnderstand staheholders’ business goals & strategy.

Scenario-based System WalkthroughsDemo of existing solution.

Application / IA MapDocument the structure of the existing solution.

Strategic Ideation

Concepts Validation with UsersValidate design prototypes through user feedback.

KANO Feature PrioritizationPrioritize features with users through KANO analysis.

Qualitative & Quantitative Data SynthesisAnalyze validation data..

Align & Assess Workshop Assess readiness across 7 capabilites.

Design Research

Qualitative Observation

Affinity DiagrammingConstruct themes from qualitative data.

Persona DevelopmentCreate customer types based on behaviors and values.

Current Journey MapVisualize the user’s perspective of the current experience.

Research PlanDesign activities to meet research goals.

Technical Organization Capability AnalysisExisting skills and toolsets.

Solution Architecture AssessmentExisting application architecture.

Enterprise Architecture Capability AssessmentExisting enterprise infrastructure.

Content InventoryCatalog the content of the website.

Heuristic EvaluationIdentify initial breakdowns and opportunities.

Competitive AnalysisEvaluate competitors and comparables on specific axes.

Client Data AnalysisMarket research, website feedback, corporate strategy, etc.

Brand AnalysisEvaluate the state of the brand.

Metrics EvaluationEstablish quantitative baseline of engagement & conversion data.

Research UX Design Technology Digital Marketing

User Workflow ModelingVisually document workflows & work systems.

SurveysSolicit structured feedback from users.

Quantitative

Quantitative Data VisualizationPresent data visually.

Conceptual User Scenari-osExplanation TBD.

Conceptual User ScenariosWrite high level narratives of an ideal future flow.

StoryboardsIllustrate graphical representa-tions of scenarios.

Concepts: Paper / Interactive / VideoDevelop concepts for testing.with users.

Experience Strategy

Opportunities Prioritization MatrixPrioritize in three dimensions, including user experience impact.

Consolidated User States DiagramAbstracted from individual user workflows.

Future Journey MapVisualize the user’s future, improved experience.

Design PrinciplesSummarize the vision for the product/service in statements to guide the design.

Product / Experience RoadmapPlan how great UX can be achieved through the design.

Experience Success MetricsAgree on business metrics for a successful user experience.

Elaboration

Detailed User ScenariosWrite detailed narratives for user experience flows.

Workflow ConceptsDraw high-level wireframes for key workflows.

Application / Navigation Framework ConceptsCreate models for the framework of the application.

Digital Marketing Go LiveCampaign launch.

Ongoing User ResearchTargeted analysis of subsequent releases.

Periodic Strategy and Execution Review Assess progress towards goals.

Skills TransferEducate client development team.

Ideation / ValidationCreate testable concepts and validate them with users.

Qualitative ResearchInvestigate ongoing opportunities and concepts with users.

Unit TestingTest system units in isolation.

DevelopmentWrite code and tests to complete sprint tasks.

Requirements / User Stories DefinitionWrite user stories based on detailed user scenarios.

Look & Feel StudiesExplore different visual treatments and styles.

Application Map / Information Architecture Map the product from the users’ point of view.

Refined, Validated ConceptsRefine the validated prototype based on findings.

Zero Feature ReleaseDemonstrate CI, automated testing, core solution setup.

High Level Technical ArchitectureDescribe high level architecture, including packaged components.

PrototypesBuild paper or coded prototypes to validate interactions.

DeployRelease to production.

Sprint PlanningCommit to stories, break down tasks.

RetrospectiveRefine approach based on what was effective.

Sprint DemoDemo completed work to stakeholders.

Backlog GroomingReprioritize backlog, add new stories.

Identify new & emerging opportunitiesAnalyze research / validation results to yield new stories.

Launch

Analysis & Synthesis

Deep Dive WorkshopsImmerse stakeholders in data and brainstorm opportunities.

Opportunities Generation & EvaluationOpportunities & prototype choice.

Marketing OpportunitiesStrategic planning of owned, earned, & paid online tactics.

Campaign OptimizationTesting of creative, media, bids & landing experiences.

Campaign MeasurementIn-depth analysis of campaign results and trends.

Campaign RefinementIterative enhancement of campaign tactics.

Beyond Conversion Optimization

Digital Marketing SWOT AnalysisIdentify strengths, weaknesses, opportunities & threats.

Usability TestingEvaluate the product’s designs or code through user testing.

Continuous IntegrationContinuously build, test, deploy, and integration test the system.

Integration TestingTest subsystems and their integration.

Run Book CreationCreate & update artifacts for maintenance & monitoring.

Non-functional Requirements TestingTest performance & scalability.

QA TestingValidate completed stories against acceptance criteria.

Visual DesignApply visual designs to the wireframes and generate assets.

IXD / WireframingCreate high fidelity wireframes of the design.

Visual Design LibraryDetermine & document visual design patterns.

Interaction Design LibraryDetermine & document interaction patterns.

User Education & TrainingConduct training sessions, create help content.

Sprint Execution Campaign ExecutionDeploy

Continuous Refinement

Production-Ready Completed FeaturesBuilt and tested features.Consolidated Workflow

DiagramAggregate individual user workflows into one diagram.

Content Creation Process FlowDesign the content creation processes for the organization.

Content ArchitectureVisualize all the content created, including creators and locations.

Digital Marketing CreativeConcepts to support search, display, social media, landing.

Content Governance PlanCollaborative design how created content will be governed.

Design ValidationFor example, a RITE study.

Development Infrastructure ConfigurationContinuous Integration setup.

Technical Package Identification / EvaluationPerform product evaluations for package solution components.

Architecture Spikes / Proofs of ConceptProve candidate architectures via top to bottom spikes.

Page 181: Putting the "User" back in User Experience
Page 182: Putting the "User" back in User Experience

Last…

Page 183: Putting the "User" back in User Experience

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

Page 184: Putting the "User" back in User Experience

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

Page 185: Putting the "User" back in User Experience

@jeremyjohnson

Thanks!

Page 186: Putting the "User" back in User Experience

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

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