<?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: It&#8217;s Easy</title>
	<atom:link href="http://thingsthatarebrown.com/blog/2009/09/its-easy/feed/" rel="self" type="application/rss+xml" />
	<link>http://thingsthatarebrown.com/blog/2009/09/its-easy/</link>
	<description>The design blog of Matt Brown and Tiffani Jones Brown - thingsthatarebrown.com</description>
	<lastBuildDate>Mon, 16 Aug 2010 03:08:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Tom Carmony</title>
		<link>http://thingsthatarebrown.com/blog/2009/09/its-easy/comment-page-1/#comment-535</link>
		<dc:creator>Tom Carmony</dc:creator>
		<pubDate>Sun, 20 Sep 2009 06:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=724#comment-535</guid>
		<description>Great post, Matt. I&#039;ve been struggling with some of these same issues on recent client projects. You quite eloquently articulated a lot of my own frustrations.</description>
		<content:encoded><![CDATA[<p>Great post, Matt. I&#8217;ve been struggling with some of these same issues on recent client projects. You quite eloquently articulated a lot of my own&nbsp;frustrations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://thingsthatarebrown.com/blog/2009/09/its-easy/comment-page-1/#comment-533</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 18 Sep 2009 01:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=724#comment-533</guid>
		<description>@Geof: Agreed -- there seems to be agreement that development is complicated, expensive, iterative and time-consuming.  Somehow though, design is rarely afforded this patient consideration -- many still see it as a &quot;style&quot; layer, and not a full-cycle consideration.</description>
		<content:encoded><![CDATA[<p>@Geof: Agreed&thinsp;&#8212;&thinsp;there seems to be agreement that development is complicated, expensive, iterative and time-consuming.  Somehow though, design is rarely afforded this patient consideration&thinsp;&#8212;&thinsp;many still see it as a &#8220;style&#8221; layer, and not a full-cycle&nbsp;consideration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan Sharp</title>
		<link>http://thingsthatarebrown.com/blog/2009/09/its-easy/comment-page-1/#comment-532</link>
		<dc:creator>Evan Sharp</dc:creator>
		<pubDate>Fri, 18 Sep 2009 01:03:59 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=724#comment-532</guid>
		<description>Great article, Matt.

It sounds to me like you are arguing that there is a flavor of &lt;a href=&quot;http://en.wikipedia.org/wiki/Service_design&quot; rel=&quot;nofollow&quot;&gt;Service Design&lt;/a&gt; related to web design that needs to be addressed in any great web design project.

I love your point that web designers need a &quot;systematized workflow to help designers experiment&quot;. In essence, what AA, Zappos, and recent Craigslist redesigns are saying is mostly: &quot;your website is confusing and its presentation is overly-complex: here, look how easy it was for us to clean-up!&quot;. And, while this is definitely true, and I enjoy watching these designers go through the exercise, all professional designers know that the difficult part of any redesign is not making things simpler, it&#039;s making EVERYTHING simpler; it&#039;s finding that elusive balance between layout, typography, color, and interface elements that lets each piece communicate its function while also performing its function.

Word.</description>
		<content:encoded><![CDATA[<p>Great article,&nbsp;Matt.</p>
<p>It sounds to me like you are arguing that there is a flavor of <a href="http://en.wikipedia.org/wiki/Service_design" rel="nofollow">Service Design</a> related to web design that needs to be addressed in any great web design&nbsp;project.</p>
<p>I love your point that web designers need a &#8220;systematized workflow to help designers experiment&#8221;. In essence, what AA, Zappos, and recent Craigslist redesigns are saying is mostly: &#8220;your website is confusing and its presentation is overly-complex: here, look how easy it was for us to clean-up!&#8221;. And, while this is definitely true, and I enjoy watching these designers go through the exercise, all professional designers know that the difficult part of any redesign is not making things simpler, it&#8217;s making EVERYTHING simpler; it&#8217;s finding that elusive balance between layout, typography, color, and interface elements that lets each piece communicate its function while also performing its&nbsp;function.</p>
<p>Word.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nishant Kothary</title>
		<link>http://thingsthatarebrown.com/blog/2009/09/its-easy/comment-page-1/#comment-531</link>
		<dc:creator>Nishant Kothary</dc:creator>
		<pubDate>Fri, 18 Sep 2009 00:47:03 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=724#comment-531</guid>
		<description>Amen, brother. I couldn&#039;t have put it better myself. That. is. all.</description>
		<content:encoded><![CDATA[<p>Amen, brother. I couldn&#8217;t have put it better myself. That. is.&nbsp;all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geof Harries</title>
		<link>http://thingsthatarebrown.com/blog/2009/09/its-easy/comment-page-1/#comment-530</link>
		<dc:creator>Geof Harries</dc:creator>
		<pubDate>Thu, 17 Sep 2009 23:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://thingsthatarebrown.com/blog/?p=724#comment-530</guid>
		<description>This is precisely why I made the decision to grow my company beyond just a lone designer. After being involved in countless large enterprise software projects, I&#039;ve grown to dislike the &quot;vision and visuals&quot; role that design is relegated to in the engineering lifecycle. You&#039;re more than welcome in the beginning and at the front-end, but by the time the system is actually built and being maintained, it&#039;s game over. Interface &amp; interaction design needs to be, as is development, iterative and ever-changing. We need to be in there the entire time. We cannot be afraid to get our hands dirty, both in process and code - and agencies &amp; clients need to embrace that ideal.</description>
		<content:encoded><![CDATA[<p>This is precisely why I made the decision to grow my company beyond just a lone designer. After being involved in countless large enterprise software projects, I&#8217;ve grown to dislike the &#8220;vision and visuals&#8221; role that design is relegated to in the engineering lifecycle. You&#8217;re more than welcome in the beginning and at the front-end, but by the time the system is actually built and being maintained, it&#8217;s game over. Interface <span class="amp">&amp;</span> interaction design needs to be, as is development, iterative and ever-changing. We need to be in there the entire time. We cannot be afraid to get our hands dirty, both in process and code - and agencies <span class="amp">&amp;</span> clients need to embrace that&nbsp;ideal.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
