Chapter 3. User Needs and Behaviors
What we’ll cover: |
The dangers of an oversimplified view of how we find information |
How our information needs vary |
How our information-seeking behaviors vary |
How and why to learn more about determining users’ information needs and information-seeking behaviors |
In the last two chapters, we’ve defined information architecture and placed it within the broader context of where, when, and by whom it’s practiced. But before we jump into the actual “stuff” of information architecture—the components that make up an architecture, the methodologies that drive its design, and so on—let’s first take a look at users. Information architecture is not restricted to taxonomies, search engines, and the other things that help users find information on a site. Information architecture starts with users and the reason they come to a site in the first place: they have an information need.
This is a truism, but there’s more to it than meets the eye. Information needs can vary widely, and each type of information need causes users to exhibit specific information-seeking behaviors. Information architects need to understand those needs and behaviors, and their designs should correspond accordingly. There is no goal more important to designing information architecture than to satisfy users’ needs.
For example, if your site is a staff directory, looking up a staff member’s phone number is probably a very common information need among your site’s users; in fact, this type of ...
Get Information Architecture for the World Wide Web, 3rd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.