Joy joy – Victor seems

Joy joy – Victor seems to be blogging again, and asks: “It seems to me one of the big holes in our knowledge of information architecture, one of the main holes in fact, is how taxonomies become navigation. We’re starting to develop very good methods for arriving at taxonomies for modern websites, and we’re also getting better at determining what characteristics are apparent in successful navigation. But that junction of taxonomy and navigation still seems to be part of the black art of IA, the challenge of marrying the bottom-up to the top-down.”

Here’s my take: the disconnect between a taxonomy and a navigation on a site happens when taxonomies are designed without thinking through how they will be used. This ties in with the myth that you can design a taxonomy for something that is not influenced by its use (or its audience). Or even sillier: that there would be a taxonomy without bias. The idea of the objective taxonomy. It’s wrong. There is no such thing. So if you are designing a taxonomy without imagining how you will use it in the navigation, yes, it will be hard to turn it into navigation.

Another take: if you look at taxonomies as organization schemes (for example: Geographical, or By Product, or by Task), a general rule when turning taxonomies into navigation is: one navigation section per taxonomy. Avoid mixing them, except in the global navigation, where mixing navigation schemes is often a good thing. If you visually separate organization schemes it will be easier for the user to find the right one for them.
If you look at the structure of taxonomies (ontology vs. topicmap vs. simple hierarchy vs. facets vs. controlled vocab vs. …), you are thinking about how to design the actual navigation widgets. We know how to best navigate a simple hierarchy. Yahoo. We are learning how to best navigate a faceted structure. Flamenco. The more complex/rich the structure of the taxonomy gets, the more possibilities for creating complex navigation structures.

0 thoughts on “Joy joy – Victor seems

  1. I meant to say: one navigation section per organization scheme. And with navigation section I mean a part of the screen containing navigation widgets, like a dropdown, or a left hand nav… A visually separate navigation section.

  2. I completely agree a taxonomy has to be designed with user and use in mind, absolutely.

    But what I’m getting at is a little different. Navigation isn’t simply a clickable taxonomy. For example, parts of it are exposed at times and other parts are hidden. Why and how do we expose which parts? (think of a menu with only the category label exposed, vs. a list with all items in a category appearing as hyperlinks).

    If we only map taxonomies to navigation by experimenting and guessing, than the results will only be good if we are very good or very lucky. I believe it’s possible (or at least worth investigating) to make this process more methodical.

    RE>The more complex/rich the structure of the taxonomy gets, the more possibilities for creating complex navigation structures.

    All the more reason to spend time figuring this out!

    Thanks for the link.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s