<?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: Beware of the Frankenstein Design</title>
	<atom:link href="http://www.michaelgaigg.com/blog/2009/05/22/beware-of-the-frankenstein-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelgaigg.com/blog/2009/05/22/beware-of-the-frankenstein-design/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 19:58:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: IT Solutions Blog &#187; Happy 1st Anniversary!</title>
		<link>http://www.michaelgaigg.com/blog/2009/05/22/beware-of-the-frankenstein-design/comment-page-1/#comment-486</link>
		<dc:creator>IT Solutions Blog &#187; Happy 1st Anniversary!</dc:creator>
		<pubDate>Mon, 05 Oct 2009 22:39:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=406#comment-486</guid>
		<description>[...] Beware of the Frankenstein Design [...]</description>
		<content:encoded><![CDATA[<p>[...] Beware of the Frankenstein Design [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Gaigg</title>
		<link>http://www.michaelgaigg.com/blog/2009/05/22/beware-of-the-frankenstein-design/comment-page-1/#comment-271</link>
		<dc:creator>Michael Gaigg</dc:creator>
		<pubDate>Mon, 15 Jun 2009 14:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=406#comment-271</guid>
		<description>Hey Neal, that&#039;s an excellent example of CYA :) and as you say, important is to set these things in stone. I like the concept of &quot;on-strategy&quot; and &quot;off-strategy&quot; - helps to make the customer think upfront, helps your team to focus and will save you of surprises later. 
 
This is a good read about Common Visual Design Misconceptions (Luke Wroblewski, &lt;a href=&quot;http://www.uxmatters.com/mt/archives/2008/11/common-visual-design-misconceptions.php)&quot; rel=&quot;nofollow&quot;&gt;http://www.uxmatters.com/mt/archives/2008/11/comm...&lt;/a&gt; that explores the disconnect between what clients expect and what they mean when they say it. Kind of, why is it yellow? We asked for bright, sunny and lively... Can you make the button green or bigger (=stand out). What they really mean: I didnt&#039; find the button (maybe the place is wrong or the label misleading). </description>
		<content:encoded><![CDATA[<p>Hey Neal, that&#039;s an excellent example of CYA <img src='http://www.michaelgaigg.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  and as you say, important is to set these things in stone. I like the concept of &quot;on-strategy&quot; and &quot;off-strategy&quot; &#8211; helps to make the customer think upfront, helps your team to focus and will save you of surprises later.</p>
<p>This is a good read about Common Visual Design Misconceptions (Luke Wroblewski, <a href="http://www.uxmatters.com/mt/archives/2008/11/common-visual-design-misconceptions.php)" rel="nofollow">http://www.uxmatters.com/mt/archives/2008/11/comm&#8230;</a> that explores the disconnect between what clients expect and what they mean when they say it. Kind of, why is it yellow? We asked for bright, sunny and lively&#8230; Can you make the button green or bigger (=stand out). What they really mean: I didnt&#039; find the button (maybe the place is wrong or the label misleading).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neal D</title>
		<link>http://www.michaelgaigg.com/blog/2009/05/22/beware-of-the-frankenstein-design/comment-page-1/#comment-265</link>
		<dc:creator>Neal D</dc:creator>
		<pubDate>Fri, 12 Jun 2009 11:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=406#comment-265</guid>
		<description>Require a creative brief or other document that outlines strategic objectives before the project begins. Never argue esthetics with a client &#8211; those arguments are impossible to win. Instead, determine if the design, color choice, fonts, hierarchy, etc. is on-strategy or off-strategy. To do this, you need a document that specifies the strategy. Then, when the client says they hate yellow, you can point to the strategy that said the site needed to be &#8220;bright, sunny, and lively.&#8221; You can defend yellow as being on-strategy, but suggest you&#8217;d be happy to explore other shades of yellow or other color choices that convey &#8220;bright, sunny, and lively.&#8221; </description>
		<content:encoded><![CDATA[<p>Require a creative brief or other document that outlines strategic objectives before the project begins. Never argue esthetics with a client &ndash; those arguments are impossible to win. Instead, determine if the design, color choice, fonts, hierarchy, etc. is on-strategy or off-strategy. To do this, you need a document that specifies the strategy. Then, when the client says they hate yellow, you can point to the strategy that said the site needed to be &ldquo;bright, sunny, and lively.&rdquo; You can defend yellow as being on-strategy, but suggest you&rsquo;d be happy to explore other shades of yellow or other color choices that convey &ldquo;bright, sunny, and lively.&rdquo;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BobMarche</title>
		<link>http://www.michaelgaigg.com/blog/2009/05/22/beware-of-the-frankenstein-design/comment-page-1/#comment-264</link>
		<dc:creator>BobMarche</dc:creator>
		<pubDate>Wed, 10 Jun 2009 17:25:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=406#comment-264</guid>
		<description>Thanks for the useful info. It&#039;s so interesting </description>
		<content:encoded><![CDATA[<p>Thanks for the useful info. It&#039;s so interesting</p>
]]></content:encoded>
	</item>
</channel>
</rss>

