<?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: UIE Tips: What Goes into a Well-Done Critique?</title>
	<atom:link href="http://www.uie.com/brainsparks/2012/04/24/uie-tips-critique-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2012/04/24/uie-tips-critique-3/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Wed, 22 May 2013 21:10:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Michele Ide-Smith</title>
		<link>http://www.uie.com/brainsparks/2012/04/24/uie-tips-critique-3/comment-page-1/#comment-216829</link>
		<dc:creator>Michele Ide-Smith</dc:creator>
		<pubDate>Sat, 28 Apr 2012 06:55:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=6956#comment-216829</guid>
		<description>The things that have worked really well for me in design critiques are:
- having a set of &#039;rules&#039; on the wall, encouraging any feedback and explaining how the session will work
- inviting the whole project team and colleagues in other teams if possible (including developers, testers, project managers, product managers, technical authors and other user experience practitioners)
- running through the designs with everyone when they arrive
- standing back and listening in to what people have to say about the designs, rather than defending design decisions
- asking people to put comments and ideas on sticky notes on the relevant designs - we then review the comments and suggestions together and discuss them (at this point I try to remain in a facilitator role, but explain reasons behind the designs without being defensive)
- offering chocolates or biscuits to encourage team members to come along!</description>
		<content:encoded><![CDATA[<p>The things that have worked really well for me in design critiques are:<br />
- having a set of &#8216;rules&#8217; on the wall, encouraging any feedback and explaining how the session will work<br />
- inviting the whole project team and colleagues in other teams if possible (including developers, testers, project managers, product managers, technical authors and other user experience practitioners)<br />
- running through the designs with everyone when they arrive<br />
- standing back and listening in to what people have to say about the designs, rather than defending design decisions<br />
- asking people to put comments and ideas on sticky notes on the relevant designs &#8211; we then review the comments and suggestions together and discuss them (at this point I try to remain in a facilitator role, but explain reasons behind the designs without being defensive)<br />
- offering chocolates or biscuits to encourage team members to come along!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
