<?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 for You the User</title>
	<atom:link href="http://youtheuser.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://youtheuser.com</link>
	<description>little ideas keep growing</description>
	<lastBuildDate>Fri, 29 Jan 2010 07:18:39 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on As little design as possible but as much help as you can get by Nick</title>
		<link>http://youtheuser.com/2010/01/28/as-little-design-as-possible-but-as-much-help-as-you-can-get/comment-page-1/#comment-106</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Fri, 29 Jan 2010 07:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://youtheuser.com/?p=313#comment-106</guid>
		<description>Hiya, the title of this post is similar to this weeks post at www.userexperience.co.nz
I&#039;ve photographed a couple of &#039;innovative&#039; car door handles which have managed to dodge the process which all those quoted above recommend.
One is simplified to breaking point, the other complicated to frustration point.

http://www.userexperience.co.nz/2010/01/when-less-is-not-more-and-more-is-too-much/

Nick</description>
		<content:encoded><![CDATA[<p>Hiya, the title of this post is similar to this weeks post at <a href="http://www.userexperience.co.nz" rel="nofollow">http://www.userexperience.co.nz</a><br />
I&#8217;ve photographed a couple of &#8216;innovative&#8217; car door handles which have managed to dodge the process which all those quoted above recommend.<br />
One is simplified to breaking point, the other complicated to frustration point.</p>
<p><a href="http://www.userexperience.co.nz/2010/01/when-less-is-not-more-and-more-is-too-much/" rel="nofollow">http://www.userexperience.co.nz/2010/01/when-less-is-not-more-and-more-is-too-much/</a></p>
<p>Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Like buying a puff of air by Ian Fenn</title>
		<link>http://youtheuser.com/2010/01/11/like-buying-a-puff-of-air/comment-page-1/#comment-84</link>
		<dc:creator>Ian Fenn</dc:creator>
		<pubDate>Mon, 11 Jan 2010 16:59:36 +0000</pubDate>
		<guid isPermaLink="false">http://youtheuser.com/?p=306#comment-84</guid>
		<description>And that&#039;ll be why I continue, I&#039;m afraid, to buy physical music where possible... Even when it comes to vintage tracks, I&#039;m trawling second-hand music stores and charity shops...</description>
		<content:encoded><![CDATA[<p>And that&#8217;ll be why I continue, I&#8217;m afraid, to buy physical music where possible&#8230; Even when it comes to vintage tracks, I&#8217;m trawling second-hand music stores and charity shops&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CV format &#8211; is it broken? Does it need fixing by CV format – is it broken? Does it need fixing (UPDATE)</title>
		<link>http://youtheuser.com/2009/12/23/cv-format-is-it-broken-does-it-need-fixing/comment-page-1/#comment-80</link>
		<dc:creator>CV format – is it broken? Does it need fixing (UPDATE)</dc:creator>
		<pubDate>Mon, 04 Jan 2010 21:52:23 +0000</pubDate>
		<guid isPermaLink="false">http://youtheuser.com/?p=177#comment-80</guid>
		<description>[...] update to previous article about CVs is that I have updated the CV Grid [...]</description>
		<content:encoded><![CDATA[<p>[...] update to previous article about CVs is that I have updated the CV Grid [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on To portfolio or not to portfolio, that is the question by Jason Mesut</title>
		<link>http://youtheuser.com/2009/12/30/to-portfolio-or-not-to-portfolio-that-is-the-question/comment-page-1/#comment-77</link>
		<dc:creator>Jason Mesut</dc:creator>
		<pubDate>Wed, 30 Dec 2009 10:21:15 +0000</pubDate>
		<guid isPermaLink="false">http://youtheuser.com/?p=243#comment-77</guid>
		<description>Love the sentiment of this article - portfolios should definitely show more than just finished work. It&#039;s a portfolio of process as much as polish - if not more process than polish. 

I do, however, challenge the notion that a portfolio should be self-explanatory. It can take a really long time to do this, and it&#039;s easier to just pull out relevant examples as part of a conversation. It would take me about a week of clear time to do this for my portfolio, and to be honest I&#039;m always going to be too busy for that. Is that arrogance? Maybe, but for me, it&#039;s just pragmatic.

The issue of NDAs is a tricky one. If you have ever done any decent paid work for a decent &#039;known&#039; organisation it is likely to be under some sort of NDA. I don&#039;t want to urge people to break the law, but for decades designers have shown work that is technically confidential and shouldn&#039;t be shared. But, an interview is a place of confidentiality anyway. You will probably say things that you wouldn&#039;t want spread around the industry (to your current boss, your colleagues, your ex-boss). And the interviewers are not likely to rip off your ideas or your wireframes. Seriously, they are really not likely to. The chances of them remembering what they saw when a relevant project comes up are very low.

So, I get incredibly frustrated when interviewees pull the NDA card as an excuse for not showing some of their &#039;interesting&#039; work. If you really can&#039;t bring yourself to share the work that you have done to get the job that you want by proving what you can do, you are really missing out as an interviewer really can&#039;t make such a leap of faith in your abilities just on your say so. 

But there is an alternative... You could always de-brand the work, recreating it in a way that the original client is not identifiable. Or, as the article points out, show some non-work work. Side projects, thought leadership, failed projects, pitch work etc.

I hope that every User Experience person in our industry that is planning on taking themselves to an interview can take note of this article and be respectful of both the interviewer&#039;s time and their need to see how you work so they can have faith that you can help them deliver work for their clients.</description>
		<content:encoded><![CDATA[<p>Love the sentiment of this article &#8211; portfolios should definitely show more than just finished work. It&#8217;s a portfolio of process as much as polish &#8211; if not more process than polish. </p>
<p>I do, however, challenge the notion that a portfolio should be self-explanatory. It can take a really long time to do this, and it&#8217;s easier to just pull out relevant examples as part of a conversation. It would take me about a week of clear time to do this for my portfolio, and to be honest I&#8217;m always going to be too busy for that. Is that arrogance? Maybe, but for me, it&#8217;s just pragmatic.</p>
<p>The issue of NDAs is a tricky one. If you have ever done any decent paid work for a decent &#8216;known&#8217; organisation it is likely to be under some sort of NDA. I don&#8217;t want to urge people to break the law, but for decades designers have shown work that is technically confidential and shouldn&#8217;t be shared. But, an interview is a place of confidentiality anyway. You will probably say things that you wouldn&#8217;t want spread around the industry (to your current boss, your colleagues, your ex-boss). And the interviewers are not likely to rip off your ideas or your wireframes. Seriously, they are really not likely to. The chances of them remembering what they saw when a relevant project comes up are very low.</p>
<p>So, I get incredibly frustrated when interviewees pull the NDA card as an excuse for not showing some of their &#8216;interesting&#8217; work. If you really can&#8217;t bring yourself to share the work that you have done to get the job that you want by proving what you can do, you are really missing out as an interviewer really can&#8217;t make such a leap of faith in your abilities just on your say so. </p>
<p>But there is an alternative&#8230; You could always de-brand the work, recreating it in a way that the original client is not identifiable. Or, as the article points out, show some non-work work. Side projects, thought leadership, failed projects, pitch work etc.</p>
<p>I hope that every User Experience person in our industry that is planning on taking themselves to an interview can take note of this article and be respectful of both the interviewer&#8217;s time and their need to see how you work so they can have faith that you can help them deliver work for their clients.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
