Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design [Hardcover]

'Software for Use' embraces the key principles of usability in a very pragmatic way. The book is also 'in tune' with trends in the field of usability: moving to a more collaborative team model; addressing usability as a proactive design process rather than a reactive QA function; rethinking technology, tools, & techniques for the purpose of delivering user-centric software products - these are all fundamental aspects of how usability is maturing as a discipline.

One of things I enjoyed most about the book, was its hidden gems of wisdom embedded in each chapter. For example, in discussing the issues of marketability versus usability, the authors offer this simple maxim: "Design for use; refine for sale.... It is almost always far easier to make a functional but unaesthetic system attractive, than to take an attractive but impractical system and make it work."

If I had any criticisms about this book, there would be only one. As with many of today's practical guides, I find there is a recurring challenge with terminology. It is sometimes difficult to identify terms that are 'standard' versus those being introduced by the authors as new. As practitioners we rely heavily on the clarity of words to communicate tasks and deliverables. When applied terms are unfamiliar in context and origin, or they suggest double meaning, we introduce cost and confusion to the process of communication. This is not so much a criticism of the book as it is an observation of humankind, and our struggle to expand the English language.

As the authors themselves note, 'usability is not rocket science,' but it takes time and effort to achieve. Usability needs to be experienced before it can be standardized within an organization. That is why 'Software for Use' is such a good book - it is an experiential guide.

You might expect that anything from Larry Constantine would be terrific and again he - this time with equally adept co-author Lucy Lockwood - hasn't let us down. SfU (as it seems to be called in the chat groups) addresses one of the most under-addressed issues in our industry: Why is so much potentially useful software in fact useless because of its appalling user interfaces?

There are lots of valuable topics in this book. But probably the most valuable thing that I got from the book was a methodical approach to developing user interfaces, through the user role maps, task models, essential use cases, use case narrative, tools and materials and ... well, perhaps you should read the book!

If you're in the mood for some edutainment (i.e. cheap laughs while learning something handy), read the section on Web wisdom. There you'll find some wonderfully silly interface designs to avoid on your next e-commerce project.

Bottom line: I'll bet this book's on the way to becoming a classic. It's a "must read" for every software developer involved in any way with software that's meant to be used. And if you're actually charged with developing user interfaces, I'd say it's a "must own".