Top positive review
What the doctor ordered
on November 1, 2002
When I read the following, I knew I'd purchased the right book:
"You are going to do it. You might be the project or product manager, the designer, the engineer, or the marketing guy. You're not really sure why it landed on your desk; heck, you're looking around to see if there is another desk you could slide onto. But as your hope for getting someone else to do it fades, you realize it has to be done. And this is the book I wrote for you."
I am a software engineer (primarily web application development) and I spend most of my time writing "backend" code to query databases, apply business logic and generate server driven web pages (much like the one you are viewing right now).
As these applications grow more sophisticated it becomes more and more important to organize the which, how and what of content. This comes up in many ways: the order in which the user sees information, the navigation from screen to screen, the amount of data being display and so on.
This book begins with a description and basis for information architecture and then introduces a variety of principles that one can employ in creating an information architecture for a web site. Some examples of topics include wayfinding, navigation, organization, interviewing and mapping content.
The author's voice maintains an informal tone - it's obvious the author did not want to sound pedantic. However, the content is rich and well developed so one doesn't feel patronized.
The hidden value of this book is that it gives many examples when a principle is asserted. Just by touring the websites given with these principles in mind will make one a better information architect, be it formal or informal.
So my rating is 5 stars; loved it, loved it, loved it!