Find a book on UX or a UX adjacent topic that is not already in the collection under Books, provide a list of important quotations, in the way you see in the Books section, and write a review of the book — who it is for, what it explains, how well you think it works. When you send me the quotations, I will add your book and your quotations to Books. Post your review on your blog. If you want to practice talking head presenting, you can video record your review and post that to your blog.
Full Book Title: Observing the User Experience: A Practitioner’s Guide to User Research
Authors: Mike Kuniavsky, Elizabeth Goodman, and Andrea Moed
Publisher : Morgan Kaufmann; 2nd edition (September 21, 2012)
ISBN : 978-0123848697
I came across Observing the User Experience when I first saw it being listed as a required reading book for the ENGL 8122 User-Experience Research & Writing class. The book holds a 4.3 on Amazon. If you’re looking for one book to read to get a solid understanding of user research, this is it. This is a brilliant textbook and reference book as it almost covers all the major subjects in UX full of clear descriptions and useful examples and case studies.
- Who is the book for?
The textbook is suitable for the beginner in UX such as somebody who is interested in UX but not yet working in it or somebody who has just started their career to develop or improve a product in UX but lacks the experience.
Besides, it is also suitable for professionals who want to hone their skills in UX.
The authors point out on the Preface there are 7 types of readers who might be the targeted readers.
- A program manager who wants to know how to prioritize a team’s effort
- A designer who needs to create and refine new ways to interact
with and through digital information
- A marketing manager who wants to know what people find most
valuable in your products
- An information architect who needs to pick an organizational
scheme
- A programmer creating a user interface, trying to interpret an
ambiguous spec
- A consultant trying to make your clients’ products better
- An inventor who wants to make a product people will love
The book is excellent for someone who wants to know how the people who use the product they are making perceive it, what they expect from it, what they need from it, and whether they can use what they have made for them.
- What does the book explain?
This book serves as an indispensable guide for practitioners seeking to enhance their user research skills and create products that truly resonate with their target audience. Divided into three parts, the book covers a comprehensive range of topics with a lot of clear subtitles and bullet points.
1). Part one is about why research is good and how it fits into product development. The first section lays the groundwork by introducing key concepts, such as the importance of user research, a nano-usability test, a micro-usability test, the different roles involved like end users, the company and advertisers, and the overall process. The authors’ clear and concise explanations make these foundational ideas accessible to readers of all backgrounds.
2). Part two is about various user experience research techniques which are really shining in this book.
This is the most substantial section that dives deep into various user research techniques, including research planning, competitive research, recruiting interviews, focus groups, object-based techniques, observational field visits, diary studies, usability tests, surveys, global and cross-cultural research, analyzing qualitative data, usage data and customer feedback. For each method, the writers provide a clear definition of the term including when to conduct the method, what is the method, detailed instructions on how to conduct it effectively, and how to integrate the findings into the product or software development. Even if you are already familiar with the basics, the authors’ clear explanations are a nice refresher. In addition, as someone who learns best from real-world examples, I appreciate all the concrete tips and instructions the authors add in some key terms.
3) Part 3 offers guidance on putting research into action, doing reports, presentations, and workshops and creating a user-centered corporate culture.
- Quotes and reflections
Quote 1
“Just as technology strategist John Shiple said, “Competitive research is one of the first things you should do. It can define your world for you and make your life a whole lot easier” (Page 74).
“Competitive Product Interviews and Observation
One-on-one interviews with users of a competitive product can reveal much about what makes that product functional and where it fails. Watching people use your competition’s product reveals usage” (Page 83).
This raises our awareness to conduct interviews with different users of a competitive product and dive deeper into the advantages that the competition’s product gives its users and the hindrances it places in their ways. Competitive research can be done at any point in our product development cycle and it provides useful information as “Great minds think alike”. It can give us some shortcuts to design or improve a product or service if we can draw on the shining points and avoid the shortages of the competition’s product and service.
Quote 2
The analyst must determine who the competitors are, what aspects should be compared, and how to compare them. The general sequence of steps resembles those that a financial analyst would follow when surveying the market landscape—but will take a lot less time and cost a lot less money.
- Identify and profile the competition.
- Define a set of key dimensions for comparison.
- Compare competitors to each other (and to your product).
- Use the comparisons to create recommendations for action.” (Page 75).
This book provides a thorough and systematic approach to making a competitor analysis.
1). Identifying and profile the competition
- We can start with online searches using various keywords or phrases related to our product’s main functions.
- We should know the description of the product and a profile of its audience. We can get audience details from news, forums, reviews, etc.
2). Defining Comparison Dimensions
We should limit the scope of the competitive analysis to what our users may consider important and those dimensions relevant to the research questions we need to answer.
We should collect the important features or attributes of the competitive products.
And we should emphasize focusing on user perspectives and priorities instead of just internal assumptions.
Also, we should prioritize based on the areas that mean the most to the product’s functionality, to the company’s success, or to the users’ satisfaction.
3). Competitive Analysis Techniques
We can also conduct user research methods like usability testing about the competitors’ products. In addition, we should have a balanced perspective by looking at the positives of competitors rather than all just negatives.
To do a rapid competitive analysis, we can concentrate on getting the most out of existing sources: industry analysis, whitepapers, newspapers, blogs, user forums, and so on with limited time. The secret is to use comments from real users to drive our lists of features and attributes.
Quote 3
“Here is one way of dividing a standard interview process into six phases.
1). Introduction. All participants introduce themselves. In groups, it’s
important to know that the other people in the group are somewhat like you in order to feel comfortable, so a group introduction emphasizes the similarities between all the
participants, including the interviewer. In contrast, an individual interview introduction establishes the role of the interviewer as a neutral, but sympathetic, entity.
2). Warm-up. The warm-up in any interview is designed to get people to step away from their regular lives and focus on thinking about the product and the work of answering questions.
3). General issues. The initial product-specific round of questions concentrates on experiences with the product, as well as attitudes, expectations, and assumptions about it. Asking these kinds of questions early prevents the assumptions of the product development team from skewing people’s perceptions. Often, the product isn’t even named during this phase.
4). Deep focus. The product, service, or idea is introduced, and people concentrate on the details of what it does, how it works, whether they can use it, and what their immediate experience of it is. For usability testing, this phase makes up the bulk of the interview, but for site visits or exploratory interviews, it may never enter the
discussion.
5). Retrospective. This phase allows people to evaluate the product or idea in a broader light. The discussion is comparable to the “general issues” phase, but the discussion is focused on how the ideas introduced in the “deep focus” phase affect the issues discussed earlier.
6). Wrap-up. This is generally the shortest phase of the interview. It formally completes the interview so that the participants aren’t left hanging after the last question and return to administrative topics” (Page 130).
I think this book gives us a great reflection on our interview process. If our interview questions are not logical and ordered correctly, these may contribute to too subjective results. As UX designers, we can think about these questions.
1). Introduction
- For group interviews, do our introductions highlight similarities of all participants to build rapport? (This is extremely important to build rapport in a group interview with many participants who are not familiar with each other).
- For individual interviews, do our introductions establish the interviewer as a neutral but supportive entity? (We should express our gratitude for the individual’s participation and show their significance in improving the product) 2). Warm-up
- Do our warm-up questions successfully let participants step away from their daily lives and focus on answering questions about a product or the topic? (UX researchers should think about some interesting starters to help interviewees raise their awareness of using this product or service.)
- 3). General Issues
- Do these general questions effectively explore participants’ experiences, attitudes, expectations, and assumptions first? (We should try to find out their initial attitudes without introducing the name of this particular service or product and get to know if they have biased opinions towards using this type of service and product before asking further detailed questions.)
- 4). Deep Focus
- When the product or service was introduced, do deep focus questions allow concentration on details like what it does, how it works, whether they can use it, what their experience of it is, etc? (If we have usability testing, we can conduct the testing first and then ask interviewees these deep focus questions.)
- 5). Retrospective
- Do participants have the opportunity to re-evaluate the product or service more broadly? (We can ask them to rate the product or service after they consider all the factors.)
- 6). Wrap-up
- Is there a clear conclusion that does not leave participants hanging? (We should end with the shortest phase.)
- How well does it work?
Possible weaknesses:
1). The book is too lengthy which is not suitable for someone who seeks quick answers and avoids repeated ideas. Sometimes the idea is repeated to some extent in some parts of the book. Chapter two and Chapter 11 both cover the topic of the process of conducting usability tests. Although recruiting and interviews may be the backbone of every successful research project which deserves a chapter of their own in Chapter 6, these two are also covered in Chapter 13 as individual topics.
2). This is not suitable for someone who wants to delve into the psychology of users or wants to dive deeper into the subconsciousness of the clients. Readers with academic backgrounds in psychology or social sciences may find some aspects of data analysis lacking in depth.
3)There might be too many qualitative techniques covered in the book. One thing that strikes me is just how qualitative-focused most of the techniques are. Other than surveys, it is almost all interviews, observations, and the like. Is qualitative-focused the nature of user research? I am wondering if the book is missing some useful quantitative methods.
Overall Evaluation:
If I had to confine my review to a star rating system, I would give it a 4.8/5. In a nutshell, Observing the User Experience is a comprehensive and practical resource for anyone involved in user experience research, from a green hand to a seasoned professional in the field. The authors’ clear and simple writing style, extensive practical examples, and intriguing case studies make this book a must-read for those seeking to create user-centered products and services.