SIGIA-L Mail Archives: Re: [Sigia-l] sitemap question
Re: [Sigia-l] sitemap question
> Consider, you have a web-based tool and users are
> having a hard time navigating to the web pages for
> performing a task.
Before I do anything, I'd ask myself if there isn't something I can do to
actually solve the problem (make it easier to perform the task) instead of
papering it over with "better" documentation/sitemap. For example:
> Task: Submit The Leave Request
> Nav Path: Home page > Web Forms > Create > Leave
If a particular task is performed often (like Leave Request), I'd ask myself
if I should place a direct link on the home page. Or if I should perhaps
group the top half dozen functions together. Or if I should abandon the page
oriented architecture for a task oriented one, thereby eliminating page
There's often something drastically wrong, if I have to manually type (long)
URLs from a printed document to decipher an online app's navigation.
> The reason why the users are facing navigation
> problems might be because of the numerous functions
> available with the tool.
That alone is almost never a legitimate excuse to not optimize the UI.
Are you prevented from actually redesigning the architecture/interface to
get rid of the root cause instead of these symptoms?
"Innovate as a last resort."
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
Searchable Archive at http://www.info-arch.org/lists/sigia-l/
IA 06 Summit. Mark your calendar. March 23-27, Vancouver, BC
Sigia-l mailing list -- post to: Sigia-l_at_asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
This archive was generated by hypermail 2.1.6
: Mon Jan 02 2006 - 17:11:01 EST