First of all, I want to make it clear that I'm not writing this review out of spite or to draw attention to myself, but for juniors and those who don't know what UX design is but are on the path to finding out and want to consider the topic of this book as relevant to their project. This text aims to help them understand whether it's worth picking up this book, what benefits they can gain from it, and what to pay special attention to. My opinion is subjective, but I hope it will help you better decide whether this publication is appropriate for your needs.

Before you read this book, remember that the author is an expert in research and testing, focusing mainly on aspects related to user analysis and research, not on product construction or interface design. You'll find a short section about aesthetics and its role, but the musings on this topic are shallow. She refers to convenient excerpts from authorities' opinions without delving into the matter. She doesn't look at practice, which repeatedly shows that aesthetics are important. My clients want attractive interfaces because they look at a given application all day, and they still provide reliable feedback regarding functionality. A good-looking interface will never mislead them. Therefore, in my opinion, aesthetics is an important element in practice. You'll learn more in the rest of the review.

I have been writing this review along with the impressions that reading this book gave me, and I will continue in that order. This book is difficult to evaluate unambiguously, but I'll try to share my thoughts with you.

First Impression

I remember how optimistic I was when I ordered this book. I saw the subject matter and thought to myself: "How nice, maybe a decent publication on this topic has come out." I read the description and ordered it. When I unpacked the package, I noticed that the book has 500 pages. That surprised me. It's true, I didn't show much foresight at that moment, but I made up for it by putting on a brave face. I looked through the table of contents and decided that I could handle it; after all, I'm an engineer. The number of pages in the publication doesn't motivate one to read it, but I felt that it's a challenge worth taking. Besides, it's worth seeing what's happening on the Polish market and finding out whether the book brings something new to my professional practice.

I won't hide that I am a demanding person, especially regarding professional literature. I hope the book will be an inspiration for me, and maybe I'll learn something new. The truth is that there's no better source of knowledge than practical experience, but good literature can facilitate learning and help avoid mistakes that others have already made.

Upgrading Nomenclature

After briefly wondering whether someone tested the readability of the cover, I read the table of contents and realized that I use different terminology. I found out that what I've been doing for years as standard—collecting information about the project, market, business, interviews with users and the team—is called research in this book. Without this knowledge, I can't start the project or finish it at a level that meets the client's expectations. It seems natural to me in the case of such publications, but it may be surprising for people who are just starting their adventure with UX and UI.

Until now, working as a UX/UI designer, I didn't need to use all methodologies. Why? Due to the group of users of the designed application and the specificity of the projects I realized. However, it's worth staying up to date with literature and knowing what's happening in the industry, especially when it's written by such experienced people. Sometimes it happens that some methods become popular and widely used, even if they're not always necessary.

Tip for Juniors: Yellow color was printed on white paper. That's crying out for improvement. The contrast is too low. It's time to train in the basics of accessibility. Let's be honest—even on a high-quality monitor, yellow looks blurry. It must be sufficiently darkened to meet the standards. In design practice, it's not just about aesthetics but also about accessibility. Without adequate contrast, users may have difficulty using the interface. Remember, UX is not only about functionality but also about user comfort for everyone.

Initial Criticisms

Reading the first chapter, I had the impression that the given example was practically copied from some book. I point this out because I didn't notice a footnote, and the way it was presented misled me. The authors presented it as if it were theirs. I also found examples that were simply slightly altered. Moreover, the story repeated that supposedly after the research, the author lost a friend when he heard the uncomfortable truth. For me, that's too much of a coincidence. Check out the publication—UX Strategy: How to Devise Innovative Digital Products that People Want. Such inconsistencies can raise doubts about the reliability of the presented content, especially when someone expects solid and well-documented knowledge.

A mention about design thinking. It's not at all a new field. I attended such workshops years ago. It's just that now more people know about it, and the topic has become more popular and trendy. The beginnings of this field date back to the 1950s, so it's not something groundbreaking. You can read more about it in the book What is Design Thinking? by J. Stanford and E. Siminoff. Nevertheless, it's worth knowing different perspectives on the topic to choose the best approach for your projects.

If you're frowning now and think I'm being too picky because such things can be overlooked, I'll remind you that I'm a UX/UI designer, and UX obliges. I can't let go when I notice mistakes that can mislead people. In UX work, it's about details and striving for perfection, including the reliability of the information on which we base our design decisions.

Diverse User Types

Continuing. The author discusses various types of users. However, there are many more than those described in the book. While reading, I have the impression that the publication is a compendium of possibilities. However, it doesn't oblige anyone to use all methodologies. Many good practices are listed. Thanks to them, you'll learn to ask questions during interviews and better understand users' needs. The publication is somewhat idealized because a small number of projects apply all the included good practices. However, it's good to be aware of the possibilities and tools you can use.

These are guidelines you can follow to be confident that you'll make good design decisions later. It's worth bearing in mind that every situation is different, and applying all practices at once may simply be inefficient. Analysis of existing data can provide product creators with a better understanding of the business context, get to know the target group, or the language they use, but also discover the direction of development and possibilities for product optimization. In the work of a UX designer, it's important to skillfully balance various elements—not always do you need to use all the tools that are available.

