Introduction

When I switched careers from psychology to design, I expected to leave one field and enter another. That is not what happened. The deliverables changed. Instead of assessments and psychological reports, I was making wireframes and prototypes. But the foundation was the same; figuring out how people think and behave. I was still working with human behavior, just through a different craft.

What surprised me was that many designers did not see it that way. In the design world, the focus seemed to be on craft, visual systems, and aesthetics. Psychology was treated as something for researchers, or something you mentioned to sound smart in a meeting, not as a core part of the design process.

For the first few years, I kept my master’s in psychology quiet. I was almost embarrassed by it, like I was a psychologist pretending to be a designer. I had it completely backwards.

Design = psychology

Every decision you make as a designer is a claim about how a person will think, feel, or behave. Where you put a button is a claim about where people look. What you show on an empty state is a claim about what people need when they feel lost. Whether you use a progress bar is a claim about how people experience effort. You are making these claims all day long. The only question is whether you make them with any understanding of how people actually work, or just with a gut feeling and a deadline.

Dieter Rams said it better than I can:

“You cannot understand good design if you don’t understand people; design is only made for people.”

— Dieter Rams

He was not being poetic, he was simply describing the job of a designer. Design without an understanding of people is just decoration. It might look good in a portfolio. It will fail in the hands of a real user with real habits, real emotions, and a real reason to be somewhere else.

What this means for you

Most design mistakes are not taste mistakes. They are psychology mistakes. Someone assumed users would understand an interface that made sense to the designer. Someone assumed people would change a habit because a better option was now available. Someone assumed that if they explained the new design well enough, users would come around. None of that is how people work, and all of it is in this book.

The book covers four areas. Your own head first, because the biases that warp what you build start before a user ever sees your work. Then the interface itself, because visual and structural decisions shape behavior whether you intend them to or not. Then your users, and what they bring with them before they touch anything you made. Then the organizations designers work inside, because bad incentives and groupthink kill good work long before it ships.

Each chapter takes one finding from psychological research, explains what it means in plain language, and what it means the next time you open a design file. Read it in order or skip around. But if a chapter title makes you slightly uncomfortable, that is probably the one to start with.