<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Weblog overcomplexity</title>
	<atom:link href="http://www.darcynorman.net/2004/09/06/weblog-overcomplexity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.darcynorman.net/2004/09/06/weblog-overcomplexity/</link>
	<description>apparently much happier in person</description>
	<lastBuildDate>Fri, 20 Nov 2009 14:35:07 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Hubick</title>
		<link>http://www.darcynorman.net/2004/09/06/weblog-overcomplexity/#comment-79261</link>
		<dc:creator>Chris Hubick</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-79261</guid>
		<description>I totally agree with this rant!!

I think &#039;clutter&#039; is a problem with not just blogs, but most web site designs in general (such as one for a university I am quite familiar with).  I think web designers need to learn the concept of use-cases and start thinking of &quot;reasons people come to this web site&quot;, and tailor the design to meet those cases with efficiency.  I personally translate this into what I term a &#039;wizard&#039; or &#039;deep&#039; style layout.  *Physically* a site is a &#039;web&#039; of links, but *logically*, according to use-case, it can be thought of as a &#039;tree&#039; structure.  With a &#039;shallow&#039; layout, the front page of your site (the root of the tree) has a link to almost every other page on the site.  A &#039;deep&#039; layout presents a minimal (reasonable acording to use-case, over-reduction can be just as evil) set of options at the root (and each sub-level), walking the user deeper into the site tree to find what they want (wizard style).  There can be multiple logical paths to any one physical page (leaf), organized by use-case.  Each branch of the tree should NOT link to the other branches - it should only present options to navigate up or down within the current use-case, that is to say, your university &#039;application for admission&#039; page does not need a link to the &#039;swimming pool hours&#039; page (admitedly extreme example).  Put another way, Headers, Footers, and Menus need to be context sensitive.  Web designs that optimize for the number of clicks are missing the point, sure, you have to click less times with a shallow layout, but if the options are intelligently designed in a deep layout, finding *what* to click on should be so obvious as to be almost subconsciously fast - rather than forcing you to spend a minute finding the right link on each page.</description>
		<content:encoded><![CDATA[<p>I totally agree with this rant!!</p>
<p>I think &#8216;clutter&#8217; is a problem with not just blogs, but most web site designs in general (such as one for a university I am quite familiar with).  I think web designers need to learn the concept of use-cases and start thinking of &#8220;reasons people come to this web site&#8221;, and tailor the design to meet those cases with efficiency.  I personally translate this into what I term a &#8216;wizard&#8217; or &#8216;deep&#8217; style layout.  *Physically* a site is a &#8216;web&#8217; of links, but *logically*, according to use-case, it can be thought of as a &#8216;tree&#8217; structure.  With a &#8217;shallow&#8217; layout, the front page of your site (the root of the tree) has a link to almost every other page on the site.  A &#8216;deep&#8217; layout presents a minimal (reasonable acording to use-case, over-reduction can be just as evil) set of options at the root (and each sub-level), walking the user deeper into the site tree to find what they want (wizard style).  There can be multiple logical paths to any one physical page (leaf), organized by use-case.  Each branch of the tree should NOT link to the other branches &#8211; it should only present options to navigate up or down within the current use-case, that is to say, your university &#8216;application for admission&#8217; page does not need a link to the &#8217;swimming pool hours&#8217; page (admitedly extreme example).  Put another way, Headers, Footers, and Menus need to be context sensitive.  Web designs that optimize for the number of clicks are missing the point, sure, you have to click less times with a shallow layout, but if the options are intelligently designed in a deep layout, finding *what* to click on should be so obvious as to be almost subconsciously fast &#8211; rather than forcing you to spend a minute finding the right link on each page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D'Arcy Norman</title>
		<link>http://www.darcynorman.net/2004/09/06/weblog-overcomplexity/#comment-79262</link>
		<dc:creator>D'Arcy Norman</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-79262</guid>
		<description>Exactly, Chris. I&#039;m guessing most people visiting any website aren&#039;t too concerned with how many clicks they have to make. They are more likely to be more concerned about their ability to find what they&#039;re looking for. That can/should have nothing to do with the number of clicks - and be more related to organization, searchability, and stuff like that.

I actually wasn&#039;t too concerned about other people&#039;s experience with this website - it is primarily intended to be an offline brain for myself (and I use it all the time). As such, it has to be easy for me to find stuff. A decent (doesn&#039;t have to be perfect, or great) design lets me do that. Without wading through blogrolls, last 500 posts, other sites I visit, blah blah blah. That stuff is still here, but it&#039;s tucked out of the way. And there are other tools provided to give better control to the user (i.e., me) in accessing content.  If other folks find it useful, that&#039;s a bonus, too ;-)</description>
		<content:encoded><![CDATA[<p>Exactly, Chris. I&#8217;m guessing most people visiting any website aren&#8217;t too concerned with how many clicks they have to make. They are more likely to be more concerned about their ability to find what they&#8217;re looking for. That can/should have nothing to do with the number of clicks &#8211; and be more related to organization, searchability, and stuff like that.</p>
<p>I actually wasn&#8217;t too concerned about other people&#8217;s experience with this website &#8211; it is primarily intended to be an offline brain for myself (and I use it all the time). As such, it has to be easy for me to find stuff. A decent (doesn&#8217;t have to be perfect, or great) design lets me do that. Without wading through blogrolls, last 500 posts, other sites I visit, blah blah blah. That stuff is still here, but it&#8217;s tucked out of the way. And there are other tools provided to give better control to the user (i.e., me) in accessing content.  If other folks find it useful, that&#8217;s a bonus, too <img src='http://www.darcynorman.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
