I wasn't quite sure what to expect in getting this book. As an experienced UI person, there is the constant juggle of documentation versus development. You can work with developers in an Agile environment on the fly, but what does QA test to? I was hoping this book addressed this new age question. It most certainly does not. But that is my mistake as this book does not suggest that will do that. Instead, I found a fairly basic book on UI, that deals with the earlier stages or more basic stages of UI development and how to document that.
Imagine you are a consultant or a UI person looking into a new website or application, or reviewing an old site to resolve some issues. It is this level of early documentation this book is discussing:
*Personas
*Task Models
*User Journeys
*Content Requirements
*Sitemaps
*Wireframes
*Usability Test Reports
*Funnel Diagrams
What I found surprising was the detailed instructions on how to create each of these items in various Software programs; mostly Omnigraffle or MS Powerpoint. There was some reference to Axure, MS Word and MS Excel as well, but they were in the minority.
Nearly half of this book (158 pages versus 332 overall) concerned itself with detailed instructions for how to create this documentation in a very specific format.
Since the Omnigraffle instructions were uniquely for an Apple system; 81 pages had instructions that I could not use. Having not had Axure available to me, another 15 were of no use either.
A concern, I have with all this specificity for a format, was, that it may not fit all circumstances. I get that it may been graphically pleasing to present information in this format for various situations, but it is also highly limiting. If you are consulting, their customer may have unique requests. Also if this graphical technique of representing data, was used by a prior consultant, it makes it seem unimaginative or non-customized for the clients circumstances.
Through the book, I did find sections that were repetitive, leading me to consider this a more basic text; however there were some great nuggets.
As an example in the section on Content requirements they appropriately point out the usefulness of testing with 5 users 5 times versus 25 users at the end, this is a time honored Human Factors tenant. Additionally in the Wireframe section, I liked the use of shading to portray visual heat in a section to help with the hierarchy of information. This is a simple way to be sure your locations of information and graphics are doing what they are supposed to.
In summary, this was a basic text on Human factors and User Experience documentation that will provide a framework and some sound guidance on how to design or redesign a site or application for a defined task. It also gives some very particular instructions on how to do this in a few very popular software programs.