A clear and focused guide to creating useful user experience documentation As web sites and applications become richer and more complex, the user experience (UX) becomes critical to their success. This indispensible and full-color book provides practical guidance on this growing field and shares valuable UX advice that you can put into practice immediately on your own projects. The authors examine why UX is gaining so much interest from web designers, graduates, and career changers and looks at the new UX tools and ideas that can help you do your job better. In addition, you'll benefit from the unique insight the authors provide from their experiences of working with some of the world's best-known companies, learning how to take ideas from business requirements, user research, and documentation to create and develop your UX vision. Communicating the User Experience is an ideal resource for getting started with creating UX documentation.
This books covers quite in detail the different "standard" documentation produced by UX professionals. Of course, everyone has their own methods and styles, so there's no "one fits all" solution (fortunately!), but this book proposes a set of guidelines and principles (as well as examples) that make sense and can be certainly useful to get applied, or at least to know about. I have some years of experience dealing with different kinds and sizes of teams, clients or audiences. Each case was a different scenario, and the methodologies and tools (such as documentation) in each of them was always different, adapted to the actual requirements. However, there are some underlying and recurrent needs and patterns, and this books does a good job covering most of them in a simple and elegant way.
As a downside, I found that each chapter included too many pages dedicated to "how to" use different tools to produce the aforementioned documents (using different software such as Omnigraffle, Axure, Powerpoint...). I understand that for someone beginning his way into UX this could seem useful, but there are many and much better books and online resources on that. In my opinion, including this tutorials in the book made its valuable contents dilute, and I would have much preferred them not to be included.
In summary, I think most of what is exposed in this book will be valuable both for beginners and experts alike. It made me rethink some of the things I do at work, and I definitely plan to apply most of it in future projects.
Excelente libro para gente que quiere aprender y está aprendiendo del UX. Ejemplifica muy bien la forma de documentar cada etapa del proceso de diseño, explica de manera concisa y con ejemplos cada parte y no deja las i sin tilde ni las x sin cruzar.
Se lo recomiendo y selo seguiré recomendando a cualquiera ligeramente interesado en el tema, de verdad es de lo mejor que me eh topado en cuanto a documentación UX, si no es que lo mejor.
Si hubiera que ponerle un PERO, sería que casi no hace referencia a gente que le daría mayor valides a los puntos, por ejemplo citar a Nielsen, citar a Kruger, o citar alguna de las biblias que ya existen de UX, o las heurísticas de N/N. Sin embargo sí cumple con las reglas ya establecidas, solo que no las cita.
Lo acabé hace varios meses pero se me había olvidado ponerlo aquí.
This book has some interesting parts - e.g., about the content of UX study report and follow up on this report. But it contains dozens of pages for "How to draw shapes in PowerPoint, OmniGraffe, etc." so it's more about tools and oriented for someone not familiar with basics.
This is a very tactical book, something that many of these manual type books aren't strong in. Topics covered are things such as how to design a funnel diagram, what data should be in it, what it should look like, etc. I really liked the practicality of the outputs one should consider for UX documentation.
However, a considerable amount of time is spent describing step by step, how to create the documents in various applications such as Powerpoint, OmniGraffle, etc. I tended to skip through these sections because I was more concerned in portraying the information through the proper output, not what tools I should use to create that output.
Overall, this is a keeper and well worth being a reference well after reading.