2. MATT TONAK
COMMUNITY MANAGER
Friday, October 21, 2011
3. THE NERDERY
HOURS WORKED SINCE 2003 PROJECTS DOGS IN OUR OFFICE BIKE COMMUTERS
821,217 4334
HOURS WORKED, LAST 12 MONTHS
EIGHT 6 AVERAGE JANUARY TEMPERATURE
º
PEOPLE WHO WORK AT THE NERDERY
TWO HUNDRED SIXTY-ONE FOUR
WE HELP OUR PARTNERS GET BIG
IDEAS OUT OF THEIR HEADS AND
ONTO THEIR CLIENTS’ WEBSITES
HTTP://WWW.NERDERY.COM
TWITTER: @THE_NERDERY
Friday, October 21, 2011
4. HOW TO PARTICIPATE
Using the questions panels in the GoToMeeting app
On Twitter @The_Nerdery
Send us an email at primers@nerdery.com
Friday, October 21, 2011
5. INTRO TO
USER RESEARCH
INTERACTIVE PRIMER SERIES
Friday, October 21, 2011
6. ZACK
USER EXPERIENCE DESIGNER
Friday, October 21, 2011
7. MIKE
DIRECTOR OF USER EXPERIENCE
Friday, October 21, 2011
8. WHAT IS UX?
User Goals
Application
Business Goals
Friday, October 21, 2011
9. WHAT IS UX?
Aligning user behavior and
motivations with business objectives
through interaction design
User Goals Business Goals Application
Friday, October 21, 2011
23. SELF DESIGN
SOLVING YOUR OWN PROBLEM
Friday, October 21, 2011
24. SELF DESIGN
SOLVING YOUR OWN PROBLEM
I know what I want for dinner.
Self Design is cooking for yourself.
Friday, October 21, 2011
25. SELF DESIGN
SOLVING YOUR OWN PROBLEM
I know what I want for dinner.
Self Design is cooking for yourself.
Pretty simple.
Friday, October 21, 2011
26. GENIUS DESIGN
SOLVING A PROBLEM YOU’VE SOLVED BEFORE
Friday, October 21, 2011
27. GENIUS DESIGN
SOLVING A PROBLEM YOU’VE SOLVED BEFORE
If I’ve made dinner for Mike
(or people like him) many
times before, I rely on my
domain specific experience
to cook dinner for Mike.
Friday, October 21, 2011
28. GENIUS DESIGN
SOLVING A PROBLEM YOU’VE SOLVED BEFORE
If I’ve made dinner for Mike
(or people like him) many
times before, I rely on my
domain specific experience
to cook dinner for Mike.
I don’t actually cook for Mike. #justsayin’
Friday, October 21, 2011
29. GENIUS DESIGN
THERE’S A CATCH
Friday, October 21, 2011
30. GENIUS DESIGN
THERE’S A CATCH
Genius Design presupposes that
you originally did your research to
define the problem.
Friday, October 21, 2011
37. USER RESEARCH
IS NOT
MARKETING RESEARCH
Friday, October 21, 2011
38. USER RESEARCH
IS NOT
MARKETING RESEARCH
...but there is some overlap
Friday, October 21, 2011
39. USER RESEARCH
IS NOT
MARKETING RESEARCH
...but there is some overlap
Friday, October 21, 2011
40. USER RESEARCH
We do this
IS NOT
MARKETING RESEARCH
...but there is some overlap
Friday, October 21, 2011
41. USER RESEARCH
We do this
IS NOT
MARKETING RESEARCH
...but there is some overlap
Friday, October 21, 2011
42. USER RESEARCH
We do this
IS NOT
We DON’T do this
MARKETING RESEARCH
...but there is some overlap
Friday, October 21, 2011
43. USER RESEARCH MARKETING RESEARCH
Friday, October 21, 2011
44. USER RESEARCH MARKETING RESEARCH
Preferences
Opinions
Likes
Desires
Friday, October 21, 2011
45. USER RESEARCH MARKETING RESEARCH
Behavior Preferences
Needs Opinions
Goals Likes
Tasks Desires
Mental & Physical Context
Friday, October 21, 2011
46. RESEARCH SPECTRUM
Indi Young - Mental Models: Rosenfeld Media http://www.flickr.com/photos/rosenfeldmedia/2159500714/in/set-72157603511616271/
Friday, October 21, 2011
47. RESEARCH SPECTRUM
Indi Young - Mental Models: Rosenfeld Media http://www.flickr.com/photos/rosenfeldmedia/2159500714/in/set-72157603511616271/
Friday, October 21, 2011
48. RESEARCH SPECTRUM
overlap
Indi Young - Mental Models: Rosenfeld Media http://www.flickr.com/photos/rosenfeldmedia/2159500714/in/set-72157603511616271/
Friday, October 21, 2011
49. WHY DO USER RESEARCH?
Friday, October 21, 2011
50. WHY DO USER RESEARCH?
Remember when we said that
design solves problems?
Friday, October 21, 2011
51. WHY DO USER RESEARCH?
Remember when we said that
design solves problems?
Remember when we said that a UX
process starts with defining the problem?
Friday, October 21, 2011
52. WHY DO USER RESEARCH?
Remember when we said that a UX
process starts with defining the problem?
Friday, October 21, 2011
53. WHY DO USER RESEARCH?
Friday, October 21, 2011
54. WHY DO USER RESEARCH?
Friday, October 21, 2011
55. WHY DO USER RESEARCH?
Research tells us what the problem is.
Friday, October 21, 2011
56. WHY DO USER RESEARCH?
Research tells us what the problem is.
Research tells us why it’s a problem.
Friday, October 21, 2011
57. WHY DO USER RESEARCH?
Research tells us what the problem is.
Research tells us why it’s a problem.
Research shows us how to fix it.
Friday, October 21, 2011
59. BENEFITS OF USER RESEARCH
Throughly defines the problem.
Friday, October 21, 2011
60. BENEFITS OF USER RESEARCH
Throughly defines the problem.
Informs design decisions.
Friday, October 21, 2011
61. BENEFITS OF USER RESEARCH
Throughly defines the problem.
Informs design decisions.
Provides direction & priority.
Friday, October 21, 2011
62. BENEFITS OF USER RESEARCH
Throughly defines the problem. SHOWS US THE “WHAT”
Informs design decisions.
Provides direction & priority.
Friday, October 21, 2011
63. BENEFITS OF USER RESEARCH
Throughly defines the problem. SHOWS US THE “WHAT”
Informs design decisions. TEACHES US THE “WHY”
Provides direction & priority.
Friday, October 21, 2011
64. BENEFITS OF USER RESEARCH
Throughly defines the problem. SHOWS US THE “WHAT”
Informs design decisions. TEACHES US THE “WHY”
Provides direction & priority. GUIDES US TO THE “HOW”
Friday, October 21, 2011
65. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
“WHAT”
“WHY”
“HOW”
Friday, October 21, 2011
66. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
“WHAT” “We need a website redesign”
“WHY”
“HOW”
Friday, October 21, 2011
67. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“WHY”
“HOW”
Friday, October 21, 2011
68. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t
“WHY” working for us”
“HOW”
Friday, October 21, 2011
69. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“HOW”
Friday, October 21, 2011
70. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“We should update
“HOW” the look & feel”
Friday, October 21, 2011
71. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“We should update We need to design clearer
“HOW” the look & feel” call to action buttons.
Friday, October 21, 2011
72. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“We should update We need to design clearer
“HOW” the look & feel” call to action buttons.
Friday, October 21, 2011
73. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“We should update We need to design clearer
“HOW” the look & feel” call to action buttons.
Friday, October 21, 2011
74. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“We should update We need to design clearer
“HOW” the look & feel” call to action buttons.
Vague & Undefined
Friday, October 21, 2011
75. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“We should update We need to design clearer
“HOW” the look & feel” call to action buttons.
Vague & Undefined
Friday, October 21, 2011
76. EXAMPLE PROJECT NEEDS
Stated: What Research Tells Us:
The website doesn’t meet
“WHAT” “We need a website redesign”
users’ expectations
“The current site isn’t There are usability
“WHY” working for us” flaws in the design
“We should update We need to design clearer
“HOW” the look & feel” call to action buttons.
Vague & Undefined
Clear & Actionable
Friday, October 21, 2011
77. BEWARE OF THE DATA TYPE
QUALITATIVE vs. QUANTITATIVE
Friday, October 21, 2011
78. BEWARE OF THE DATA TYPE
QUALITATIVE X
vs. QUANTITATIVE
Friday, October 21, 2011
79. BEWARE OF THE DATA TYPE
QUALITATIVE X
vs. QUANTITATIVE
Just remember
Friday, October 21, 2011
80. BEWARE OF THE DATA TYPE
QUALITATIVE X
vs. QUANTITATIVE
Just remember
We need both!
Friday, October 21, 2011
81. BEWARE OF THE DATA TYPE
QUANTITATIVE
Objective
X
vs. QUALITATIVE
Subjective
“Measurable” “Non-measurable”
Numerical Data NOT Numerical
Statistics Concepts
Friday, October 21, 2011
82. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
Friday, October 21, 2011
83. BEWARE OF THE DATA TYPE
QUANTITATIVE
QUALITATIVE
Friday, October 21, 2011
84. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
Friday, October 21, 2011
85. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
Page Views
Bounce Rate
Time On Site
Yes/No
True/False
Friday, October 21, 2011
86. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
Page Views Expectations
Bounce Rate Reactions
Time On Site Confusion
Yes/No Comprehension
True/False Behavior
Friday, October 21, 2011
87. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
Friday, October 21, 2011
88. BEWARE OF THE DATA TYPE
QUALITATIVE
QUANTITATIVE
Friday, October 21, 2011
89. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
Friday, October 21, 2011
90. BEWARE OF THE DATA TYPE
QUANTITATIVE informs QUALITATIVE
Friday, October 21, 2011
91. BEWARE OF THE DATA TYPE
QUANTITATIVE informs QUALITATIVE
Friday, October 21, 2011
92. BEWARE OF THE DATA TYPE
QUANTITATIVE informs QUALITATIVE
“WHAT”
Friday, October 21, 2011
93. BEWARE OF THE DATA TYPE
QUANTITATIVE informs QUALITATIVE
“WHAT”
Friday, October 21, 2011
94. BEWARE OF THE DATA TYPE
QUANTITATIVE informs QUALITATIVE
“WHAT” “WHY”
Friday, October 21, 2011
95. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
“WHAT” informs “WHY”
Friday, October 21, 2011
96. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
“WHAT” informs “WHY”
i.e. Sign-up page bounce rate it high.
Friday, October 21, 2011
97. BEWARE OF THE DATA TYPE
QUANTITATIVE QUALITATIVE
“WHAT” informs “WHY”
i.e. Sign-up page bounce rate it high. i.e. Call to action text is confusing.
Friday, October 21, 2011
98. WHEN SHOULD YOU DO
USER RESEARCH?
Timeframe Beginning of the project During Design Production Project Completion
- re-enforce direction
- inform direction & scope - gauge progress/success
Benefit - validate design decisions
- throughly defines the problem - guides product direction
- acquire design feedback at
- provides insights for next steps - discover areas for improvement
significantly lower cost
- Contextual Inquiry - Usability Testing - Usability Testing
Example - Field Study/Ethnography - Card Sorting - Site Search Analytics
Method/Use - User Interviews - Personas - Web Analytics
- Surveys - Mental Models - A/B Testing/Multivariate Testing
Friday, October 21, 2011
101. BONUS ROUND
ONGOING RESEARCH
Friday, October 21, 2011
102. BONUS ROUND
ONGOING RESEARCH
How:
Friday, October 21, 2011
103. BONUS ROUND
ONGOING RESEARCH
How: - Create a solid and sustainable research plan for a continuous
feedback loop from your customers/users
Friday, October 21, 2011
104. BONUS ROUND
ONGOING RESEARCH
How: - Create a solid and sustainable research plan for a continuous
feedback loop from your customers/users
Why:
Friday, October 21, 2011
105. BONUS ROUND
ONGOING RESEARCH
How: - Create a solid and sustainable research plan for a continuous
feedback loop from your customers/users
Why: - Your audience changes and evolves over time
Friday, October 21, 2011
106. BONUS ROUND
ONGOING RESEARCH
How: - Create a solid and sustainable research plan for a continuous
feedback loop from your customers/users
Why: - Your audience changes and evolves over time
- Your product/service/website will attract new audience segments
Friday, October 21, 2011
107. BONUS ROUND
ONGOING RESEARCH
How: - Create a solid and sustainable research plan for a continuous
feedback loop from your customers/users
Why: - Your audience changes and evolves over time
- Your product/service/website will attract new audience segments
-Other products/services/websites introduce new expectations for
interacting with your information
Friday, October 21, 2011
108. WHEN SHOULD YOU DO
USER RESEARCH?
Timeframe Beginning of the project During Design Production Project Completion
- re-enforce direction
- inform direction & scope - gauge progress/success
Benefit - validate design decisions
- throughly defines the problem - guides product direction
- acquire design feedback at
- provides insights for next steps - discover areas for improvement
significantly lower cost
- Contextual Inquiry - Usability Testing - Usability Testing
Example - Field Study/Ethnography - Card Sorting - Site Search Analytics
Method/Use - User Interviews - Personas - Web Analytics
- Surveys - Mental Models - A/B Testing/Multivariate Testing
Friday, October 21, 2011
109. WHEN SHOULD YOU DO
USER RESEARCH?
Timeframe Beginning of the project During Design Production Project Completion
- re-enforce direction
- inform direction & scope - gauge progress/success
Benefit - validate design decisions
- throughly defines the problem - guides product direction
- acquire design feedback at
- provides insights for next steps - discover areas for improvement
significantly lower cost
- Contextual Inquiry - Usability Testing - Usability Testing
Example - Field Study/Ethnography - Card Sorting - Site Search Analytics
Method/Use - User Interviews - Personas - Web Analytics
- Surveys - Mental Models - A/B Testing/Multivariate Testing
Friday, October 21, 2011
110. WHEN SHOULD YOU DO
USER RESEARCH?
Timeframe Beginning of the project During Design Production Project Completion
Let’s talk about a few in more detail
- re-enforce direction
- inform direction & scope - gauge progress/success
Benefit - validate design decisions
- throughly defines the problem - guides product direction
- acquire design feedback at
- provides insights for next steps - discover areas for improvement
significantly lower cost
- Contextual Inquiry - Usability Testing - Usability Testing
Example - Field Study/Ethnography - Card Sorting - Site Search Analytics
Method/Use - User Interviews - Personas - Web Analytics
- Surveys - Mental Models - A/B Testing/Multivariate Testing
Friday, October 21, 2011
113. WHAT IS CONTEXTUAL INQUIRY?
Fancy Definition: a field data-gathering technique that studies a few carefully
selected individuals in depth to arrive at a fuller understanding of
the work practice across all customers.
Friday, October 21, 2011
114. WHAT IS CONTEXTUAL INQUIRY?
Fancy Definition: a field data-gathering technique that studies a few carefully
selected individuals in depth to arrive at a fuller understanding of
the work practice across all customers.
- Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered Systems
Friday, October 21, 2011
115. WHAT IS CONTEXTUAL INQUIRY?
Fancy Definition: a field data-gathering technique that studies a few carefully
selected individuals in depth to arrive at a fuller understanding of
the work practice across all customers.
- Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered Systems
Non-Nerd Version:
Friday, October 21, 2011
116. WHAT IS CONTEXTUAL INQUIRY?
Fancy Definition: a field data-gathering technique that studies a few carefully
selected individuals in depth to arrive at a fuller understanding of
the work practice across all customers.
- Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered Systems
Non-Nerd Version: go watch people work in their own context.
Friday, October 21, 2011
117. WHAT IS CONTEXTUAL INQUIRY?
Fancy Definition: a field data-gathering technique that studies a few carefully
selected individuals in depth to arrive at a fuller understanding of
the work practice across all customers.
- Hugh Beyer and Karen Holtzblatt - Contextual Design: Defining Customer-Centered Systems
Non-Nerd Version: go watch people work in their own context.
- Us
Friday, October 21, 2011
118. THE “HOW-TO” OF
CONTEXTUAL INQUIRY
1. Recruiting Contact & schedule the people you will observe. THIS IS THE MOST IMPORTANT STEP.
2. Research Plan Establish a clear focus for what you’re seeking to understand & what you hope to learn.
3. Observe Watch users completing relevant goals & tasks in their own context.
4. Analyze Review what you learned. What patterns emerged?
5. Report Create appropriate documentation to communicate what you found to the team.
Friday, October 21, 2011
119. WHAT’S THE BENEFIT OF
CONTEXTUAL INQUIRY?
Are there current frustrations or problems with the existing design? What about with their
Issues physical environment or other systems and processes? Can the new design support those?
What are the high level priorities of the people using the current design?
Goals What are they trying to accomplish?
Tasks What are the steps people are taking to accomplish those goals?
Environment What is their physical location like? How does it impact the design or how they use it?
What other hardware or software are they using to do their work? Can (or should) they be
Applications integrated? Can the new design eliminate the need of these factors?
Friday, October 21, 2011
120. WHAT’S THE BENEFIT OF
CONTEXTUAL INQUIRY?
Work-Arounds Are people creating ways to work around a poor design now?
Triggers What causes someone to begin down a path of completing a goal?
Are there several ways in which people are accomplishing the same goal or task? Should the
Variation(s) design support one? Both?
Partners Who does the person work with to accomplish a goal or task?
“Crutches” Do people have “cheat-sheets” or other materials to help them accomplish goals and tasks?
Friday, October 21, 2011
121. RECOMMENDATIONS FOR
CONTEXTUAL INQUIRY
Recruiting Be sure to observe an appropriate, representative sample of your target audience.
Aim for 3-5 participants separately.
Timeline Allow 1-2 weeks for recruiting effort. (Varies depending on the project & participant availability)
Allow 1-2 weeks for conducting the research. (Assuming 5 participants)
Allow AT LEAST 1 week for analysis
Allow 1 week to create a report.
Approximately 4-8 weeks total
Friday, October 21, 2011
124. WHAT IS USABILITY TESTING?
Definition: a form of gathering feedback from actual users of a design by
having them attempt to complete intended goals and tasks with
said design.
Friday, October 21, 2011
125. THE “HOW-TO” OF
USABILITY TESTING
Determine who you will conduct usability testing with, write a screener to ensure you recruit
1. Recruiting your target audience from the responses & schedule the participants. Again, a CRITICAL step.
Where will the tests take place? What will the research cover? As before, Establish a clear
2. Research Plan focus for what you hope to learn.
3. Conduct Tests Conduct the test (ideally with an experience moderator) & observe, while taking notes.
4. Analyze Discuss test results with any participating team members & review recordings if available.
5. Report Create appropriate documentation that conveys the findings from the research.
Friday, October 21, 2011
126. WHAT’S THE BENEFIT OF
USABILITY TESTING?
Expectations Is the solution designed meeting expectations of those intended to use it?
Task Completion Can the users complete the available tasks of the design?
Level of difficulty If so, how difficult was it for them to complete the task(s)? Why?
Path Taken What were the steps involved in completing a given task?
Impression Did the user(s) understand the overall message and intent that the design meant to convey?
Friday, October 21, 2011
127. VARIATIONS OF
USABILITY TESTING
In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator
leading the session(s) with participants.
Research is conducted via “live recruiting” from an existing website.
Remote, Moderated Participants are immediately connected with a moderator from a remote location.
Sessions are conducted using an online service that allows users to
Remote, Un-moderated participate at their convenience, without a moderator.
Usability testing done with minimal recruiting effort and logistical
Guerilla planning. Common locations are coffee shops, bars, offices, etc.
Friday, October 21, 2011
128. VARIATIONS OF
USABILITY TESTING
Good
In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator
leading the session(s) with participants.
Research is conducted via “live recruiting” from an existing website.
Remote, Moderated Participants are immediately connected with a moderator from a remote location.
Sessions are conducted using an online service that allows users to
Remote, Un-moderated participate at their convenience, without a moderator.
Usability testing done with minimal recruiting effort and logistical
Guerilla planning. Common locations are coffee shops, bars, offices, etc.
Friday, October 21, 2011
129. VARIATIONS OF
USABILITY TESTING
Better
In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator
leading the session(s) with participants.
Research is conducted via “live recruiting” from an existing website.
Remote, Moderated Participants are immediately connected with a moderator from a remote location.
Sessions are conducted using an online service that allows users to
Remote, Un-moderated participate at their convenience, without a moderator.
Usability testing done with minimal recruiting effort and logistical
Guerilla planning. Common locations are coffee shops, bars, offices, etc.
Friday, October 21, 2011
130. VARIATIONS OF
USABILITY TESTING
Best
In-Person, Moderated Sessions are conducted at a physical location with a live, in-person moderator
leading the session(s) with participants.
Research is conducted via “live recruiting” from an existing website.
Remote, Moderated Participants are immediately connected with a moderator from a remote location.
Sessions are conducted using an online service that allows users to
Remote, Un-moderated participate at their convenience, without a moderator.
Usability testing done with minimal recruiting effort and logistical
Guerilla planning. Common locations are coffee shops, bars, offices, etc.
Friday, October 21, 2011
131. RECOMMENDATIONS FOR
USABILITY TESTING
Do your own recruiting if possible. If this is not possible, work closely with a recruiting agency
Recruiting to ensure the participants being recruited match your target audience.
(especially for the particular research you’re doing)
Aim for 5-10 participants. (dependent on the study)
Timeline Allow 1-2 weeks for recruiting effort. (Varies depending on the recruiting method)
Allow 1 week for conducting the tests. (Assuming 5 participants)
Allow 3 days to 1 week for analysis.
Allow 3 days to 1 week to create a report.
Approximately 3-6 weeks total
Friday, October 21, 2011
150. NERDERY RESEARCH METHODS
Usability Testing Field Study/Ethnography
Surveys Site Search Analytics
Card Sorting
Web Analytics
Stakeholder Interviews
A/B Testing : Multivariate Testing
User Interviews
Mental Models
Contextual Inquiry
Personas
Friday, October 21, 2011
151. NERDERY RESEARCH METHODS
“WHAT”
Usability Testing Field Study/Ethnography
Surveys Site Search Analytics
Card Sorting
Web Analytics
Stakeholder Interviews
A/B Testing : Multivariate Testing
User Interviews
Mental Models
Contextual Inquiry
Personas
Friday, October 21, 2011
152. NERDERY RESEARCH METHODS
“WHY”
Usability Testing Field Study/Ethnography
Surveys Site Search Analytics
Card Sorting
Web Analytics
Stakeholder Interviews
A/B Testing : Multivariate Testing
User Interviews
Mental Models
Contextual Inquiry
Personas
Friday, October 21, 2011
153. NERDERY RESEARCH METHODS
“HOW”
Usability Testing Field Study/Ethnography
Surveys Site Search Analytics
Card Sorting
Web Analytics
Stakeholder Interviews
A/B Testing : Multivariate Testing
User Interviews
Mental Models
Contextual Inquiry
Personas
Friday, October 21, 2011
154. QUESTIONS?
Using the questions panels in the GoToMeeting app
On Twitter @The_Nerdery
Send us an email at primers@nerdery.com
More answers online at http://nerdery.com
Friday, October 21, 2011