Every few months a new "books every designer should read" list goes around. I bookmark most of them. I finish very few of the books.

That used to bother me. Now I think the list was never the point. Reading only helps when it changes the next decision you make, so I care less about how many books I get through and more about how I read the ones I pick.

Start with a problem, not a list

I get the most out of a book when I open it with a question from my current work. Why do people abandon this form halfway? How much should a dashboard show on first load? What makes an empty state feel like a dead end?

With a question in mind, I read differently. I skim the parts that don't apply yet and slow down where the author is talking about my problem. A chapter that answers a real question sticks far longer than a whole book read to tick it off.

Read across the craft, not just about it

Product design sits between a few disciplines, and the useful ideas often come from the edges:

  • How people think: perception, memory, attention, and how decisions get made under pressure.
  • How products get built: discovery, prioritization, and working with engineering and business constraints.
  • How words work: interface copy, structure, and writing that people can scan.
  • How visuals carry meaning: typography, hierarchy, and layout.

If everything I read is about interface design, my work starts to look like everyone else's. Reading a little outside the field keeps the thinking fresh.

Turn notes into something I can use

Highlights alone don't change much. After a chapter that matters, I write down one idea in my own words and one place I could try it: a flow to simplify, a label to rewrite, a question to ask in the next review. If I can't name where it applies, I probably didn't understand it yet.

Then I try it. An idea tested on a real screen teaches more than three more chapters.

Re-read the few that hold up

Most books give me one or two lasting ideas. A small number keep paying off every time I come back, because I'm a different designer with different problems on each reading. Those are the ones worth keeping close.

Where to start

If you want a curated starting point, Aaron James's Product design reading list on Bootcamp is a thoughtful one. Pick one book from a list like that, bring a question from your current project, and see what changes in your next design.