The document discusses the dual nature of the web as a hypertextual information space and a software interface, emphasizing the need for user experience practitioners to clarify terminology and understand user needs through research. It explores various elements of user experience, including visual and interaction design, information architecture, and the importance of involving users in the design process. The document highlights the significance of user research and testing in creating intuitive designs that address real user needs.

1. Putting the User
back in User Experience
@jeremyjohnson

2. @jeremyjohnson
(yes, we’re hiring)

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

4. WORKED FOR

5. WORKED WITH

7. Uncover user needs,
Design great solutions,
and build out solutions to launch.

8. USER EXPERIENCE

9. we make things for

10. we make things for
http://500px.com/jeremyjohnson/sets/buenos_aires_2012

11. We work in ecosystems
http://500px.com/jeremyjohnson/sets/london_2012

12. we think visually

13. We learn through observation
http://500px.com/jeremyjohnson/sets/london_2012

14. we’re curious
http://500px.com/jeremyjohnson/sets/london_2012

16. USER EXPERIENCE

17. USER EXPERIENCE

18. Mr. User

19. Mr. User Software Development
Product Decisions
“Hey, what’s going on over there?”

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

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

22. I’ve got… 2

23. #1 You don’t really
know your
customers as well
as you think you do
(usually)…

24. #2 If you’re
launching twelve
months from now,
and are not involving
your customer,
that’s a big gamble…

25. Getting everything
right the first time,
is hard.

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

27. 2000

28. The Elements of User Experience
A basic duality: The Web was originally conceived as a hypertextual information space;
but the development of increasingly sophisticated front- and back-end technologies has
fostered 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 beyond
the scope of its original application. The goal of this document is to define some of these
terms within their appropriate contexts, and to clarify the underlying relationships among
these various elements.
Jesse James Garrett
jjg@jjg.net
Completion
30 March 2000
Web as software interface Web as hypertext system
Visual Design: graphic treatment of interface
elements (the "look" in "look-and-feel")
Information Architecture: structural design
of the information space to facilitate
intuitive access to content
Interaction Design: development of
application flows to facilitate user tasks,
defining how the user interacts with
site functionality
Navigation Design: design of interface
elements to facilitate the user's movement
through the information architecture
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Functional Specifications: "feature set":
detailed descriptions of functionality the site
must include in order to meet user needs
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally derived goals for the site
Content Requirements: definition of
content elements required in the site
in order to meet user needs
Interface Design: as in traditional HCI:
design of interface elements to facilitate
user interaction with functionality
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Visual Design: visual treatment of text,
graphic page elements and navigational
components
Concrete
task-oriented information-oriented
Abstract
time
Interface Design Navigation Design
Conception
Visual Design
Information Design
Interaction
Design
Architecture
Functional
Specifications
Information
Content
Requirements
User Needs
Site Objectives
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally 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 a
user experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.
© 2000 Jesse James Garrett http://www.jjg.net/ia/

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

30. “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/

31. http://t.co/vzaW4WSJil

32. We’re not just painters!

33. SO MUCH
MORE
COMPLEX.

34. UX

35. User Experience

36. The Elements of User Experience
A basic duality: The Web was originally conceived as a hypertextual information space;
but the development of increasingly sophisticated front- and back-end technologies has
fostered 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 beyond
the scope of its original application. The goal of this document is to define some of these
terms within their appropriate contexts, and to clarify the underlying relationships among
these various elements.
Jesse James Garrett
jjg@jjg.net
Completion
30 March 2000
Web as software interface Web as hypertext system
Visual Design: graphic treatment of interface
elements (the "look" in "look-and-feel")
Information Architecture: structural design
of the information space to facilitate
intuitive access to content
Interaction Design: development of
application flows to facilitate user tasks,
defining how the user interacts with
site functionality
Navigation Design: design of interface
elements to facilitate the user's movement
through the information architecture
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Functional Specifications: "feature set":
detailed descriptions of functionality the site
must include in order to meet user needs
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally derived goals for the site
Content Requirements: definition of
content elements required in the site
in order to meet user needs
Interface Design: as in traditional HCI:
design of interface elements to facilitate
user interaction with functionality
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Visual Design: visual treatment of text,
graphic page elements and navigational
components
Concrete
task-oriented information-oriented
Abstract
time
Interface Design Navigation Design
Conception
Visual Design
Information Design
Interaction
Design
Architecture
Functional
Specifications
Information
Content
Requirements
User Needs
Site Objectives
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally 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 a
user experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.
© 2000 Jesse James Garrett http://www.jjg.net/ia/

37. 2010

38. We own so much more than the website!

39. SERVICE
DESIGN

42. #$%!

44. WOOT

45. Systems Thinking
Ecosystems
Service Design

48. “SEAT AT
THE
TABLE”

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

51. We’ve
#WON

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

53. It’s not that easy.

