Published: March 8th, 2016
The book starts off with a story from Eric, when his daughter was being rushed to the hospital and how hard it was to find information needed to get to the ER through his phone's web browser.
The authors then go through different scenarios where this kind of thinking has made a lot of people uncomfortable or unable to complete tasks because off
The key takeaways from this book for me are to start with stress cases, and work out from there. A system designed to be effective when there is a cognitive stress or physical issue will work just the same, or better for when there are no challenges for a user. Think through how your copy and design might be hard to navigate when going through a hard time. The cheery copy might not be welcomed, or the fun graphics might make the user feel worse about their conditions.
Far fewer of our conversations start with “how is this new feature supposed to make someone feel”
I highlighted a bunch of areas of this book, but some of my favorites are below:
Availability heuristic: the easier it is for you to think of an example of something, the likelier you are to think that thing happens frequently.
Whenever you’re asking someone to give you information or complete an action, you can never go wrong by telling them what you plan to do with the information, as well as how their actions may affect them later.
Wherever we turn, we find that the best solutions come from situations where working together isn’t just encouraged, but its actively built into a team’s structure.
We’re going to screw up. We’re going to learn from it. It’s only unforgivable if we don’t share what we learned.