 |
|
When I read Information Architecture for the World Wide Web, I was satisfied to feel the bulb burning brightly above my head. Since I am a human factors engineer and usability professional, most of the concepts in the book were not new to me. However, I repeatedly observed that this book is one of the only resources that brings the eclectic ideas of web site information architecture together.
Rosenfeld and Morville bring to light some theoretically powerful material regarding the planning, design, testing, and maintenance of large scale web sites. Their approach, as the title suggests, is information architecture. The authors explain that people tend to design web pages rather than web sites, and they show how this is detrimental. When web pages are not developed within a well-conceived information architecture framework, the web site will suffer: Customers will complain, users will not revisit the site, and products will not sell. The big picture is crucial.
I was pleased to see that the book runs contrary to the glut of graphic-design-oriented web- development books available that tend to focus on issues like graphics, HTML, and page layout. I admit that these issues are important, even critical, but only after your users are considered, planning takes place, and the content for the site is generated.
The book is certain to be an eye opener for many web site developers. If you have not utilized human factors and usability analysis, user-centered design, or information architecture in your web site development, I strongly recommend this book. But beware, the book is primarily laden with theory, not tools. I think you might be disappointed if you are looking for a hands-on formula for creating a great web site.
-- John S. Rhodes (john@WebWord.com, http://www.WebWord.com/)
Because different users have varying needs, it's important to support multiple modes of finding information. Some users know exactly what they're looking for. The know what it's called (or labeled), and they know it exists. The just want to find it and leave, as quickly and painlessly as possible. The is called known-item searching.
Other users do not know what they're looking for. They come to the site with a vague idea of the information they need. They may not know the right labels to describe what they want or even whether it exists. As they casually explore your site, they may learn about what they want or even whether it exists. As they casually explore your site, they may learn about products and services that they'd never even considered. Iteratively, through serendipity and associative learning, they may leave your site with knowledge(or products) that they hadn't known they needed.
These modes of finding information are not mutually exclusive. In a well-designed system, many users will switch between known-item searching and casual browsing as they explore the site. If you care about the consumer, make sure your architecture supports both modes. While attractive graphics and reliable technologies are essential to user satisfaction, they are not enough.
Nonetheless, you can demonstrate the value to the organization through less scientific means. Depending upon the goals and nature of your site, you may even be able to defend your investment with some not-so-hard numbers.
Consideration of the value to the producer takes us back to the consumer. If you're producing an external web site, this involves actual and prospective customers, investors, employees, and business partners, not to mention the media and senior executives within your organization. Do you really want to frustrate any of these people? What is the value of quickly and easily helping them find the information they need?
If you're producing and intranet, the employees of your organization are the consumers. What is the cost of their time spent to find the information they need? What is the cost when employees don't find the information they need?
Finally we need to consider the actual costs of designing and implementing the architecture. A well-designed, diplomatic architecture can prevent costly political battles that can stop a project in its tracks. The cost of time spent by high-level executives arguing over which department's information belongs on the main page can skyrocket if you're not careful. A well-designed scaleable architecture can prevent doing it all over a year later. Far too many architectures are crushed under the weight of their own content. Redesign of the information architecture impacts all other aspects of the web site, from graphical navigation bars to the content itself, and it can be a very costly adventure.
-- from Information Architecture for the World Wide Web, pages 12-13.
Forward
Preface
1. What Makes a Web Site Work
2. Introduction to Information Architecture
3. Organizing Information
4. Designing Navigation Systems
5. Labeling Systems
6. Searching Systems
7. Research
8. Conceptual Design
9. Production and Operations
10. Information Architecture in Action
Selected Bibliography
Index
| Readability |
|
| Originality |
|
| Organization |
|
| Accuracy |
|
| Consistency |
|
| Depth |
|
| Timeliness |
|
| Editing |
|
| Design |
|
| Overall Value |
|
Explanation of ERCB rating scale: No stars = unacceptable, 1 Star = marginal, 2 Stars = average, 3 Stars = above average, 4 Stars = exceptional.