Don Norman published The Design of Everyday Things in 1988. It still appears on more UX job descriptions than tools released in the last decade. That's a useful signal: the best UX design books don't expire the way software does. The ideas in them—mental models, feedback loops, human cognition—predate every design tool you're currently using and will outlast whatever comes next.
The harder problem is knowing which books actually matter. Most reading lists in this field run to 30+ titles, half of which are tangentially related or included because someone famous wrote them. This list is shorter on purpose: books that practicing designers return to, titles that change how you work rather than how you describe your work.
How We Selected the Best UX Design Books
Three criteria determined what made this list:
- Author credibility: Written by practitioners or researchers who designed real things, not theorists describing design from a distance.
- Applicability: You can finish the book and immediately change how you approach your next project. Books that are intellectually interesting but practically inert didn't make the cut.
- Durability: The core ideas hold up despite changes in tools and platform trends. A book about Sketch workflows from 2015 isn't useful. A book about how people process visual information from 2010 still is.
Books are listed roughly in order of how foundational the content is. New to UX? Start at the top. Several years in? The research and psychology titles are where most practitioners find the biggest gaps in their knowledge.
Best UX Design Books for Beginners
Don't Make Me Think by Steve Krug
The shortest and most practical book on this list. Krug's argument is that good usability means users never have to think about what to do—they just do it. The examples skew toward web design, but the logic applies to any interface. At around 200 pages, you can read it in a few hours and apply the ideas the same week. Most usability consultants who've been practicing for 15 years would still recommend this as the first UX book for someone new to the field. Read the third edition; the updated examples are worth it.
The Design of Everyday Things by Don Norman
Norman's book isn't really about screens—it's about the principles that make any designed object intuitive or confusing. Affordances, signifiers, feedback, constraints, mappings, conceptual models: these are the vocabulary of UX reasoning. If you've ever caught yourself trying to explain why a design doesn't work and struggled to articulate it, this book gives you the language. The 2013 revised edition added a section on digital design that doesn't feel forced. This is required reading before any design review where you need to make a structured argument rather than an aesthetic one.
The Elements of User Experience by Jesse James Garrett
Garrett's five-planes model—strategy, scope, structure, skeleton, surface—gives beginners a mental map of UX as a discipline. It explains why "make it look better" misses the point, and why UX problems often have roots several layers below what's visible on screen. The book is short and the diagrams carry most of the weight. Its main value is in establishing shared vocabulary with non-designers: project managers and developers who read it tend to have far more productive conversations with UX teams afterward.
Best UX Design Books for Research and Process
Just Enough Research by Erika Hall
Hall's book is a corrective to two bad tendencies in UX: doing no research at all ("we'll just test it later"), and doing so much research that nothing ships. She's practical and opinionated about what types of research actually produce decisions versus what produces reports nobody reads. The chapter on organizational research—understanding the company you're designing within—is something almost no other UX book covers. If you're a designer who does your own research rather than handing it off to a dedicated researcher, this is the highest-leverage book on this list.
Sprint by Jake Knapp, John Zeratsky, and Braden Kowitz
Sprint documents the five-day design sprint process developed at Google Ventures: Monday to map the problem, Tuesday to sketch solutions, Wednesday to decide, Thursday to prototype, Friday to test with real users. The process has been widely adopted and widely misapplied—teams often compress it or skip the user testing day, which defeats the purpose. Reading the book gives you the reasoning behind each step, which makes it easier to hold the structure together when someone in a meeting suggests "can we just do this in two hours?" The book reads quickly and the format is practical.
Lean UX by Jeff Gothelf and Josh Seiden
If you work in a product team that runs sprints or uses agile development, this book explains how UX fits into that context—or how it should. Gothelf's framework centers on assumptions, hypotheses, and validated learning rather than deliverables and sign-offs. The tension it addresses is real: traditional UX processes produce artifacts (wireframes, specifications) that agile teams don't have cycles to wait for. Lean UX describes how to work in shorter loops, test earlier, and deliver continuously. The third edition covers remote-first teams, which makes it more immediately applicable than older copies.
Best UX Design Books on Psychology and Behavior
100 Things Every Designer Needs to Know About People by Susan Weinschenk
Weinschenk is a behavioral psychologist, and this book is a catalog of cognitive science findings translated into design implications. Each chapter covers one finding: how people read on screens, how attention works, what drives trust, how memory affects navigation. Some are well-known (the Gestalt principles, Fitts's Law), many are less familiar but directly applicable. The chapters are short and self-contained, which makes this more useful as a reference than a cover-to-cover read. If you're doing design reviews and want to argue from evidence rather than preference, this is the book to cite.
Hooked: How to Build Habit-Forming Products by Nir Eyal
Eyal's four-step cycle—trigger, action, variable reward, investment—explains why certain products become habitual. It's primarily aimed at consumer app designers, and the examples are heavy on social media and games. The book has drawn criticism for enabling manipulative design patterns, and Eyal addresses this only partially. It's worth reading because the framework is analytically useful even if you disagree with its applications: understanding what makes a product habit-forming helps you recognize when you're engineering compulsion versus genuine utility. The ethical line isn't drawn for you, which is actually one of the book's more honest qualities.
Articulating Design Decisions by Tom Greever
Most UX books focus on making good design decisions. This one focuses on explaining them to people who weren't in the room. Greever's central argument is that a good design you can't defend will lose to a mediocre design someone can articulate with confidence. The book covers listening to stakeholders, understanding what they actually need versus what they're asking for, and structuring design presentations to make approval more likely. It's particularly useful for designers working inside organizations where they don't control the decision-making process—which is most designers, most of the time.
Top Courses to Pair with Your UX Reading
Books build judgment; practice builds skill. These courses cover technical and visual areas that complement the conceptual groundwork above—particularly for designers who collaborate closely with engineering teams or need to strengthen execution skills alongside their design reasoning.
How to Create Bestselling Kindle Ebook Covers - Series 1
Covers visual hierarchy, typography, and composition in a context where design decisions directly affect commercial outcomes—the same principles that govern strong UI work, applied under real constraints.
The Best Node JS Course 2026 (From Beginner To Advanced)
UX designers who understand how server-side logic and data flow work write more precise specs and have fewer revision cycles with engineering teams; this 9.8-rated course builds that foundation from scratch.
API in C#: The Best Practices of Design and Implementation
Understanding API design patterns helps UX designers reason more clearly about error states, loading behavior, and data latency when documenting interactions—the gaps that cause the most friction in developer handoff.
FAQ
What's the single best UX design book to start with?
Start with Don't Make Me Think by Steve Krug. It's the shortest, most immediately applicable book on the list. You can read it in an afternoon and leave with a working framework for evaluating usability. The Design of Everyday Things is more foundational theoretically, but Krug's book produces actionable results faster for someone new to the field.
Do UX design books go out of date?
It depends on the type. Books about specific tools—Sketch workflows, Adobe XD tutorials—date quickly. Books about human cognition, research methods, and design process age much more slowly. Norman's book from 1988 is still relevant because human psychology hasn't changed. The books on this list were selected partly for durability. Avoid lists that include recent tool-specific guides alongside conceptual classics without distinguishing between the two.
Is The Design of Everyday Things still worth reading in 2026?
Yes. The core concepts—affordances, signifiers, feedback, conceptual models—are the vocabulary every UX designer needs. The first few chapters alone will change how you think about design problems. Read the 2013 revised edition rather than the original (which was titled The Psychology of Everyday Things). The revision adds material on digital design without diluting the original content.
What's the best UX book for user research specifically?
Erika Hall's Just Enough Research is the most practical option for working designers. It's opinionated about what research actually influences decisions and cuts through the academic framing that makes other research books feel disconnected from practice. If you want more depth on qualitative techniques specifically, Steve Portigal's Interviewing Users is worth adding alongside it.
Should I read UX books before or after taking a course?
Courses are better for learning tools and processes; books are better for developing judgment. The most effective sequence: start with one or two foundational books (Krug and Norman are the right choices), take a course to build hands-on skill, then return to the research and psychology books once you have real design work to apply them to. Reading 100 Things Every Designer Needs to Know About People after you've done actual design work produces insights that reading it cold wouldn't.
Are there good UX books specifically for mobile or app design?
Mobile-specific books tend to date quickly as platform conventions change. A more durable approach is to read platform-agnostic titles (Krug, Norman, Weinschenk) and supplement with Google's Material Design documentation and Apple's Human Interface Guidelines, both of which are regularly updated. These are more current and authoritative on mobile-specific patterns than any book published more than two or three years ago.
Bottom Line
The best UX design books on this list aren't interchangeable, and reading them in the wrong order wastes time. Krug and Norman are foundational—read them early, before you've developed habits that are hard to unlearn. Hall and Greever address gaps that most practitioners develop over time: how to research without it becoming its own deliverable, and how to communicate design decisions to people who weren't part of making them.
If you're building a reading list from scratch, start with Don't Make Me Think, then The Design of Everyday Things, then pick your next book based on where your current work is exposing specific weaknesses. That's more effective than reading all ten sequentially before touching a real design problem. The books are most useful when you have actual work to test them against.