Reflection: Very often in the work of a UX designer, I have to reconcile the needs of the user and the business. It's necessary to design features for which the user is willing to pay. Not always what users say they want is what they really need, and finding that balance is one of the more challenging parts of this job.

While reading further, I noticed that the authors include quotes and statements from recognized names in the UX world. This is a pleasant surprise. It introduces a certain level of authority to the text and gives the feeling that the presented information is supported by the experience of other experts.

I previously mentioned that the book can be a compendium of knowledge. However, during reading, imperfections appeared. I estimate 80% reliability. Nevertheless, I still consider the publication a good start for a junior. It's worth remembering that beginnings in this field can be difficult, but appropriate literature can certainly help.

Subsequent Chapters and Impressions

Reading further chapters, I have the impression that sometimes general standards are not described but conclusions based on a specific sample of users. I miss the characteristics of these samples to have a reference. Nationalities are mentioned here and there, and some observations, according to my experience, are not only characteristic of race or nationality but also of professional profile. This is an aspect that could be better developed so that the reader can understand the context in which the research was conducted.

Another set of impressive quotes. The authors have thoroughly studied foreign literature, which adds value to the book, but I still miss more detailed descriptions of the research context. Without that, it's hard to relate to their universality. Let's remember that culture and environment have a huge impact on user behavior.

On Aesthetics

UX designers often criticize aesthetics. I hear in interviews that "paper accepts anything," and in my portfolio, there are only pretty pictures. I've corrected the work of more than one UX designer because their projects weren't functional. In reality, when you design a web application, aesthetics is only 25% of the work. Where's the rest? Another 25% is research, and the remaining 50% is UX design. Personally, I believe that the projects I've done so far didn't even need a UI designer because, in the vast majority, they are tables. In this situation, it's crucial to properly select colors and fonts available in the design system. There's no room for illustrations or a large number of animations because they will simply interfere.

"Attractive things work better... When you wash and wax your car, it drives better, right? Or at least that's how it seems to us." — Don Norman. The same is written by the author of UX laws. Maybe this principle applies to a car. Don Norman very often cites examples of UX from everyday life to better explain this issue. However, a steering wheel is a steering wheel, and an interface is an interface. You'll design a car differently than a chair. Design principles vary; you can compare them to illustrate, but we're still aware of the differences between the two objects. The same applies to interfaces. The quote isn't entirely true. I also wrote about this in my earlier review of the book UX Laws.

I don't exclude that I read quite an interesting dissertation on aesthetics. If someone says that what's pretty isn't functional and can't be functional, then they know little about design or aesthetics. You can reconcile both issues. I've had many teams where they evidently got used to my projects—you can get used to caviar. Therefore, ultimately I gathered reliable feedback regarding functionality. What looks good can also work well, but it requires a balance between aesthetics and functionality. Additionally, not everyone likes everything. What one considers beautiful, another may regard as a scribble.

The topic of aesthetics surprised me. I expected mainly research, but I'm glad that the subject of aesthetics was addressed. It was hard to read this book so far because it's a collection of methods from foreign publications in one place. I'd already read them earlier, and it's difficult to read a translation of the original. Personally, I rarely return twice to the same book. But I didn't give up. I paid for it, so I'm reading on. The money can't go to waste.

Improper Team Work Management

I like the statement: "Once again, it is confirmed that tight deadlines are the biggest enemy of user experience" (p. 401). This sentence perfectly reflects the problems that many UX designers face, especially in the context of cooperation with other departments such as developers or project managers.

The quote obviously refers to conducted research but very well reflects the role of the UX/UI designer in a project. I wonder how much money clients will waste before they conclude that this is a bad practice. Both research and designing mockups are connected vessels. If there's no time for discussions, brainstorming, wireframing, and later designing high-fidelity mockups and prototypes, then tests will be pointless and off-target. The team will later correct obvious errors that could have been spotted at the design stage. I'll mention that at every stage of design, there are corrections. Therefore, no stage should be skipped. Unless someone has time and money for a developer to correct not only twice but three times the same fragment of the interface.

Summary

The book Research as a Foundation for User Experience Design is a useful publication, especially for people just starting their journey with UX. Although I came across some flaws, such as the lack of exact footnotes and slight misrepresentations of some examples, the content offers a solid foundation for understanding UX research. It's a compendium that can help in better understanding users, especially for juniors. However, it's worth remembering that not all methods and practices are necessary in every situation, and in UX work, it's extremely important to adapt actions to the project's context.

Reading this book is a good start, but I encourage you to reach for other publications afterward, which will allow for a better understanding of the practical aspect of UX design. The knowledge gained from this book is only the beginning of the journey—we learn the most in practice, working on real projects and adapting our approach to the needs of both users and business.

I found a few good ideas in this book to improve my work. Or maybe not? Maybe I just refreshed my memory?

But perhaps the best is the last page. I agree with the last line. It was worth reading the other 489 pages for it.