54. There are still 100s of
companies that make
revenue off software in the
$100s of millions that don’t
have a user experience team.

55. “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/

56. Solving Problems by
Automating Solutions

57. Is it harder than doing
it manually?
(I didn’t say “is it easy?”)
https://www.flickr.com/photos/33989236@N00/4214027902/

58. software users
have raised the
bar
their expectations
have changed.

59. Sunday. Monday.

60. “We’re focusing on
User Experience”

61. “We’re focusing on
User Experience”
I hired a UX guy!
(or gal)

62. # of developers
# of UX designers

63. # of developers
# of UX designers

64. UX Magic

65. UX is complex.
UX is everywhere.
UX is business.

66. 2015

67. forgetting…

68. UX is complex.
UX is everywhere.
UX is business.
UX is for people.

69. “users”

70. “users”
“people”

72. The Elements of User Experience
A basic duality: The Web was originally conceived as a hypertextual information space;
but the development of increasingly sophisticated front- and back-end technologies has
fostered 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 beyond
the scope of its original application. The goal of this document is to define some of these
terms within their appropriate contexts, and to clarify the underlying relationships among
these various elements.
Jesse James Garrett
jjg@jjg.net
Completion
30 March 2000
Web as software interface Web as hypertext system
Visual Design: graphic treatment of interface
elements (the "look" in "look-and-feel")
Information Architecture: structural design
of the information space to facilitate
intuitive access to content
Interaction Design: development of
application flows to facilitate user tasks,
defining how the user interacts with
site functionality
Navigation Design: design of interface
elements to facilitate the user's movement
through the information architecture
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Functional Specifications: "feature set":
detailed descriptions of functionality the site
must include in order to meet user needs
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally derived goals for the site
Content Requirements: definition of
content elements required in the site
in order to meet user needs
Interface Design: as in traditional HCI:
design of interface elements to facilitate
user interaction with functionality
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Visual Design: visual treatment of text,
graphic page elements and navigational
components
Concrete
task-oriented information-oriented
Abstract
time
Interface Design Navigation Design
Conception
Visual Design
Information Design
Interaction
Design
Architecture
Functional
Specifications
Information
Content
Requirements
User Needs
Site Objectives
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally 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 a
user experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.
© 2000 Jesse James Garrett http://www.jjg.net/ia/

73. “user needs”

74. The Elements of User Experience
A basic duality: The Web was originally conceived as a hypertextual information space;
but the development of increasingly sophisticated front- and back-end technologies has
fostered 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 beyond
the scope of its original application. The goal of this document is to define some of these
terms within their appropriate contexts, and to clarify the underlying relationships among
these various elements.
Jesse James Garrett
jjg@jjg.net
Completion
30 March 2000
Web as software interface Web as hypertext system
Visual Design: graphic treatment of interface
elements (the "look" in "look-and-feel")
Information Architecture: structural design
of the information space to facilitate
intuitive access to content
Interaction Design: development of
application flows to facilitate user tasks,
defining how the user interacts with
site functionality
Navigation Design: design of interface
elements to facilitate the user's movement
through the information architecture
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Functional Specifications: "feature set":
detailed descriptions of functionality the site
must include in order to meet user needs
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally derived goals for the site
Content Requirements: definition of
content elements required in the site
in order to meet user needs
Interface Design: as in traditional HCI:
design of interface elements to facilitate
user interaction with functionality
Information Design: in the Tuftean sense:
designing the presentation of information
to facilitate understanding
Visual Design: visual treatment of text,
graphic page elements and navigational
components
Concrete
task-oriented information-oriented
Abstract
time
Interface Design Navigation Design
Conception
Visual Design
Information Design
Interaction
Design
Architecture
Functional
Specifications
Information
Content
Requirements
User Needs
Site Objectives
User Needs: externally derived goals
for the site; identified through user research,
ethno/techno/psychographics, etc.
Site Objectives: business, creative, or other
internally 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 a
user experience development team. Rather, it seeks to define the key considerations that go into the development of user experience on the Web today.
© 2000 Jesse James Garrett http://www.jjg.net/ia/

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

76. 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.
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.
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.
… good UX is the result of understanding the customer, seizing
technological opportunity, and pursuing simplicity.

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

78. 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

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

80. 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!

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

82. “…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/

83. Let’s talk about Listening to customers

84. “Hey, I want you to go
and understand our
user’s needs.”

85. “I’ve read stories about
our users online”
Marketing Data / Segmentation / Surveys

86. “I’ve watched some
videos about our users”
Focus Groups / Past Usability Studies / Marketing Research

87. “I’ve seen our users in
the lab”
Usability Testing / Concept Testing / Customer Councils

88. “I went to our users and
observed them”
Contextual Inquires / Field Studies / Interviews

89. “I understand best
practices, and I’m a
student of psychology"
I have experience / I’m great at what I do

