<?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: [JOB] Worrell Needs a User Experience Designer</title>
	<atom:link href="http://mnteractive.com/archive/job-worrell-needs-a-user-experience-designer/feed" rel="self" type="application/rss+xml" />
	<link>http://mnteractive.com/archive/job-worrell-needs-a-user-experience-designer</link>
	<description>Minnesota's Interaction Design, Information Architecture, and User Experience Design Community</description>
	<lastBuildDate>Fri, 27 Apr 2012 22:37:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Garrick Van Buren</title>
		<link>http://mnteractive.com/archive/job-worrell-needs-a-user-experience-designer/comment-page-1#comment-64864</link>
		<dc:creator>Garrick Van Buren</dc:creator>
		<pubDate>Thu, 12 Nov 2009 06:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/?p=1434#comment-64864</guid>
		<description>my favorite is this one:
 http://mnteractive.com/archive/ui-and-webdev-jobs

&quot;my company is hiring. here&#039;s a link. email me if you want to know more.&quot;

It&#039;s like a haiku.</description>
		<content:encoded><![CDATA[<p>my favorite is this one:<br />
 <a href="http://mnteractive.com/archive/ui-and-webdev-jobs" rel="nofollow">http://mnteractive.com/archive/ui-and-webdev-jobs</a></p>
<p>&#8220;my company is hiring. here&#8217;s a link. email me if you want to know more.&#8221;</p>
<p>It&#8217;s like a haiku.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Frankowski</title>
		<link>http://mnteractive.com/archive/job-worrell-needs-a-user-experience-designer/comment-page-1#comment-64863</link>
		<dc:creator>Karl Frankowski</dc:creator>
		<pubDate>Wed, 11 Nov 2009 23:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/?p=1434#comment-64863</guid>
		<description>BTW Garrick, what&#039;s your #1?

K.</description>
		<content:encoded><![CDATA[<p>BTW Garrick, what&#8217;s your #1?</p>
<p>K.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Frankowski</title>
		<link>http://mnteractive.com/archive/job-worrell-needs-a-user-experience-designer/comment-page-1#comment-64862</link>
		<dc:creator>Karl Frankowski</dc:creator>
		<pubDate>Wed, 11 Nov 2009 23:04:22 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/?p=1434#comment-64862</guid>
		<description>Hi Nick,

I&#039;m a UX Designer at Worrell, and the one responsible for this job posting. Thanks for the criticism. Maybe we need to do a better job of explaining our rationale. 

Admittedly the reverse job posting is an experiment, and here are three hypotheses that we’re testing (the first two are related).

1). We are not smarter than the pool of applicants.
There’s bound to be someone smarter than us in the crowd. I hope that by eliminating boundaries rather than constructing them, we encourage a bright candidate to impress us with a better way of thinking.

2). Formulas yield predictable results.
Often, that’s the goal, but there is a flip side. Imagine if you ONLY read books suggested by Amazon’s recommendation algorithm. You would read a lot of similar books that advocate similar positions on similar issues. The algorithm doesn’t surprise you. It doesn’t lead you to discover something new. The job description is like the algorithm. It’s not a great tool for creative growth.

3). Experts recognize expertise.
As an employer, if you don’t understand the position you’re trying to fill, then keyword-matching a résumé is the best you can do to qualify an applicant. Fortunately we’re not in that position at Worrell. I’m a UX Designer, I know what the job entails. If an applicant has questions about whether or not they qualify, a Google search will offer better answers more efficiently than I could. There is a pretty good consensus online as to what a UX Designer does.

Since this is an experiment, it could go wrong. If that happens, we’ll do what we always do: assess and iterate. (We actually do that even when things go well.)

Is this risky for the job seeker? Sure, because it’s ambiguous. But you have to deal with a lot of ambiguity working for a design consultancy. At the beginning of every project there’s an anxious moment where we stare down a stunningly empty piece of paper in front of us and ask “what now?” But that’s our job. We here because we’re good at resolving ambiguity in imaginative ways. The reverse job description is asking no more of applicants than our clients ask of us. And that seems... fair.

I remove the ill-fitting HR hat from my head.

Karl.</description>
		<content:encoded><![CDATA[<p>Hi Nick,</p>
<p>I&#8217;m a UX Designer at Worrell, and the one responsible for this job posting. Thanks for the criticism. Maybe we need to do a better job of explaining our rationale. </p>
<p>Admittedly the reverse job posting is an experiment, and here are three hypotheses that we’re testing (the first two are related).</p>
<p>1). We are not smarter than the pool of applicants.<br />
There’s bound to be someone smarter than us in the crowd. I hope that by eliminating boundaries rather than constructing them, we encourage a bright candidate to impress us with a better way of thinking.</p>
<p>2). Formulas yield predictable results.<br />
Often, that’s the goal, but there is a flip side. Imagine if you ONLY read books suggested by Amazon’s recommendation algorithm. You would read a lot of similar books that advocate similar positions on similar issues. The algorithm doesn’t surprise you. It doesn’t lead you to discover something new. The job description is like the algorithm. It’s not a great tool for creative growth.</p>
<p>3). Experts recognize expertise.<br />
As an employer, if you don’t understand the position you’re trying to fill, then keyword-matching a résumé is the best you can do to qualify an applicant. Fortunately we’re not in that position at Worrell. I’m a UX Designer, I know what the job entails. If an applicant has questions about whether or not they qualify, a Google search will offer better answers more efficiently than I could. There is a pretty good consensus online as to what a UX Designer does.</p>
<p>Since this is an experiment, it could go wrong. If that happens, we’ll do what we always do: assess and iterate. (We actually do that even when things go well.)</p>
<p>Is this risky for the job seeker? Sure, because it’s ambiguous. But you have to deal with a lot of ambiguity working for a design consultancy. At the beginning of every project there’s an anxious moment where we stare down a stunningly empty piece of paper in front of us and ask “what now?” But that’s our job. We here because we’re good at resolving ambiguity in imaginative ways. The reverse job description is asking no more of applicants than our clients ask of us. And that seems&#8230; fair.</p>
<p>I remove the ill-fitting HR hat from my head.</p>
<p>Karl.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Corcodilos</title>
		<link>http://mnteractive.com/archive/job-worrell-needs-a-user-experience-designer/comment-page-1#comment-64861</link>
		<dc:creator>Nick Corcodilos</dc:creator>
		<pubDate>Wed, 11 Nov 2009 14:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/?p=1434#comment-64861</guid>
		<description>That&#039;s hilarious. I wouldn&#039;t touch that company with a 50-foot pole. Here you have some people who have no idea what the hell they&#039;re doing or what they need. This is a career disaster waiting to happen.

(Hint: Consider the difference in meaning between the same job titles/descriptions among any number of companies you care to think about. Whoever responds to this solicitation has no idea what this company needs. It&#039;s idiotic. Check my comment on the blog.)

If you want to respond, send them a note asking, &quot;What&#039;s your problem?&quot; My bet: They don&#039;t know.</description>
		<content:encoded><![CDATA[<p>That&#8217;s hilarious. I wouldn&#8217;t touch that company with a 50-foot pole. Here you have some people who have no idea what the hell they&#8217;re doing or what they need. This is a career disaster waiting to happen.</p>
<p>(Hint: Consider the difference in meaning between the same job titles/descriptions among any number of companies you care to think about. Whoever responds to this solicitation has no idea what this company needs. It&#8217;s idiotic. Check my comment on the blog.)</p>
<p>If you want to respond, send them a note asking, &#8220;What&#8217;s your problem?&#8221; My bet: They don&#8217;t know.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

