[Sigia-l] RE: Site Map/Index - as Site Element

[Listera]

AF Cossham:

> And since you can't predict
> exactly what those users want, why not give them a range of possibilities?

This does sound like a perfectly reasonable thing to suggest, and in some
circumstances it may be.

Yet there's plenty of evidence that there's an inverse relationship between
options and utility. Increasing options does not necessarily lead to better
usability. (People have written books about this and I could SPAM you if
you'd like :-)

For instance, if sitemaps are useful/necessary why not give users a whole
range/categories/templates of (what's commonly referred to as) sitemaps? Why
not have dedicated navigation for sitemaps? Why not turn the sitemap into
the landing/homepage? Etc.

The hardest part of design is exclusion; inclusion is easy.

> If I was looking for a job with a company and wanted to scope them first...

Hmm. The sitemap reflects the organization of the *site* not (necessarily)
the company.

> If I didn't know what sort of information an organisation might be
> able to offer me (say, the ALA), then a site map would be a much better
> start.

Again, this (introduction/branding for new arrivals) is a classical design
pattern *and* should be addressed by designers, not left to random perusal
of sitemaps.
 
> If design of websites was perfect, then one approach might be
> sufficient. It isn't, so cater broadly, and anticipate future needs too .

In my experience over the years, virtually all 'justifications' for sitemaps
have turned out to be a case of "the main navigation is failing" as you put
it.

Ziya
Nullius in Verba