Information Architecture for the World Wide Web: Designing Large-Scale Web Sites
Rating: 5 of 5
Easy 2 understand
Rating: 5 of 5
Phenomenal book on information architecture
I bought this book shortly before starting my new job as the webmaster 4 a division of the federal governement. It was invaluable 2 me in planning our current internet redesign project & helping 2 explain information architecture 2 non-web designers/developers. I highly recommend reading this book from cover 2 cover.
Rating: 4 of 5
Good enough
This is a perfectly good resource, if you're looking 4 the theoretical underpinnings of how IA should work. I was, however, looking 4 more specifically technical information, along the lines of algorithms & 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 4 technical detail, look elsewhere.
Rating: 5 of 5
A lifesaver
As project manager, I was in a bind when our contract information architect failed 2 understand the complexities of our matrixed business model & client base. Rosenfeld's book helped me design a IA 4 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 & tables of contents, libraries, etc.) & the pros & cons of different organization, labeling, & navigation systems. Then Rosenfeld advises on presenting IA 2 management, etc., managing expectations (yours & others), & gives detailed examples of IA strategies online.
The book describes basic theories of IA in general (i.e. book indexes & tables of contents, libraries, etc.) & the pros & cons of different organization, labeling, & navigation systems. Then Rosenfeld advises on presenting IA 2 management, etc., managing expectations (yours & others), & gives detailed examples of IA strategies online.
Rating: 4 of 5
Intriguing Title (3rdEd)
In "Part I - Intro 2 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 & DB engineer.
Google is pretty good at finding information 4 us on the vast Internet, but there is a long way 2 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 2 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, & metadata. What this basically means is, how do we categorize our data so that it makes sense, is easy 2 navigate & search, & is relevant or adaptable according 2 our users' vocabularies.
"Part III - Process & Methodology" helps one plan a path 2 your IA goals. For instance, developing a research management team 2 discuss such goals, your target audiences, functionality/deficiencies of your current IA system, & 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 2 constantly perfect. An example of this is, two people can search 4 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, & it's so simple, is card sorting. Get some blank cards (20-25) & write on them the headings from categories, subcategories, & content within your site. Ask a user 2 sort this stack of cards into piles that make sense 2 him & have him label those cards using post-it notes. Make sure 2 tell them 2 think-out-loud & be sure 2 take notes. This will give you an idea of how one would "travel" through your site, what is relevant, & what should not be on your homepage, etc.
The authors take the reader through the process of the IA development cycle, from concept, 2 getting managers 2 buy-in, 2 the implementation & 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 & 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 4 potential readers 2 get a better understanding of what IA is comprised of.
1) Strategy Architect - responsible 4 overall design goals & integration
2) Thesaurus Designer - develops classification schemes, controlled vocabularies, & thesauri
3) Controlled Vocabulary Manager - manages the evolution of controlled vocabularies & coordinates the indexing specialists team
4) Indexing Specialist - tags content & services with controlled vocabulary metadata
5) Interaction Designer - creates navigation schemes & page layouts with a focus on user interaction
6) IA Software Analyst - links the IA & IT teams, focusing on ways 2 leverage software 2 create, manage, & drive the user experience
7) IA Usability Engineer - focuses on intersection of usability & IA by conducting studies that isolate IA elements, such as category labels or metadata.
8) Cartographer - converts patterns in content, structure, & usage into maps, guides, indexes, & other useful navigational tools.
9) Search Analyst - leads the design, improvement, & ongoing analysis of search system.
"PART V - IA in the Organization" was a little dry 4 my tastes & irrelevant 2 me. May be very helpful 4 someone in a large bureaucratic organization that wants 2 implement their IA concepts.
The moral of the story is that "site builders" must employ multiple info retrieval methods & tightly integrate them. Everyone searches, browses, scans, & finds info differently; accommodate them.
This book is very comprehensive & 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.
Google is pretty good at finding information 4 us on the vast Internet, but there is a long way 2 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 2 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, & metadata. What this basically means is, how do we categorize our data so that it makes sense, is easy 2 navigate & search, & is relevant or adaptable according 2 our users' vocabularies.
"Part III - Process & Methodology" helps one plan a path 2 your IA goals. For instance, developing a research management team 2 discuss such goals, your target audiences, functionality/deficiencies of your current IA system, & 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 2 constantly perfect. An example of this is, two people can search 4 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, & it's so simple, is card sorting. Get some blank cards (20-25) & write on them the headings from categories, subcategories, & content within your site. Ask a user 2 sort this stack of cards into piles that make sense 2 him & have him label those cards using post-it notes. Make sure 2 tell them 2 think-out-loud & be sure 2 take notes. This will give you an idea of how one would "travel" through your site, what is relevant, & what should not be on your homepage, etc.
The authors take the reader through the process of the IA development cycle, from concept, 2 getting managers 2 buy-in, 2 the implementation & 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 & 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 4 potential readers 2 get a better understanding of what IA is comprised of.
1) Strategy Architect - responsible 4 overall design goals & integration
2) Thesaurus Designer - develops classification schemes, controlled vocabularies, & thesauri
3) Controlled Vocabulary Manager - manages the evolution of controlled vocabularies & coordinates the indexing specialists team
4) Indexing Specialist - tags content & services with controlled vocabulary metadata
5) Interaction Designer - creates navigation schemes & page layouts with a focus on user interaction
6) IA Software Analyst - links the IA & IT teams, focusing on ways 2 leverage software 2 create, manage, & drive the user experience
7) IA Usability Engineer - focuses on intersection of usability & IA by conducting studies that isolate IA elements, such as category labels or metadata.
8) Cartographer - converts patterns in content, structure, & usage into maps, guides, indexes, & other useful navigational tools.
9) Search Analyst - leads the design, improvement, & ongoing analysis of search system.
"PART V - IA in the Organization" was a little dry 4 my tastes & irrelevant 2 me. May be very helpful 4 someone in a large bureaucratic organization that wants 2 implement their IA concepts.
The moral of the story is that "site builders" must employ multiple info retrieval methods & tightly integrate them. Everyone searches, browses, scans, & finds info differently; accommodate them.
This book is very comprehensive & 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.
The post-Ajaxian Web 2.0 world of wikis, folksonomies, & mashups makes well-planned information architecture even more essential. How do you present large volumes of information 2 people who need 2 find what they're looking 4 quickly? This classic primer shows information architects, designers, & web site developers how 2 build large-scale & maintainable web sites that are appealing & easy 2 navigate.
The new edition is thoroughly updated 2 address emerging technologies -- with recent examples, new scenarios, & information on best practices -- while maintaining its focus on fundamentals. With topics that range from aesthetics 2 mechanics, "Information Architecture 4 the World Wide Web" explains how 2 create interfaces that users can understand right away. Inside, you'll find: An overview of information architecture 4 both newcomers & experienced practitioners The fundamental components of an architecture, illustrating the interconnected nature of these systems. Updated, with updates 4 tagging, folksonomies, social classification, & guided navigation Tools, techniques, & methods that take you from research 2 strategy & design 2 implementation. This edition discusses blueprints, wireframes & the role of diagrams in the design phase A series of short essays that provide practical tips & philosophical advice 4 those who work on information architecture The business context of practicing & promoting information architecture, including recent lessons on how 2 handle enterprise architecture Case studies on the evolution of two large & very different information architectures, illustrating best practices along the way
How do you documentthe rich interfaces of web applications? How do you design 4 multiple platforms & mobile devices? With emphasis on goals & approaches over tactics or technologies, this enormously popular book gives you knowledge about information architecture with a framework that allows you 2 learn new approaches -- & unlearn outmoded ones.
($17.98)
Buy Information Architecture for the World Wide Web: Designing Large-Scale Web Sites Now!
For someone who wants 2 know how information architecture works, this is a great book. But be careful. This books focuses heavily on the world wide web part (well it said it would) so make sure you keep that in mind if you were looking 4 general knowlede about information architecture.