I'm a dev and recently picked up "The Design of Everyday Things" as an attempt to become more design-oriented. Everyone raves about this being like the bible of design.
So far I'm about 80 pages in and have found it extremely academic and not very practical, sometimes deriving conclusions that are so far from reality that they are a bit concerning, like how a strong password does not matter because once they inevitably leak they can always be cracked via rainbow tables (the author doesn't use this exact term). As we know the exact point of a strong password is that it will not be in a rainbow table.
Of course the original version is pretty old but I picked up the latest revised version. Still some interesting insights and I haven't given up on the book quite yet but it's been a ton of theory and a lot of terminology so far.
My two cents as a 20 year product manager with +10 enterprise applications under my belt (and having read several of these):
# "Don't make me think" is a seminal work on design thinking for online services. I've yet to come across a book with as much relevance and substance even though it was written for the dot com era.
# "Positioning" by Al Reis is a book I wish I read 15 years ago when I started my company... your product's strategic positioning will greatly inform and shape design decisions (typography, colors, tones, copy, etc)
# "Ogilvy on Advertising" - written by the legend himself, once you read this book, it will change the way you see all ads in any medium
Design thinking is a human-centered, iterative approach to creative problem-
solving, focusing on deeply understanding users' needs to develop innovative
solutions through phases like Empathize, Define, Ideate, Prototype, and Test.
Apparently. It's not immediately clear how it's different from your good old "regular" design.Design thinking is a scam. I once had to took part in a design thinking class (my company wanted that). The consultant clearly were just waiting to see what kind of ideas we would come up with for some product. If an interesting idea came up in their classes they would later try to monetize it. So basically you pay them so they get your product ideas for free.
I know it is more niche to the online/websites POV, but “Don’t Make Me Think” is a book that needs to be somewhere in the lines of “The Design of Everyday Things.” Of course, I re-read the latter as reminders and catch-up readings.
I’m not a game designer, but 15 years after initially reading it, Jesse Schell’s “The Art of Game Design: A Book of Lenses” really sticks with me in any product design context. Organizing your thoughts around the lenses presented in this book makes for productive discussion, and can turn subjective points (an example might be how frictionless or not a UI element might be) into more objective points. I suggest checking it out. The author posted a deck of the lenses here: https://deck.artofgamedesign.com
Noted couple of books.
I've been curating (mostly design) books on a digital library: https://links.1984.design/books
Tom Kelley and David Kelley, founders of Stanford's Design School and IDEO (the industrial design firm that made things like Apple's first mouse and the standup toothpaste tube) have a great book, Creative Confidence.
Here's their website for the book, along with some tools and useful instructional videos https://www.creativeconfidence.com/tools/
If anyone's interested in how environment shapes behavior: I wrote "Leave the Door Open." It's about designing spaces that reduce isolation and relax the nervous system.
Based on research like the Rat Park experiments showing environment beats willpower. Practical room-by-room changes.
The Substack for Open Enough Design is here: https://OEDmethod.substack.com and you can find a link to the book there too.
Please don’t use Design Thinking.
Design Thinking is a subset of Systems Thinking (this is the polite interpretation). Design Thinking does with its sole existence what Systems Thinking tried to avoid: Another category to put stuff into, divide and conquer. It is an over-simplified version of the original theories.
Better: Jump directly to Systems Thinking, Cybernetics and Systems Theory (and if measurements are more your thing, even try System Dynamics).
I can only recommend that anyone interested in this topic take a look at the work of one of the masters of Systems Thinking, Russel Ackoff:
https://m.youtube.com/watch?v=9p6vrULecFI
This talk from 1991 is several dozen books heavily condensed into one hour.
(Russell Ackoff is considered one of the founders of Operations Research and ironically came to be regarded an apostate as he tried to reform the field he co-founded. He subsequently became a prominent figure of Systems Thinking)
My 2c. I'll show myself out.
I like how the author correctly shown the cover image for the "The Sciences of the Artificial", with plural 's' in 'sciences', but then in the paragraph praising it gleefully ignored it.
Probably means this article wasn't written by AI!
I will add : "The Design of Design" by Fred Brooks (of The Mythical Man Month fame)
I love 101 Things I Learned at Architecture School.
It's a very light, approachable book, dealing with surprisingly universal principles. Also it has very nice pictures.
Most of it also applies to game dev, and to the design of experiences.
What most people fail to realise is something quite simple about “design” - it’s the discipline of bridging human behaviour and “things” (be that objects or software).
Don Norman’s book covers a lot on human behaviour, which is the correct lens through which to view “design”.
It seems that I have learned to distrust websites that show ads.
I don't think there's nothing wrong with wanting to get paid via ads. But I don't see why a list of "design thinking" books should be some piece of info that you should be paid for.
At least there's an author to the article I guess
I was very disappointed when I learned that this wasn't about designing books that think.
[dead]
Design Thinking is the Data Science of UX: an attempt to gain influence in fields that you don't have expertise in.
Even though there might be universal design principle that can be applied in many fields, the Design Thinking people think that they can just come in and design user interfaces, etc. without really having an expertise in the particular field.
Design Thinking works for selling consulting and not much else. Nobody wants another Agile(TM) process imposed on software developers (in my particular case) that attempts to turn developers into factory line workers.