<?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: The anatomy of useful feedback</title>
	<atom:link href="http://www.callmejeffrey.com/2009/11/14/the-anatomy-of-useful-feedback/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.callmejeffrey.com/2009/11/14/the-anatomy-of-useful-feedback/</link>
	<description>The Blog of Jeffrey Kalmikoff</description>
	<lastBuildDate>Tue, 24 Aug 2010 07:29:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Sally Carson</title>
		<link>http://www.callmejeffrey.com/2009/11/14/the-anatomy-of-useful-feedback/comment-page-1/#comment-77275</link>
		<dc:creator>Sally Carson</dc:creator>
		<pubDate>Mon, 25 Jan 2010 20:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.callmejeffrey.com/?p=658#comment-77275</guid>
		<description>Cool. I really like that you went through the exercise of a design review, following your own rules for how it should be conducted. 

Guiding non-designers through design reviews is super critical to what we do. It&#039;s our job to ensure that everyone feels they&#039;ve been heard and that we get some useful, actionable feedback.

It seems that the more you&#039;re able to include the larger team (outside of design), the more everyone feels that the product is a collaborative effort. This is huge for morale, motivation, and maintaining a positive rapport between designers &amp; the rest of the crew.  Basically, make the process participatory = stoked crew.</description>
		<content:encoded><![CDATA[<p>Cool. I really like that you went through the exercise of a design review, following your own rules for how it should be conducted. </p>
<p>Guiding non-designers through design reviews is super critical to what we do. It&#8217;s our job to ensure that everyone feels they&#8217;ve been heard and that we get some useful, actionable feedback.</p>
<p>It seems that the more you&#8217;re able to include the larger team (outside of design), the more everyone feels that the product is a collaborative effort. This is huge for morale, motivation, and maintaining a positive rapport between designers &amp; the rest of the crew.  Basically, make the process participatory = stoked crew.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EverydayUX morsels (January 12th &#8211; January 13th)</title>
		<link>http://www.callmejeffrey.com/2009/11/14/the-anatomy-of-useful-feedback/comment-page-1/#comment-77273</link>
		<dc:creator>EverydayUX morsels (January 12th &#8211; January 13th)</dc:creator>
		<pubDate>Wed, 13 Jan 2010 21:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.callmejeffrey.com/?p=658#comment-77273</guid>
		<description>[...] The anatomy of useful feedback &#8211; Jeffrey Kalmikoff, Creative Powerhouse.Great piece on the benefits of soliciting cross-disciplinary feedback throughout your process. [...]</description>
		<content:encoded><![CDATA[<p>[...] The anatomy of useful feedback &ndash; Jeffrey Kalmikoff, Creative Powerhouse.Great piece on the benefits of soliciting cross-disciplinary feedback throughout your process. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Schumann</title>
		<link>http://www.callmejeffrey.com/2009/11/14/the-anatomy-of-useful-feedback/comment-page-1/#comment-77166</link>
		<dc:creator>Chris Schumann</dc:creator>
		<pubDate>Sat, 21 Nov 2009 00:51:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.callmejeffrey.com/?p=658#comment-77166</guid>
		<description>Great post, I&#039;ve been confused myself with friends photos. I really like the format you suggest for design feedback, it really forces the user to put a lot of thought into what the real issue is and how you can address it.</description>
		<content:encoded><![CDATA[<p>Great post, I&#8217;ve been confused myself with friends photos. I really like the format you suggest for design feedback, it really forces the user to put a lot of thought into what the real issue is and how you can address it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Six secrets: design lessons and shoelace knots &#171; Design and Innovation Daily</title>
		<link>http://www.callmejeffrey.com/2009/11/14/the-anatomy-of-useful-feedback/comment-page-1/#comment-77165</link>
		<dc:creator>Six secrets: design lessons and shoelace knots &#171; Design and Innovation Daily</dc:creator>
		<pubDate>Wed, 18 Nov 2009 08:22:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.callmejeffrey.com/?p=658#comment-77165</guid>
		<description>[...] Six secrets: design lessons and shoelace&#160;knots  Posted in designers, graphic design, methodology, user research by Dan on November 18, 2009   Picking up from yesterday&#8217;s topic, Jeffrey Kalmikoff, director of design and user experience at Digg, recently wrote about getting useful feedback. &#8220;If someone uses the product, they have a valid point of view &#8211; period.&#8221; In counterpoint to &#8220;When Not To Listen To Users,&#8221; you need to prompt feedback in the right way and interpret the right parts of the feedback. Here&#8217;s the post: The Anatomy of Useful Feedback [...]</description>
		<content:encoded><![CDATA[<p>[...] Six secrets: design lessons and shoelace&nbsp;knots  Posted in designers, graphic design, methodology, user research by Dan on November 18, 2009   Picking up from yesterday&#8217;s topic, Jeffrey Kalmikoff, director of design and user experience at Digg, recently wrote about getting useful feedback. &#8220;If someone uses the product, they have a valid point of view &ndash; period.&#8221; In counterpoint to &#8220;When Not To Listen To Users,&#8221; you need to prompt feedback in the right way and interpret the right parts of the feedback. Here&#8217;s the post: The Anatomy of Useful Feedback [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saeed Jabbar</title>
		<link>http://www.callmejeffrey.com/2009/11/14/the-anatomy-of-useful-feedback/comment-page-1/#comment-77162</link>
		<dc:creator>Saeed Jabbar</dc:creator>
		<pubDate>Sat, 14 Nov 2009 20:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.callmejeffrey.com/?p=658#comment-77162</guid>
		<description>Good read. Over at Vayner Media we have a round table discussion about the prospective design due to our small size but I will suggest emailing in suggestion. It is more concrete and you gain everyone&#039;s input. Google Wave sounds useful for this too since it provides a timeline.</description>
		<content:encoded><![CDATA[<p>Good read. Over at Vayner Media we have a round table discussion about the prospective design due to our small size but I will suggest emailing in suggestion. It is more concrete and you gain everyone&#8217;s input. Google Wave sounds useful for this too since it provides a timeline.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
