<?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"
	>
<channel>
	<title>Comments on: Consistency in Design is the Wrong Approach</title>
	<atom:link href="http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<pubDate>Thu, 24 Jul 2008 15:23:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Of Global Consistency and Current Knowledge &#124; Global by Design</title>
		<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/#comment-88526</link>
		<dc:creator>Of Global Consistency and Current Knowledge &#124; Global by Design</dc:creator>
		<pubDate>Wed, 19 Sep 2007 03:13:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=66#comment-88526</guid>
		<description>[...] usability consultant Jared Spool recently wrote about the difference between designing for &#8220;consistency&#8221; and designing for [...]</description>
		<content:encoded><![CDATA[<p>[...] usability consultant Jared Spool recently wrote about the difference between designing for &#8220;consistency&#8221; and designing for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johann Rosario</title>
		<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/#comment-36071</link>
		<dc:creator>Johann Rosario</dc:creator>
		<pubDate>Mon, 20 Nov 2006 19:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=66#comment-36071</guid>
		<description>Thank you for this validating article. As a user interface designer I have never been more frustrated than when I’m sitting in a “Design by Committee” meeting and some well intentioned, but otherwise misinformed corporate hack comments that “the design should be consistent.”  

Really, you think!  Consistent with what, may I ask? Consistent for the sack of consistency? Consistent with sounding proper at a meeting when you really have no idea what your talking about?

Whenever someone says “Make it consistent” I usually break out in allergies, because in my experience consistency has been the bail of anything creative and the force that misdirects a design team.  

Obviously certain things have to have a uniformity of structure, and a repeating theme in the design, but what they really are saying is, “at all cost, make it an easy project that wont be a problem later.”

It’s a cursed word because it usually has the opposite effect.  It’s a word that save you from looking radical in a corporate meeting, (and we all know where that can lead to).  It’s a word that fails to address the very fact that “consistency” often times can be equally apply to doing something consistently wrong.  

Every company has a nebulous definition of consistency, even when we think we are saying the same thing.  Perhaps the word should be banned!</description>
		<content:encoded><![CDATA[<p>Thank you for this validating article. As a user interface designer I have never been more frustrated than when I’m sitting in a “Design by Committee” meeting and some well intentioned, but otherwise misinformed corporate hack comments that “the design should be consistent.”  </p>
<p>Really, you think!  Consistent with what, may I ask? Consistent for the sack of consistency? Consistent with sounding proper at a meeting when you really have no idea what your talking about?</p>
<p>Whenever someone says “Make it consistent” I usually break out in allergies, because in my experience consistency has been the bail of anything creative and the force that misdirects a design team.  </p>
<p>Obviously certain things have to have a uniformity of structure, and a repeating theme in the design, but what they really are saying is, “at all cost, make it an easy project that wont be a problem later.”</p>
<p>It’s a cursed word because it usually has the opposite effect.  It’s a word that save you from looking radical in a corporate meeting, (and we all know where that can lead to).  It’s a word that fails to address the very fact that “consistency” often times can be equally apply to doing something consistently wrong.  </p>
<p>Every company has a nebulous definition of consistency, even when we think we are saying the same thing.  Perhaps the word should be banned!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/#comment-148</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Mon, 10 Oct 2005 16:00:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=66#comment-148</guid>
		<description>Dave: We like to turn to &lt;a href="http://www.uie.com/events/uiconf/articles/goodwin_interview/" rel="nofollow"&gt;personas&lt;/a&gt; when we're faced with the "Which users should we design for" question. Personas take an umanagable mass and focus it on a few individuals with both overlapping and independent needs.</description>
		<content:encoded><![CDATA[<p>Dave: We like to turn to <a href="http://www.uie.com/events/uiconf/articles/goodwin_interview/" rel="nofollow">personas</a> when we&#8217;re faced with the &#8220;Which users should we design for&#8221; question. Personas take an umanagable mass and focus it on a few individuals with both overlapping and independent needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/#comment-147</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Mon, 10 Oct 2005 15:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=66#comment-147</guid>
		<description>Patrick: What I was trying to say was that consistency isn't &lt;em&gt;bad&lt;/em&gt;, but is the &lt;em&gt;wrong&lt;/em&gt; place to start when designing. When designers ask, "What should this be consistent with?", they aren't necessarily taking the users' knowledge into account -- thereby creating something that is consistent but unrecognizable.

The AVIS folks shot for internal consistency, however they didn't take into account that many users would come with an already existing perception of what the asterisk meant -- the opposite of the designer's choice. The result: confusion *because* of the consistency.

Instead of focusing on consistency, the &lt;em&gt;right&lt;/em&gt; place to start is "What do the users know?" If users are familiar with design elements, and you design for that familiarity, you'll end up with a consistent interface. But, that's really an accidental side effect of designing for current knowledge.</description>
		<content:encoded><![CDATA[<p>Patrick: What I was trying to say was that consistency isn&#8217;t <em>bad</em>, but is the <em>wrong</em> place to start when designing. When designers ask, &#8220;What should this be consistent with?&#8221;, they aren&#8217;t necessarily taking the users&#8217; knowledge into account &#8212; thereby creating something that is consistent but unrecognizable.</p>
<p>The AVIS folks shot for internal consistency, however they didn&#8217;t take into account that many users would come with an already existing perception of what the asterisk meant &#8212; the opposite of the designer&#8217;s choice. The result: confusion *because* of the consistency.</p>
<p>Instead of focusing on consistency, the <em>right</em> place to start is &#8220;What do the users know?&#8221; If users are familiar with design elements, and you design for that familiarity, you&#8217;ll end up with a consistent interface. But, that&#8217;s really an accidental side effect of designing for current knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Moss</title>
		<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/#comment-145</link>
		<dc:creator>Patrick Moss</dc:creator>
		<pubDate>Mon, 10 Oct 2005 15:13:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=66#comment-145</guid>
		<description>I'm a bit confused by this article.  The headline is provocative, but the article doesn't argue that consistency is a *bad* thing.  Rather, it seems to state that being internally consistent is not sufficient for good design, if the design choices were poor.  Is this the crux of the article?  I'm not sure exactly how the Avis example makes sense in this context...it seems that if the Avis designers had elected to be 'externally' consistent (using asterisks) perhaps that would have been superior to creating their own standard and foisting it on users.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a bit confused by this article.  The headline is provocative, but the article doesn&#8217;t argue that consistency is a *bad* thing.  Rather, it seems to state that being internally consistent is not sufficient for good design, if the design choices were poor.  Is this the crux of the article?  I&#8217;m not sure exactly how the Avis example makes sense in this context&#8230;it seems that if the Avis designers had elected to be &#8216;externally&#8217; consistent (using asterisks) perhaps that would have been superior to creating their own standard and foisting it on users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Murray</title>
		<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/#comment-98</link>
		<dc:creator>Dave Murray</dc:creator>
		<pubDate>Fri, 23 Sep 2005 12:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=66#comment-98</guid>
		<description>I am curious about a couple of items.
Car companies usually are thinking of their customer's "curretn knowledge" in creating new design. While it adds sparkle to their line of products, it tends to narrow their customer base. Yet, underneath it, there seems this shadowy consistency: design by customer wants. But which customer? 

Secondly, does this tend to exaccerabte the problem of constantly changing to meet the whims of customers, reinforcing an eclectic approach to life rather than attempting to build foundations? I'm not advocating a "stone age" approach to life (i.e. everything is in concrete and can never change). No, consistency provides a framework, an identity even a sanctuary. Some consistency, I think, it vital. Addressing customer needs and wants to important too and I support researching customer knowledge as a key means of delivering the product. But I also think some dynamic balance (i.e. a consistent concept applied upon customer knowledge) would be good, too. Example: pants; still fit over two legs but look at the pockets!</description>
		<content:encoded><![CDATA[<p>I am curious about a couple of items.<br />
Car companies usually are thinking of their customer&#8217;s &#8220;curretn knowledge&#8221; in creating new design. While it adds sparkle to their line of products, it tends to narrow their customer base. Yet, underneath it, there seems this shadowy consistency: design by customer wants. But which customer? </p>
<p>Secondly, does this tend to exaccerabte the problem of constantly changing to meet the whims of customers, reinforcing an eclectic approach to life rather than attempting to build foundations? I&#8217;m not advocating a &#8220;stone age&#8221; approach to life (i.e. everything is in concrete and can never change). No, consistency provides a framework, an identity even a sanctuary. Some consistency, I think, it vital. Addressing customer needs and wants to important too and I support researching customer knowledge as a key means of delivering the product. But I also think some dynamic balance (i.e. a consistent concept applied upon customer knowledge) would be good, too. Example: pants; still fit over two legs but look at the pockets!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Couros Blog &#187; Blog Archive &#187; Forget Consistency. Think About The User First.</title>
		<link>http://www.uie.com/brainsparks/2005/09/15/consistency-in-design-is-the-wrong-approach/#comment-83</link>
		<dc:creator>Couros Blog &#187; Blog Archive &#187; Forget Consistency. Think About The User First.</dc:creator>
		<pubDate>Sat, 17 Sep 2005 00:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=66#comment-83</guid>
		<description>[...] Stephen Downes points to a great article that argues that designers often focus entirely too much on the consistency of design versus thinking about a users current knowledge. The problem with thinking in terms of consistency is that those thoughts focus purely on the design and the user can get lost. “Is what I’m designing consistent with other things we’ve designed (or others have designed)?” is the wrong question to ask. [...]</description>
		<content:encoded><![CDATA[<p>[...] Stephen Downes points to a great article that argues that designers often focus entirely too much on the consistency of design versus thinking about a users current knowledge. The problem with thinking in terms of consistency is that those thoughts focus purely on the design and the user can get lost. “Is what I’m designing consistent with other things we’ve designed (or others have designed)?” is the wrong question to ask. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
