<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: Goods, Bads, and Dailies &#8211; Lessons for Conducting Great Critiques</title>
	<atom:link href="http://www.uie.com/brainsparks/2012/10/03/uietips-great-critiques/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2012/10/03/uietips-great-critiques/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Tue, 21 May 2013 10:35:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Joakim Isaksson</title>
		<link>http://www.uie.com/brainsparks/2012/10/03/uietips-great-critiques/comment-page-1/#comment-235893</link>
		<dc:creator>Joakim Isaksson</dc:creator>
		<pubDate>Fri, 12 Oct 2012 09:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=8213#comment-235893</guid>
		<description>We have a similar process in place for our software development. Due to the extensive scope of our work, our sessions are weekly, and consists of UX presenting to the rest of the team. This allows us to get quick feedback from both developers from a technical perspective and from business stakeholders from a business perspective. I really like the goods and bads technique as well as the no interruption during &quot;performance&quot; rule. Will see if we can incorporate that.</description>
		<content:encoded><![CDATA[<p>We have a similar process in place for our software development. Due to the extensive scope of our work, our sessions are weekly, and consists of UX presenting to the rest of the team. This allows us to get quick feedback from both developers from a technical perspective and from business stakeholders from a business perspective. I really like the goods and bads technique as well as the no interruption during &#8220;performance&#8221; rule. Will see if we can incorporate that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan</title>
		<link>http://www.uie.com/brainsparks/2012/10/03/uietips-great-critiques/comment-page-1/#comment-235545</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Tue, 09 Oct 2012 08:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=8213#comment-235545</guid>
		<description>That was supposed to be a link, but it seems like it was swallowed by the comment system:
http://madhatted.com/2012/10/8/process-tips-from-hitsville</description>
		<content:encoded><![CDATA[<p>That was supposed to be a link, but it seems like it was swallowed by the comment system:<br />
<a href="http://madhatted.com/2012/10/8/process-tips-from-hitsville" rel="nofollow">http://madhatted.com/2012/10/8/process-tips-from-hitsville</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johan</title>
		<link>http://www.uie.com/brainsparks/2012/10/03/uietips-great-critiques/comment-page-1/#comment-235544</link>
		<dc:creator>Johan</dc:creator>
		<pubDate>Tue, 09 Oct 2012 08:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=8213#comment-235544</guid>
		<description>It seems like Motown used a similar method of regular critiques:

&lt;blockquote&gt;Each writing/producing team was required to come up with 5 new songs per day. To accomplish this, there was a large area with a lot of little rooms, each with a piano and tape recorder.
Each team submitted their “5 best” at a weekly production meeting.
Each team got approval to record the best two of their submissions.
Usually, only one of the two tunes would emerge complete from the recording process.
Each finished tune was mixed (with about 15 different mixes by several people).
Each finished mix was turned into an actual record.
The Quality Control department listened to each record and picked out the “A” side that was released and promoted.
&lt;/blockquote&gt;

Process Tips from Hitsville</description>
		<content:encoded><![CDATA[<p>It seems like Motown used a similar method of regular critiques:</p>
<blockquote><p>Each writing/producing team was required to come up with 5 new songs per day. To accomplish this, there was a large area with a lot of little rooms, each with a piano and tape recorder.<br />
Each team submitted their “5 best” at a weekly production meeting.<br />
Each team got approval to record the best two of their submissions.<br />
Usually, only one of the two tunes would emerge complete from the recording process.<br />
Each finished tune was mixed (with about 15 different mixes by several people).<br />
Each finished mix was turned into an actual record.<br />
The Quality Control department listened to each record and picked out the “A” side that was released and promoted.
</p></blockquote>
<p>Process Tips from Hitsville</p>
]]></content:encoded>
	</item>
</channel>
</rss>
