What do you think?
Rate this book
A Book Apart #18
Design for Real Life
You can’t always predict who will use your products, or what emotional state they’ll be in when they do. But by identifying stress cases and designing with compassion, you’ll create experiences that support more of your users, more of the time.
Join Sara Wachter-Boettcher and Eric Meyer as they turn examples from more than a dozen sites and services into a set of principles you can apply right now. Whether you’re a designer, developer, content strategist, or anyone who creates user experiences, you’ll gain the practical knowledge to test where your designs might fail (before you ship!), vet new features or interactions against more realistic scenarios, and build a business case for making decisions through a lens of kindness. You can’t know every user, but you can develop inclusive practices that support a wider range of people. This book will show you how.
Join Sara Wachter-Boettcher and Eric Meyer as they turn examples from more than a dozen sites and services into a set of principles you can apply right now. Whether you’re a designer, developer, content strategist, or anyone who creates user experiences, you’ll gain the practical knowledge to test where your designs might fail (before you ship!), vet new features or interactions against more realistic scenarios, and build a business case for making decisions through a lens of kindness. You can’t know every user, but you can develop inclusive practices that support a wider range of people. This book will show you how.
132 pages, Paperback
First published March 8, 2016
30 people are currently reading
1503 people want to read
About the author
Eric A. Meyer
57 books51 followersEric A. Meyer is an American web design consultant and author. He is best known for his advocacy work on behalf of web standards, most notably CSS (Cascading Style Sheets), a technique for managing how HTML is displayed. Meyer has written a number of books and articles on CSS and given many presentations promoting its use. Eric currently works for Igalia.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 47 reviews
April 9, 2016
I cannot recommend this book highly enough. If your work involves any form of design, please read it. We need to do better. Sara and Eric present the case for compassionate design in a way that is impossible to ignore, and they give several practical frameworks for thinking about hard problems and selling the answers on to your stakeholders.
The concept of "stress cases" is the most useful design principle I've encountered in a long time, and is changing the way I think about my work.
Buy this book, read it, and then drop it off at your bank or insurance company or local government office or neighbourhood startup – there's a good chance they need it too.
The concept of "stress cases" is the most useful design principle I've encountered in a long time, and is changing the way I think about my work.
Buy this book, read it, and then drop it off at your bank or insurance company or local government office or neighbourhood startup – there's a good chance they need it too.
May 29, 2018
Lots of crazy stories and lessons learned (e.g. Facebook's Year in Review) plus resources to avoid similar traps.
Favorite concepts:
1. Conduct a 'premortem' exercise as part of research and discovery. Inform the team that the project has somehow failed spectacularly. Everyone then independently writes down every reason they can think of for the failure.
2. There are basically three business cases for anything – it will make money (distinguish from competition), it will save money (cut operating costs), or reduce risk (avoid backlash, lose trust, etc). Use these as a focal point when making the case for anything that needs support.
3. When talking to customers, focus on desired actions rather than describing things. "People might be bad at describing specific products or ideas on the fly, but they're excellent at communicating what they wish their lives felt like."
4. Assign a 'designated dissenter' within your team to avoid groupthink for design decisions.
5. Always consider stress cases (time-sensitive actions, traumatizing circumstances, etc).
Favorite concepts:
1. Conduct a 'premortem' exercise as part of research and discovery. Inform the team that the project has somehow failed spectacularly. Everyone then independently writes down every reason they can think of for the failure.
2. There are basically three business cases for anything – it will make money (distinguish from competition), it will save money (cut operating costs), or reduce risk (avoid backlash, lose trust, etc). Use these as a focal point when making the case for anything that needs support.
3. When talking to customers, focus on desired actions rather than describing things. "People might be bad at describing specific products or ideas on the fly, but they're excellent at communicating what they wish their lives felt like."
4. Assign a 'designated dissenter' within your team to avoid groupthink for design decisions.
5. Always consider stress cases (time-sensitive actions, traumatizing circumstances, etc).
April 5, 2018
Good, but a lot of the same content as Technically Wrong. Pick one or the other, there's no reason to read but. Design for Real Life is targeted more at designers whereas Technically Wrong has a more general audience.
March 28, 2018
This gave me flashbacks to the time I had to explain miscarriages to a bunch of dudes building a baby registry app. I found it hilarious that they suggest the "designated dissenter" who looks for edge cases should rotate among the team members, so nobody hates one particular person, since raising risks in software is my full-time job.
May 25, 2022
The examples of how companies/services failed with their users are mind-blowing and questionable as to how they screwed up so bad.
The most valuable takeaway is to think of edge cases as 'stress cases'. The book advocates for common-sense practices that are now, more 0r less, currently part of the mainstream design mentality. This was likely a valuable read in 2016. But from a 2022 perspective, this is preaching to the choir.
The most valuable takeaway is to think of edge cases as 'stress cases'. The book advocates for common-sense practices that are now, more 0r less, currently part of the mainstream design mentality. This was likely a valuable read in 2016. But from a 2022 perspective, this is preaching to the choir.
November 2, 2016
A must-read for everyone making products for people. This book is powerful and I'll be re-reading it often to inspire compassion, think about pain points and broken flows, and people in crisis reading and interacting with websites and apps and really any software.
June 17, 2022
"The problem isn’t just inappropriately peppy copy. It’s all kinds of things: the airline that pushes so many competing and confusing messages at users that buying a ticket in an emergency becomes an exercise in frustration and failure. The form that asks for information about sensitive subjects without explaining why the service needs it or how it will be used. The hospital interface that emphasizes its world-class doctors but doesn’t tell you how to find the emergency room."
I was reading this book intermittently as an additional learning resource for my Masters in Web Design programme.
This book absolutely rocked my world. I read half as preparation before a presentation for my Major Project, in which we had to build User Personas, think about our audiences, etc. Stuff that is covered a lot in this book.
Taking the lessons I learned from just that one half, I was able to make a presentation that my professors were pleased to hear. I had quotes I pulled directly from the book to explain why I was using specific terms for the class, as this was recommended reading but most people probably didn't get around to reading it yet.
My classmates poked fun at me as I was (albeit, enthusiastically) exclaiming about the different stories and lessons in this book, the more kind decisions in design that make SO MUCH SENSE once you see it written out but no one thinks to do it!! But it really changed the way I thought of things on the web.
This is a useful resource for anyone that is studying web design, and supplements of the lessons in this book can be used across the board, as compassionate design goes beyond the digital world.
I was reading this book intermittently as an additional learning resource for my Masters in Web Design programme.
This book absolutely rocked my world. I read half as preparation before a presentation for my Major Project, in which we had to build User Personas, think about our audiences, etc. Stuff that is covered a lot in this book.
Taking the lessons I learned from just that one half, I was able to make a presentation that my professors were pleased to hear. I had quotes I pulled directly from the book to explain why I was using specific terms for the class, as this was recommended reading but most people probably didn't get around to reading it yet.
My classmates poked fun at me as I was (albeit, enthusiastically) exclaiming about the different stories and lessons in this book, the more kind decisions in design that make SO MUCH SENSE once you see it written out but no one thinks to do it!! But it really changed the way I thought of things on the web.
This is a useful resource for anyone that is studying web design, and supplements of the lessons in this book can be used across the board, as compassionate design goes beyond the digital world.
October 29, 2017
There were times when this seemed very close to common sense, but it's obviously needed. Compassion isn't something that's always first nature for people, especially when they're on a deadline. I love the framing of "edge cases" as "stress cases."
One odd thing I found about this book (and writings about web standards back in the day) is that it tries to train people to be apologists for this kind of process. Why not just talk about its benefits and let people decide to do it either because it's the right thing to do or because it makes business sense (both of which cases are discussed) rather than to explain how to get buy-in at your company?
In any case, this book is full of great information and you should read it.
One odd thing I found about this book (and writings about web standards back in the day) is that it tries to train people to be apologists for this kind of process. Why not just talk about its benefits and let people decide to do it either because it's the right thing to do or because it makes business sense (both of which cases are discussed) rather than to explain how to get buy-in at your company?
In any case, this book is full of great information and you should read it.
December 20, 2021
An excellent introduction to compassionate design, full of tactics to add to your toolkit, but the lack of any real discussion around disabled people is uncomfortable. I felt like most examples focused around people having bad days due to injury, death, etc. -- the book should have had more examples from marginalized communities.
Also, the frequently used example of the period tracking app as being for women (when trans people are mentioned here and there in the book) feels like the authors could have benefitted from taking their own advice and challenging their own assumptions.
Also, the frequently used example of the period tracking app as being for women (when trans people are mentioned here and there in the book) feels like the authors could have benefitted from taking their own advice and challenging their own assumptions.
June 26, 2023
So applicable, especially today with the uptick in stress and anxiety, the fragility and uncertainty.
Remember, it is best to put your digital services (or any service for that matter) through a stress test. Can it be used easily and with little cognitive load, by a user, under the most stressful of circumstances? If a user is in a crisis, can your product be just a few simple steps away from a positive outcome? If so, than it shall pass favorably for all visitors.
Remember, it is best to put your digital services (or any service for that matter) through a stress test. Can it be used easily and with little cognitive load, by a user, under the most stressful of circumstances? If a user is in a crisis, can your product be just a few simple steps away from a positive outcome? If so, than it shall pass favorably for all visitors.
February 1, 2018
A very nuanced look at how design can effect a wide variety of people - particularly those who are considering edge cases in most senses of the phrase. The anecdotes were personal and moving. The advice was practical. The resources in the back... it's going to take me some time to get through them all, but I want to jump right in. A very good book!
April 7, 2021
I was looking for a book on CSS. Eric Meyer is the author of the most famous CSS reset script that I have been using since the 2000s. The book wasn't about CSS however, it ended up being about the design thinking for large public facing application.
Insightful and highly recommended if you plan to build an application that respects human limitations and diversity.
Insightful and highly recommended if you plan to build an application that respects human limitations and diversity.
May 16, 2017
An easy read that helps remind us that we need to be mindful of who are users REALLY are. While meant to be about web design, the lessons here are really valuable to any service profession (which is ultimately ALL of them).
I may have to buy a copy for myself - I read this through ILL.
I may have to buy a copy for myself - I read this through ILL.
July 26, 2018
This book is fantastic, whether you are a web designer, a content creator, or even just a consumer of information on the web. Just as accessibility makes things easier even for those without a disability, compassionate design makes life better for everyone.
June 11, 2019
We're so quick to build the latest app or software that we forget to be compassionate to our users. This book goes into how teams can incorporate good practices to provide a useful experience when times can be stressful. Just like we should design for emotion, when should design for compassion.
July 25, 2019
The book is nice — the first half in particular.
It does go on for a bit too long and repeats itself a lot in the second half.
Nonetheless, a very important topic for designers, worth the easy and short read 👍
It does go on for a bit too long and repeats itself a lot in the second half.
Nonetheless, a very important topic for designers, worth the easy and short read 👍
January 4, 2021
"No one is using our services in a truly ideal state: distraction-free, on the latest equipment, whole emotionally content, and with as much time as it takes." This book covers how to design for this reality.
August 6, 2017
more compassion in design
September 2, 2017
Inspiring. Practical. Especially appreciated the chapter on winning over the business.
September 3, 2017
Good on a new perspective. Bad on tactical recommendations.
October 27, 2017
Good walkthrough on how we all could add more compassion to our design and development processes.
November 1, 2017
Our users are not us. "Designing for real life" encourages to look beyond that ideal persona and ask question “How will someone in different context perceive it?” It explains how thinking through all stress-case scenarios, we can get better at prioritizing information, removing fluff, and stay focused on our users.
"WHEN YOU ASSUME, YOU MAKE AN ASS OF U AND ME."
"WHEN YOU ASSUME, YOU MAKE AN ASS OF U AND ME."
November 7, 2017
An excellent read! A must for everyone involved in designing and creating websites and apps.
January 13, 2018
The very best read on designing with compassion. Valuable for not just digital product design, but anything a human being will touch.
January 27, 2018
Highly recommend this book for all people who make digital products or services for others.
April 11, 2018
Incredibly important content but repetitive. I truly appreciate the author's taking their painful experiences and transforming them into powerful lessons for the web community.
May 18, 2018
Some good insights, but a few weak examples/conclusions.
January 9, 2019
"Be conservative in what you do, be liberal in what you accept from others!"
This book is full of many fabulous examples of this statement from Jon Postel.
This book is full of many fabulous examples of this statement from Jon Postel.
August 12, 2019
A good about, that open the mind to think outside the box, leaving in consideration that humans isn't perfect like personas.
June 20, 2020
This book is solid. Honestly, the first chapter might be the newest part of information for those who are well read in design but the entire book is a good read.
Displaying 1 - 30 of 47 reviews