Product Description

Most discussion about Web design seems to focus on the creative process, yet turning concept into reality requires a strong set of deliverables—the documentation (concept model, site maps, usability reports, and more) that serves as the primary communication tool between designers and customers. Here at last is a guide devoted to just that topic. Combining quick tips for improving deliverables with in-depth discussions of presentation and risk mitigation techniques, author Dan Brown shows you how to make the documentation you're required to provide into the most efficient communications tool possible. He begins with an introductory section about deliverables and their place in the overall process, and then delves into to the different types of deliverables. From usability reports to project plans, content maps, flow charts, wireframes, site maps, and more, each chapter includes a contents checklist, presentation strategy, maintenance strategy, a description of the development process and the deliverable's impact on the project, and more.

Product Details

• Amazon Sales Rank: #77082 in Books
• Published on: 2006-09-16
• Original language: English
• Number of items: 1
• Binding: Paperback
• 368 pages

Features

• ISBN13: 9780321392350
• Condition: NEW
• Notes: Brand New from Publisher. No Remainder Mark.
• Click here to view our Condition Guide and Shipping Prices

About the Author
Dan Brown has been practicing information architecture and user experience design since 1994. Through his consulting work in both public and private sectors, he has improved enterprise communications for both Federal and Fortune 500 clients, currently the Federal Communications Commission. Dan writes and speaks frequently on information architecture, and contributed to the inaugural issue of UX Matters, a new online magazine dedicated to user experience design. Dan is very active in the local Washington, DC information architecture community, and serves on the advisory board for the Information Architecture Institute.

Customer Reviews

For people who work in large web teams
If you work in a large team in a big corporation, and use conventional rather than agile approaches to web development, you may find this book very useful. It has advice not just on what tools to employ, when, and why, but also how to interact with clients and specialists in various roles during every stage of website genesis/ontogeny, from strategy to execution (via usability tests, concept mapping, wireframes and much more).

As a one-person band with a very small budget, I found big chunks of it rather idealistic, somehow old-fashioned, and not very relevant to my own circumstances. The usability / market research specialist? The information architect? Those would be me. The programmer? The graphic designer? Oh, those would be me too. And the person making sure that the words and images are suitable for the web as a medium? Me again.

I wanted some advice on best practice for (a) documenting decisions made (and reasons for making them) and (b) highlighting consequences of those decisions (and reasons) for future work. I was quite surprised not to see much discussion about how to document (b), which in my experience is often a huge hole in documentation.

Also, the processes I use are much more agile than those described in the book, which doesn't cover how to document development using agile methods. This is a shame, because I think more and more developers are moving in this direction.

The meta-web development communication book
Dan Brown did it. I never imagined someone would pull it off, but he came up with a meta-web development communication book, a book about the process of putting together user needs, strategy and web design documents. In these three categories, he covers the ten web site communication deliverables he considers to be of most value, taking the reader through a structure that will help in the process of conception, construction, presentation to others and context.

I found the concept of Personas he introduced very interesting (and innovative in the web development space) and later picked up a book that specialized on the topic ("The User Is Always Right" by Steve Mulder and Ziv Yaar) to learn more about it. In terms of the rest of the concepts he introduced, if you are a seasoned web producer/development specialist, you may not find most of them to be new, but seeing the whole package in front of you will be useful and refresh items you know to be of importance. If you are becoming acquainted with this area, the book will become a permanent reference you will want to take with you at all times along with "Web Project Management: Delivering Successful Commercial Web Sites" by Ashley Friedlein.

Buyer beware - companion website does not have promised resources
Part of the value of this book is the promise that the author will provide templates and examples. This promise is worth zero. If you go to the companion website, there is a note from the author that says, essentially, "Ooops, so sorry. Got too busy." Just a tad unprofessional? I guess different people have different perspectives on such things.

Call me crazy, but one would think that the author would have had a whole stack of examples and templates BEFORE he wrote the book. How else would he know what documents are needed? Just a rhetorical question.....

The book itself is useful, don't get me wrong. I am just very disappointed in the lack of companion material. Other reviews very adequately cover the content.

In terms of practical help, AND downloadable templates, I vastly prefer Web ReDesign 2.0: Workflow that Works (2nd Edition) by Kelly Goto.

Kelly Goto's advice saved my tail when I was a newbie in the field (waaaaay back in the dark ages of the 20th century), and still has relevance for me today.

Web ReDesign 2.0: Workflow that Works (2nd Edition) (VOICES)


__________________________________________________________________

UPDATE: August 2008: nothing has changed on the companion website, http://www.communicatingdesign.com/ Quite frankly, it looks like it has been abandoned.