I really don't read a lot of books anymore. But I would, if I had the time to digest.

Gave me the vocabulary for affordance and the patience to ask whether a thing's shape matches its intent. Still the clearest single book on the difference between a thing that works and a thing that feels like it should.

Did the job of three larger books. Made it OK to do less research, better, and to stop apologising for that publicly.

Changed how I behave in design reviews. The framing — that the decision is a conversation with people who do not share your context — is something I now do without thinking about.

The original design system. The interesting thing is not the patterns. It is the discipline of naming a recurring decision so it can be reused without being copied.

The book I reach for when the same symptom keeps coming back wearing different clothes.

Not about design. About what happens when planners stop noticing what is already working. Every product team I have worked with would benefit from reading the first three chapters.

The closest thing the product world has to a canonical text. I disagree with parts. The discipline of the argument is what stays.

The practical follow-on to Inspired. The opportunity-solution tree is the simplest tool I know for separating what you are doing from why.

The Basecamp method, written down. Whether or not you adopt the cycles, the chapter on appetite vs estimate has changed how I scope work.

The book I quietly hand to designers and engineers alike when their work is fine but a bit flat. Twenty small choices, well-made.

A polemic. Necessary. The argument that designers carry ethical responsibility for the products they ship is non-negotiable now.

For the moment a designer first ends up leading other designers. Honest about how much of the job is conversation, not direction.

For the unflinching stance on design ethics, and for the line that designers are gatekeepers whether they like it or not.

For arguing that research is just paying attention. Slow research, in particular.

For the writing itself. The way an essay can be a careful object.

For the daily practice of side projects as a way to stay honest about your own craft.

Decades of patient writing on design and the publishing industry. The blog still reads like the early web in the best sense.

For showing that the medium of software is more malleable than we treat it. Watch his talks once a year.

On how a design team functions when you stop trying to control it from the centre. The Etsy-era writing still holds.

For the slow, careful version of qualitative research. Thinking styles, mental models, listening sessions.

For making continuous discovery a habit, not a project. The interviewing-without-leading-questions discipline alone is worth it.

For the argument that empowered product teams are not a luxury, and for being specific about what "empowered" actually means.

For Shape Up, for jobs-to-be-done in its honest form, and for being one of the few product thinkers who writes like he is in the room with you.

For getting design systems to feel less like a deliverable and more like a discipline.

Where mentorship became something I could give back without it being a side hustle. I am currently a mentor there myself.

For taking interaction design seriously as a discipline when most of the industry was still arguing about whether it was one.

For carrying the older end of the design profession's memory. Even when you outgrow the chapters, the values stay.

The closest thing the current design community has to a state-of-the-craft gathering. The Friday-after-Config dip is real.

For making it normal to talk about being a product manager out loud, with other product managers, in public.

The Slack communities that keep the day-to-day questions of working designers from being lonely.

Wherever you are. The shape of the work in a place becomes legible inside a meetup faster than anywhere online.

For the people who still think structure is a design problem worth a whole conference about.

Twenty-plus years of careful writing on the craft. The standard against which I quietly measure any design writing.

The trade journal. Still useful for the depth of the long-form articles, even when the rest of the web has shortened.

The Medium publication, when you need a wide-angle scan of what the field is currently arguing about.

For the research-paper end of the field. Citation-worthy when you need to make a usability claim out loud.

When the question becomes performance, accessibility, or a specific Web platform feature. Almost always the primary source.

Even if you do not design for Apple platforms — the patience and care in the writing is worth the visit.

For the discipline of writing a system down to the point that other teams can use it without you in the room.

The source of truth when accessibility becomes a conversation. Bookmarked, used often.

For pattern reconnaissance — what apps in your category are actually doing right now, with screens to compare.

For the visual end of the field. Useful in small doses; less useful when used as the brief.

Adam Wathan and Steve Schoger's short takes are some of the best small-bites design lessons on the open web.

For design systems, atomic design, and the longer-arc thinking on how teams scale design.