[Sigia-l] Redundant information and content

[SCoon at ameritrade.com]

Thomas Donehower wrote: 

"Quick question: Content is not always mutually exclusive. In defining a navigation structure, is it (A) better to keep content mutually exclusive to one area so as not to cause confusion or is it (B) better to allow access to the content from where ever it may be relevant. If B, is it better to link to the content in one area or to have it live in multiple areas?"

=========================

It's a good rule of thumb to create cognitive "homes" for functionality or content, yet allow for the *design* of multiple paths of navigation to such objects. 

I would begin by creating numerous content-similar hubs and their conceptual relationships (that is a very open ended parameter -- context specific business/user analysis should drive the design) when developing a site structure & navigation schema. Once my groupings were established, I'd exercise three *primary* approaches for designing access to the grouped information:

1) Top down navigation - visual in nature, so a high degree of recall can be established with the user concerning context and relevance of the content area.

2) Contextual navigation - appears throughout the interactive system at relevant touch points within various task flows, improving everything from "stickiness" (cross pollination of content/functionality), to sales (see similar's), etc.

3) Bottom up navigation - the user can find information without needing to know *where* it actually resides, yet in this particular return process, object recall will be reinforced in regards to the design of the top down navigation.

So to answer your question, generally speaking, stay away from creating repetitive content or functionality; use the medium and the affordance of navigation to do the work for you.

/*spcoon*/