<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Rob Enslin</title>
	<atom:link href="http://robenslin.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://robenslin.com</link>
	<description>Comments and thoughts from around the web.</description>
	<lastBuildDate>Wed, 02 Nov 2011 22:38:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on MSc HCI and ergonomics application at UCL by robenslin</title>
		<link>http://robenslin.com/2009/05/17/msc-hci/#comment-304</link>
		<dc:creator><![CDATA[robenslin]]></dc:creator>
		<pubDate>Wed, 02 Nov 2011 22:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=345#comment-304</guid>
		<description><![CDATA[No, however we were required to produce a sample and statement of previous related work.]]></description>
		<content:encoded><![CDATA[<p>No, however we were required to produce a sample and statement of previous related work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MSc HCI and ergonomics application at UCL by EP</title>
		<link>http://robenslin.com/2009/05/17/msc-hci/#comment-295</link>
		<dc:creator><![CDATA[EP]]></dc:creator>
		<pubDate>Thu, 22 Sep 2011 01:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=345#comment-295</guid>
		<description><![CDATA[Hi, I am actually in the process of writing my personal statement for UCL&#039;s program as well. One question, was it mandatory to include a project example?]]></description>
		<content:encoded><![CDATA[<p>Hi, I am actually in the process of writing my personal statement for UCL&#8217;s program as well. One question, was it mandatory to include a project example?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Typographica&#8217;s food for information design by Isabelle</title>
		<link>http://robenslin.com/2009/10/10/typographica-exhibit/#comment-293</link>
		<dc:creator><![CDATA[Isabelle]]></dc:creator>
		<pubDate>Tue, 06 Sep 2011 19:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.wordpress.com/2009/10/10/typographicas-food-for-information-design/#comment-293</guid>
		<description><![CDATA[All of my quesontis settled-thanks!]]></description>
		<content:encoded><![CDATA[<p>All of my quesontis settled-thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UX team of one by robenslin</title>
		<link>http://robenslin.com/2010/11/24/ux-team-of-one/#comment-245</link>
		<dc:creator><![CDATA[robenslin]]></dc:creator>
		<pubDate>Wed, 24 Nov 2010 10:59:58 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=555#comment-245</guid>
		<description><![CDATA[Thanks Bruce, those are really kind words... and much appreciated.]]></description>
		<content:encoded><![CDATA[<p>Thanks Bruce, those are really kind words&#8230; and much appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on UX team of one by Bruce</title>
		<link>http://robenslin.com/2010/11/24/ux-team-of-one/#comment-244</link>
		<dc:creator><![CDATA[Bruce]]></dc:creator>
		<pubDate>Wed, 24 Nov 2010 00:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=555#comment-244</guid>
		<description><![CDATA[Robbie, you my boy are an inspiration, I love the way you learn, share and have become a great communicator over the years. Keep it up, your passion is something to be desired!!!]]></description>
		<content:encoded><![CDATA[<p>Robbie, you my boy are an inspiration, I love the way you learn, share and have become a great communicator over the years. Keep it up, your passion is something to be desired!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expert reviewing a heuristic evaluation by robenslin</title>
		<link>http://robenslin.com/2010/08/06/expert-reviewing-a-heuristic-evaluation/#comment-226</link>
		<dc:creator><![CDATA[robenslin]]></dc:creator>
		<pubDate>Sat, 07 Aug 2010 08:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=509#comment-226</guid>
		<description><![CDATA[&quot;moving all technical stuff to the appendix...&quot; a great idea.]]></description>
		<content:encoded><![CDATA[<p>&#8220;moving all technical stuff to the appendix&#8230;&#8221; a great idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expert reviewing a heuristic evaluation by Katarzyna</title>
		<link>http://robenslin.com/2010/08/06/expert-reviewing-a-heuristic-evaluation/#comment-225</link>
		<dc:creator><![CDATA[Katarzyna]]></dc:creator>
		<pubDate>Fri, 06 Aug 2010 20:16:37 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=509#comment-225</guid>
		<description><![CDATA[Last time when I had to write a &quot;usability assessment summary&quot; (heuristics review + comments from a rough usability testing session) my manager asked me to re-write the first draft and &quot;dumb it down&quot; a little as it was &quot;too technical&quot; and &quot;too detailed&quot;. I got it right after a few iterations.  The document was supposed to be distributed to technical people responsible for the website and non-technical managers -- and writing two different versions wasn&#039;t an option. I managed to satisfy both groups by moving all technical stuff to the appendix.

Or I like to think I satisfied them as I didn&#039;t get any real feedback apart from my manager&#039;s initial comments. They did comment of findings but no-one mentioned the structure or the language I used.]]></description>
		<content:encoded><![CDATA[<p>Last time when I had to write a &#8220;usability assessment summary&#8221; (heuristics review + comments from a rough usability testing session) my manager asked me to re-write the first draft and &#8220;dumb it down&#8221; a little as it was &#8220;too technical&#8221; and &#8220;too detailed&#8221;. I got it right after a few iterations.  The document was supposed to be distributed to technical people responsible for the website and non-technical managers &#8212; and writing two different versions wasn&#8217;t an option. I managed to satisfy both groups by moving all technical stuff to the appendix.</p>
<p>Or I like to think I satisfied them as I didn&#8217;t get any real feedback apart from my manager&#8217;s initial comments. They did comment of findings but no-one mentioned the structure or the language I used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expert reviewing a heuristic evaluation by Kenneth Yau</title>
		<link>http://robenslin.com/2010/08/06/expert-reviewing-a-heuristic-evaluation/#comment-223</link>
		<dc:creator><![CDATA[Kenneth Yau]]></dc:creator>
		<pubDate>Fri, 06 Aug 2010 17:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=509#comment-223</guid>
		<description><![CDATA[One of the things that was continuously drummed into me during my management consultancy days was that you write for your reader. (In fact, I think there was actually a course called &#039;Write for your reader&#039;.) When you&#039;re in a client-serving business, it&#039;s simply good client service to tailor your writing according to the readership of your reports. It&#039;s actually just good writing. 

That&#039;s easier said than done, of course. Rewriting the dross served up by people who are excellent at what they do but useless at communicating it is what keeps copywriters in work.]]></description>
		<content:encoded><![CDATA[<p>One of the things that was continuously drummed into me during my management consultancy days was that you write for your reader. (In fact, I think there was actually a course called &#8216;Write for your reader&#8217;.) When you&#8217;re in a client-serving business, it&#8217;s simply good client service to tailor your writing according to the readership of your reports. It&#8217;s actually just good writing. </p>
<p>That&#8217;s easier said than done, of course. Rewriting the dross served up by people who are excellent at what they do but useless at communicating it is what keeps copywriters in work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expert reviewing a heuristic evaluation by robenslin</title>
		<link>http://robenslin.com/2010/08/06/expert-reviewing-a-heuristic-evaluation/#comment-222</link>
		<dc:creator><![CDATA[robenslin]]></dc:creator>
		<pubDate>Fri, 06 Aug 2010 13:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=509#comment-222</guid>
		<description><![CDATA[Thanks for sharing your experiences. Would be interesting to know if you ever get feedback about your actual review (not the findings of the review), from the recipient/s?]]></description>
		<content:encoded><![CDATA[<p>Thanks for sharing your experiences. Would be interesting to know if you ever get feedback about your actual review (not the findings of the review), from the recipient/s?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Expert reviewing a heuristic evaluation by Jessica Hall</title>
		<link>http://robenslin.com/2010/08/06/expert-reviewing-a-heuristic-evaluation/#comment-221</link>
		<dc:creator><![CDATA[Jessica Hall]]></dc:creator>
		<pubDate>Fri, 06 Aug 2010 12:10:54 +0000</pubDate>
		<guid isPermaLink="false">http://robenslin.com/?p=509#comment-221</guid>
		<description><![CDATA[Yes, I agree. We write different types of expert reviews for different clients. We have one which is aimed at people in general marketing roles and points out high and low priority UX issues, as well as positives, without using any jargon. For people with a more technical mindset/job role, the deliverable needs to be different.]]></description>
		<content:encoded><![CDATA[<p>Yes, I agree. We write different types of expert reviews for different clients. We have one which is aimed at people in general marketing roles and points out high and low priority UX issues, as well as positives, without using any jargon. For people with a more technical mindset/job role, the deliverable needs to be different.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
