Defensive Design for the Web is an encompassing guide to creating successful error messages, help, forms, and other crisis points. This is an important subject as website visitors should find their way around whenever something goes wrong during their visit to a website.
The book is written as a series of guidelines that are illustrated using rich examples from real websites; this makes for an easy and interesting read. Each guideline can be studied separately and usually an immediate action will come from them.
Below is a list of the 40 guidelines provided in the book:
- Give an error message that’s noticeable at a glance
- Use color, icons, and text to clearly highlight and explain the problem area
- Always identify errors the same way
- Eliminate the need for back-and-forth clicking
- Don’t use language that might be unfamiliar to your customers
- Keep text brief and easy to understand
- Be polite
- Highlight either required or optional fields
- Accept entries in all common formats
- Provide sample entries, pull-downs, and formatting hints to ensure clean data
- Explicitly state limits to characters, number of entries, and so forth
- If customers can’t choose it, don’t show it
- Validate entries (as soon as possible)
- Button up: Eliminate the Reset button and disable the Submit button after it’s clicked
- Assist form dropouts by saving information
- Offer customized “Page Not Found” error pages
- Successfully redirect near-miss URLs
- Use ALT tags for images
- Don’t shut out visitors with old technology: Offer alternative versions and technology upgrade information
- Answer questions on the same page they arise
- Offer an easy-to-use “Help” section and provide clear links to it
- Let customers help themselves through online forums and training sessions
- Provide a human fallback plan (help via chat, phone, or email)
- Answer emails quickly and effectively
- Help login with tips or email
- Don’t disable the browser’s Back button
- Make it fast, not cute
- Don’t force registration
- Don’t block content with ads
- Eliminate unnecessary navigation during multi-step processes
- Offer a clear explanation when no results are found or inexact matches are shown
- Anticipate common errors and provide relevant results
- Too many results? Offer features that let searchers refine and filter results
- No results? Let customers easily expand search criteria
- Offer tips on how to improve results
- Don’t rely on advanced searches
- Be upfront about item unavailability
- If a product will be available at a later date, explain when, provide product details, and take advance orders
- Offer email notification
- Show similar items that are available
Book Description*
Let’s admit it: Things will go wrong online. No matter how carefully you design a site, no matter how much testing you do, customers still encounter problems. So how do you handle these inevitable breakdowns? With defensive design. In this book, the experts at 37signals (whose clients include Microsoft, Qwest, Monster.com, and Clear Channel) will show you how.
Defensive design is like defensive driving brought to the Web. The same way drivers must always be on the lookout for slick roads, reckless drivers, and other dangerous scenarios, site builders must constantly search for trouble spots that cause visitors confusion and frustration. Good site defense can make or break the customer experience.
In these pages, you’ll see hundreds of real-world examples from companies like Amazon, Google, and Yahoo that show the right (and wrong) ways to get defensive. You’ll learn 40 guidelines to prevent errors and rescue customers if a breakdown occurs. You’ll also explore how to evaluate your own site’s defensive design and improve it over the long term.
This book is a must read for designers, programmers, copywriters, and any other site decision-makers who want to increase usability and customer satisfaction.
Author Information*
Chicago-based 37signals is a team of web design and usability specialists dedicated to simple, and usable, customer-focused design. 37signals popularized the concept of contingency/defensive design in various articles and white papers and via the web site DesignNotFound.com. The team also has conducted workshops and presentations on the topic for a variety of conferences and companies.
37signals clients include Microsoft, Qwest, Monster.com, Clear Channel, Panera Bread, Meetup, Performance Bike, and Transportation.com. Work has been featured in the New York Times, Sports Illustrated, Washington Post, on CNN, and in numerous other publications. Team members have appeared as featured speakers at AIGA Risk/Reward, Activ8, South By Southwest, HOW Design Conference, ForUse, and other conferences. Additional information can be found at www.37signals.com.
This book is authored by Matthew Linderman with Jason Fried. Other members of the 37signals team include Ryan Singer and Scott Upton.
* Information from publisher website