<?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: A Bit More on Good 2.0 Design</title>
	<atom:link href="http://www.fastforwardblog.com/2007/05/24/a-bit-more-on-good-20-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2007/05/24/a-bit-more-on-good-20-design/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 11:19:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bill Ives</title>
		<link>http://www.fastforwardblog.com/2007/05/24/a-bit-more-on-good-20-design/comment-page-1/#comment-12865</link>
		<dc:creator>Bill Ives</dc:creator>
		<pubDate>Sun, 27 May 2007 00:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/05/24/a-bit-more-on-good-20-design/#comment-12865</guid>
		<description>Paula - Thanks for the links. While I may not be using aestehtics in the classic sense, a good event has a sense of harmony and flow. If the event seems awkward it is less likely to work in my expereince.  Pain is a certainly a good thing to look for. It can be caused by unnecessary complexity.  Web 2.0, if applied right, can simplify this complexity and reduce the pain.  Pain can also be caused by obstacles to communication. Once again, we can see enterprise 2.0 solutions.  There were many times in the past were I saw this enterprise pain. Solutions done in the spirit of enterprise 2.0 (prior to the tools we have now) addressed the lack of communication or the unnecessary complexity.  Bill</description>
		<content:encoded><![CDATA[<p>Paula - Thanks for the links. While I may not be using aestehtics in the classic sense, a good event has a sense of harmony and flow. If the event seems awkward it is less likely to work in my expereince.  Pain is a certainly a good thing to look for. It can be caused by unnecessary complexity.  Web 2.0, if applied right, can simplify this complexity and reduce the pain.  Pain can also be caused by obstacles to communication. Once again, we can see enterprise 2.0 solutions.  There were many times in the past were I saw this enterprise pain. Solutions done in the spirit of enterprise 2.0 (prior to the tools we have now) addressed the lack of communication or the unnecessary complexity.  Bill</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Thornton</title>
		<link>http://www.fastforwardblog.com/2007/05/24/a-bit-more-on-good-20-design/comment-page-1/#comment-12724</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Fri, 25 May 2007 19:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/05/24/a-bit-more-on-good-20-design/#comment-12724</guid>
		<description>Kudos for deep thoughts on design (always welcomed). I also like the overall concepts. I simply add a 'caution' for those who have filtered glasses on today (there seems to be a lot of that going around). There are many who apply a mindset to the term 'aesthetics' that requires caution. The typical meaning associated with aesthetics is common means by which to dismiss the true potential for design thinking. Good design being simple and good design solving the right problem is related to but not equal to esthetics (http://en.wikipedia.org/wiki/Esthetics).

The most common meaning attached to this term has to do with feeling and emotion, as elicited by visual or physical aspects of a thing. The kind of emotion I look for in design is 'pain' -- that can be elicited at a visual or physical aspect, but is more often to be found where the visual and physical aspects are all just great. Pain, is where the problems are (see the 5 ps of Design and Development, http://totalexperience.corante.com/archives/2007/03/02/the_5_ps_of_design_development.php). The highest design value can be gained first by finding and addressing points of pain.

The potential for 2.0 is finding little pains that happen a lot and big pains that we've turned into pearls (we've simply adapted to them and are now numbed to their damaging effects).</description>
		<content:encoded><![CDATA[<p>Kudos for deep thoughts on design (always welcomed). I also like the overall concepts. I simply add a &#8216;caution&#8217; for those who have filtered glasses on today (there seems to be a lot of that going around). There are many who apply a mindset to the term &#8216;aesthetics&#8217; that requires caution. The typical meaning associated with aesthetics is common means by which to dismiss the true potential for design thinking. Good design being simple and good design solving the right problem is related to but not equal to esthetics (http://en.wikipedia.org/wiki/Esthetics).</p>
<p>The most common meaning attached to this term has to do with feeling and emotion, as elicited by visual or physical aspects of a thing. The kind of emotion I look for in design is &#8216;pain&#8217; &#8212; that can be elicited at a visual or physical aspect, but is more often to be found where the visual and physical aspects are all just great. Pain, is where the problems are (see the 5 ps of Design and Development, <a href="http://totalexperience.corante.com/archives/2007/03/02/the_5_ps_of_design_development.php" rel="nofollow">http://totalexperience.corante.com/archives/2007/03/02/the_5_ps_of_design_development.php</a>). The highest design value can be gained first by finding and addressing points of pain.</p>
<p>The potential for 2.0 is finding little pains that happen a lot and big pains that we&#8217;ve turned into pearls (we&#8217;ve simply adapted to them and are now numbed to their damaging effects).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
