← All Writings Essay II  ·  Reading List

The Designer's Library: Essential Reads

March 2025  ·  11 min read

Every profession has its canonical texts. Designers, thankfully, have a genuinely compelling body of literature — and the four books here represent some of the best of it. These are not books you read once and shelve. You return to them at different career stages and discover they have changed, because you have.

FOUNDATION The Design of Everyday Things Don Norman 1988 / 2013 01 ENTRY LEVEL UX for Beginners Joel Marsh 2016 02 INTERMEDIATE Don't Make Me Think Steve Krug 2000 / 2014 03 PRACTICE Solving Product Design Exercises Artiom Dashinsky 2018 04

Four books · four stages of a designer's growth

01
The Design of Everyday Things
Don Norman  ·  1988, revised 2013

Don Norman's foundational text changed how an entire generation of designers thinks. It introduced the "Norman Door" — any door that, through no fault of the person trying to open it, is simply impossible to figure out. If you've ever pushed when you should have pulled, you've had a Norman moment.

"Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible." (Norman, 2013, p. 3)

When something goes wrong between a person and an object, the fault almost always lies with the design, not the person. Norman gives designers a precise vocabulary to diagnose exactly why: affordances (what an object lets you do), signifiers (what communicates how), feedback (what confirms you did it), and conceptual models (the mental picture a user builds). Read the 2013 revised edition — it's sharper on the affordance/signifier distinction.

Foundational theory Affordances Human factors Essential for all levels
02
UX for Beginners: A Crash Course in 100 Short Lessons
Joel Marsh  ·  2016

One hundred short lessons, each under four minutes, each making exactly one point clearly before getting out of the way. Joel Marsh's book is the antidote to the bloated design-theory genre.

"Good UX is invisible. Bad UX screams at you." (Marsh, 2016, p. 12)

Particularly strong on the psychology side — cognitive load, mental models, decision fatigue — all in plain language without losing substance. The chapters on why users don't read and on the gap between what users say and what they do are worth the price alone. This won't make you a senior UX designer, but it will give you the vocabulary and curiosity to become one.

Beginner-friendly Psychology of UX Fast to read Research and design basics
03
Don't Make Me Think: A Common Sense Approach to Web Usability
Steve Krug  ·  2000, revised 2014

Steve Krug's book has been in print for over two decades, which is an extraordinary thing for any technology-adjacent text. The reason is simple: it is about human behaviour, not technology, and human behaviour has not changed much since 2000. People still scan pages rather than read them. People still click the first vaguely plausible option they see rather than reading all available choices. People still blame themselves when a website is confusing, rather than blaming the website. All of this was true in 2000, and all of it is true today.

"It doesn't matter how many times I have to click, as long as each click is a mindless, unambiguous choice." (Krug, 2014, p. 41)

The title is also the central principle. When a user has to stop and think about how to use something, the designer has already lost. The goal of good web usability is to make every decision on every page so obvious that the user's brain can operate on autopilot, reserving its actual cognitive resources for the things that matter. Figuring out where the navigation is should not be one of those things.

Krug is also one of the best writers in the field, which is a rarer quality than it should be. His prose is direct, self-aware, and occasionally very funny. The chapter on usability testing is among the most practical pieces of writing I have encountered on the subject. His core argument, that any organisation can run meaningful usability tests with almost no budget, is correct and actionable and still under-practised in teams that really should know better.

The third edition, updated in 2014, includes a section on mobile usability that brings the book squarely into contemporary relevance. Read this one early, re-read it before any major project, and keep it somewhere visible as a reminder that the person using what you build is not you.

Web usability Cognitive load Usability testing Quick read, lasting value
04
Solving Product Design Exercises
Artiom Dashinsky  ·  2018

This book occupies a different position in the list from the previous three. It is not a work of design theory. It is, in the most practical sense, a rehearsal guide for the design interview process. And it is a genuinely good one.

Dashinsky's book grew from a straightforward observation: design interviews increasingly ask candidates to solve open-ended product design problems on the spot, and most candidates, no matter how good their actual design skills, have never practised that specific type of thinking under that specific type of pressure. The book addresses this gap directly, offering frameworks for approaching product design challenges and a series of exercises with detailed worked solutions.

"The goal of a design exercise is not to find the perfect solution. It is to demonstrate a structured way of thinking." (Dashinsky, 2018, p. 23)

What makes the book valuable beyond interview preparation is the underlying discipline it teaches: how to decompose an ambiguous design problem into a structured process that produces coherent output in a defined amount of time. This is, in fact, what senior designers do every day in contexts far less formal than a job interview. The ability to receive a vague brief, ask the right clarifying questions, identify constraints, and propose a direction with confidence is a professional skill, not just an interview skill.

The book is most useful for designers who are early in their careers or returning to the job market, but the framework it teaches has broader application. Treat it as a method for thinking rigorously about product problems. The interview preparation is a welcome side effect.

Interview preparation Product thinking Structured problem-solving Portfolio building

A Note on Reading as a Practice

Reading design books is not a substitute for designing things. The person who has read every book on this list but has never shipped anything is considerably less equipped than the person who has shipped three projects and read none of them. Theory without practice is interesting conversation at best.

What books do, at their best, is give you language for things you have already half-understood from experience. They make tacit knowledge explicit. They let you name what you have been doing intuitively, which makes it easier to teach, to defend, and to apply deliberately the next time.

Read these books slowly. Argue with them when they are wrong, which they occasionally are. Return to them when your practice has changed and see what they have to say to the designer you have become. That is, in the end, what the best books do. They do not tell you what to think. They give you better tools for thinking with.

References

Dashinsky, A. (2018). Solving product design exercises: Questions and answers for designers preparing for interviews. Artiom Dashinsky.

Krug, S. (2014). Don't make me think, revisited: A common sense approach to web usability (3rd ed.). New Riders.

Marsh, J. (2016). UX for beginners: A crash course in 100 short lessons. O'Reilly Media.

Norman, D. A. (2013). The design of everyday things (Revised and expanded ed.). Basic Books.

← Stakeholder Management The Three Levels of Design →