Customer comments on this selection.
 Good enough
This is a perfectly good resource, if you're looking for the theoretical underpinnings of how IA should work. I was, however, looking for more specifically technical information, along the lines of algorithms and integration techniques. For this I ended up going with Programming Collective Intelligence: Building Smart Web 2.0 Applications, which is more geared in that direction. Again, if IA is your whole intention, then this is a great resource, but if you're looking for technical detail, look elsewhere.
 A lifesaver
As project manager, I was in a bind when our contract information architect failed to understand the complexities of our matrixed business model and client base. Rosenfeld's book helped me design a IA for our 700 page HTML site that has since been described as simple, intuitive, a no-brainer. What great compliments!
The book describes basic theories of IA in general (i.e. book indexes and tables of contents, libraries, etc.) and the pros and cons of different organization, labeling, and navigation systems. Then Rosenfeld advises on presenting IA to management, etc., managing expectations (yours and others), and gives detailed examples of IA strategies online.
Intriguing Title (3rdEd)
In "Part I - Intro to IA," obviously the basics are covered, like what exactly is IA? What does an Information Architect do? After reading this title, I would define an Information Architect as a glorified content manager. Someone that occupies the realm between UI designer and DB engineer.
Google is pretty good at finding information for us on the vast Internet, but there is a long way to go. I believe these authors make a valid point that IA will become increasingly relevant. In fact, I wouldn't doubt that in the future you will actually be able to obtain a BS in IA. Nonetheless, IA is around us everyday when we use technology no matter what we want call it.
The elements that make up IA are covered in "Part II - Basic Principles of IA." The basis of IA is the interaction or retrieval of information in terms of organization systems, labeling systems, navigation systems, search systems, thesauri, controlled vocabularies, and metadata. What this basically means is, how do we categorize our data so that it makes sense, is easy to navigate and search, and is relevant or adaptable according to our users' vocabularies.
"Part III - Process and Methodology" helps one plan a path to your IA goals. For instance, developing a research management team to discuss such goals, your target audiences, functionality/deficiencies of your current IA system, and integrating other software, such as your customer management system (CMS).
My favorite topic here is the detailed discussion of "building vocabularies." This is something everybody needs to constantly perfect. An example of this is, two people can search for the same thing using two different criteria. How can can we build a vocabulary system that recognizes that?
Many research tools are discussed. My favorite technique, and it's so simple, is card sorting. Get some blank cards (20-25) and write on them the headings from categories, subcategories, and content within your site. Ask a user to sort this stack of cards into piles that make sense to him and have him label those cards using post-it notes. Make sure to tell them to think-out-loud and be sure to take notes. This will give you an idea of how one would "travel" through your site, what is relevant, and what should not be on your homepage, etc.
The authors take the reader through the process of the IA development cycle, from concept, to getting managers to buy-in, to the implementation and administration of the system; very thorough.
The hands-on aspects of IA are explained in "Part IV - IA in Practice." One thing I found insightful was how one could pursue an official education in the area of IA, albeit there is no such degree. To gain a competitive advantage, the authors suggest obtaining a degree in Library and Information Science (LIS) or Human-Computer Interaction (HCI).
At the end of chapter 15, there is a list of position titles making up an ideal IA team.
This list may prove helpful for potential readers to get a better understanding of what IA is comprised of.
1) Strategy Architect - responsible for overall design goals and integration
2) Thesaurus Designer - develops classification schemes, controlled vocabularies, and thesauri
3) Controlled Vocabulary Manager - manages the evolution of controlled vocabularies and coordinates the indexing specialists team
4) Indexing Specialist - tags content and services with controlled vocabulary metadata
5) Interaction Designer - creates navigation schemes and page layouts with a focus on user interaction
6) IA Software Analyst - links the IA and IT teams, focusing on ways to leverage software to create, manage, and drive the user experience
7) IA Usability Engineer - focuses on intersection of usability and IA by conducting studies that isolate IA elements, such as category labels or metadata.
8) Cartographer - converts patterns in content, structure, and usage into maps, guides, indexes, and other useful navigational tools.
9) Search Analyst - leads the design, improvement, and ongoing analysis of search system.
"PART V - IA in the Organization" was a little dry for my tastes and irrelevant to me. May be very helpful for someone in a large bureaucratic organization that wants to implement their IA concepts.
The moral of the story is that "site builders" must employ multiple info retrieval methods and tightly integrate them. Everyone searches, browses, scans, and finds info differently; accommodate them.
This book is very comprehensive and even deals with the politics of IA. To me, the book gets a little long at times, but if your life evolves around information somehow, this is an essential read.
Excellent reference
The topic of the Polar Bear is very defined and focused, and the book reflects this. It's a bit dry - reads much like stereo instructions - but for someone who is dedicated to exploring content and information architecture in depth, there's simply no better reference.
I wouldn't call this a good primer, but I'd definitely recommend it for more advanced reading, and definitely as a reference book.
 Very biased book
In general, this book contains some useful yet common sense information. This book is more about how to become a talker than a worker. I read through and found the first half confirmed my experience and the second half is a bust. If you want to become an office politician, this is a must have.
|
