SIGIA-L Mail Archives: Re: SIGIA-L: Global nav during a process?
Re: SIGIA-L: Global nav during a process?
From: Harland, Dave (dave.harland_at_tallan.com)
Date: Mon Jul 23 2001 - 14:00:01 EDT
If your solution is truly "usage-based", you must choose the latter.
to pigeon-hole users into a process is usually the solution for poor
> From: Steve.Mulder_at_corp.terralycos.com
> Date: Mon, 23 Jul 2001 12:58:54 -0400
> To: sigia-l_at_asis.org
> Subject: SIGIA-L: Global nav during a process?
> Hi all -
> Here's a thorny problem I've run across many times and now face yet
> I'd love to hear ideas, opinions, and data.
> The question: Should global navigation (in this case, the top levels of
> hierarchical nav) appear on the page when the user is within a process
> (anything from email newsletter sign-up to search to checkout)?
> On one side:
> - Reducing "interruptability." If a user is within a transaction, don't
> distract them with global nav that isn't relevant to the task. Let them
> explicitly cancel the task to return to the non-process state.
> - Real estate. Processes like checkout often require more screen real
> estate, which global nav can sometimes hog.
> On the other side:
> - Escape hatch. On the Web, users leave a process not through canceling,
> but by simply going somewhere else. Global nav should always be there so
> that users have control.
> - Consistency. If the global nav appears and disappears throughout the
> experience, it's less reliable and learnable, and potentially
> I'm trying to pose the question in a neutral way so as not to reveal my
> bias. :-)
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:47 EST