90. aka Shut up, I’m a
design genius.

91. Q. Which one accurately
answers the question:

92. “Hey, I want you to go
and understand our
user’s needs.”

93. “I want to know them
so well, the system we
design “just works”
for them.”

101. User Experience

102. User Experience

103. Web Design vs. User Experience

104. User Experience

105. “Top Job”
http://money.cnn.com/pf/best-jobs/2012/snapshots/43.html

106. “Top Job”
http://money.cnn.com/pf/best-jobs/2012/snapshots/43.html

107. http://www.uxutd.com/

109. “Give me three skills a ux
designer needs today and
for the future”

111. HTML
ILLUSTRATOR
PHOTOSHOP

112. “empathy”

114. http://poetpainter.com/

115. HARD
http://poetpainter.com/ “EASY”

116. http://poetpainter.com/

117. “personal significance”
“works like I think”

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

119. You get there by
understanding
your users.

120. 5 WAYS
Getting to know your
users helps YOU.

121. Learn the unexpected

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

123. 1.
Business needs data to
backup decisions.

124. 2.
Mind-blowing,
astonishing, insights.

125. 3.
Something
in-between…

126. Observations will
speak volumes for
your users.

127. User Quotes

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

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

130. “I have no idea how to
use this, so I just skip
that whole step”

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

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

133. Affinity Diagramming

134. Solving the right problems

135. Product Owner
“I know”
CEO
Designer
CMO
Developer

136. Institutional Knowledge

137. The 8 Monkeys
http://speakingofresearch.com/category/news/campus-activism/

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

139. The 8 Monkeys
http://speakingofresearch.com/category/news/campus-activism/

140. Institutional Knowledge

141. Go observe, talk to, and
interact with your users!
Get first hand experience of your
user’s problems!

142. Show you care

143. #1 reaction when
observing users of
business-to-business
software?

144. “Wow, you care about us?
I thought we were
abandoned to the depths
of bad software!”

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

146. #1 reaction when
observing users.

147. Hugs.

148. You’re the expert

149. “Hey, who do I go to, I
have a question
about what we
should do here?”

150. Amount you know about your users Number of questions you’ll get about the direction of your product

151. “SEAT AT
THE
TABLE”

152. + 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

153. Design Research
(or User Research)

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

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

156. Usability Testing vs. User Research

157. Today
6 months
3 years

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

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

160. 8 Design Research
practices to kick start your
user knowledge!

161. Participatory Design
Contextual Inquiries
Affinity Diagramming
Understand Design Refine
Persona Development
Concept Validation
Workflow Modeling
KANO Feature Prioritization
Card Sorting
404 testing
User Journals / Diaries

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

163. Psychology, cognitive
science, etc…

164. 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.
http://www.shmula.com/jeff-bezos-5-why-exercise-root-cause-analysis-cause-and-effect-ishikawa-lean-thinking-six-sigma/987/

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

166. Contextual
Inquiries

167. 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

169. Observing Users.

170. Persona
Development

171. Primary Persona
David
Corporate Employee, 40 yrs old
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:
Experience:
Health Motivators:
Goals:
Technology Adoption:
90% 55% 100%
Ideal State:
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.

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

173. As a user…
Jane needs to…

174. Concept
Validation

175. 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

177. “Starbucks Testing”

182. x
x

183. Core team makes decisions
Done!
the core team

184. Affinity
Diagramming

186. Participatory
Design

187. “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

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

189. Card
Sorting

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

191. 404
testing

192. Comics, fast!
www.ubercomics.com
Want comics delivered to your home, fast?
Download our app!

193. 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

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

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

197. 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/

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

199. User
Journals /
Diaries

200. “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/

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

202. http://www.trackyourhappiness.org/

203. “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/

204. 8 Design Research
practices to kick start your
user knowledge!

205. Rockstars!

206. Tomer Sharon
User Experience Researcher at Google Search
https://plus.google.com/+TomerSharon/about

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

208. Google I/O 2014 - Perfectly executing the wrong plan
https://www.youtube.com/watch?v=9TJTbRw4ri8

209. Research
+
Lean Startup

210. Leisa Reichelt
Head of User Research at the Government Digital Service in the Cabinet Office
http://www.disambiguity.com/

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

212. https://twitter.com/leisa

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

214. Big Government
+
Empathy

215. 1. Research with project teams, not for them
2. Research with users, as opposed to
http://inside.mygov.scot/2014/09/09/five-principles-user-research/
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

216. Peter Eckert
Co-Founder & CXO
http://projekt202.com/

217. 10+ Years

218. Enterprise / Complex
Software
+
Design Research

221. Last…

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

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

224. Thanks!
@jeremyjohnson

225. “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

226. Thanks!
Questions?
Jeremy Johnson
Director of User Experience @
@jeremyjohnson
214-228-2894
.com
@projekt202
jeremy.johnson@projekt202.com