<?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: User Experience in the Agency World</title>
	<atom:link href="http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html</link>
	<description>Michael Krotscheck's insights, ideas, and inspirations about web technology, life, and the kitchen sink.</description>
	<lastBuildDate>Fri, 03 Feb 2012 05:12:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Andrew Schechterman</title>
		<link>http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html/comment-page-1#comment-522</link>
		<dc:creator>Andrew Schechterman</dc:creator>
		<pubDate>Mon, 07 Jul 2008 17:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html#comment-522</guid>
		<description>Michael, You&#039;re onto something that many still are not, despite the lessons of the dot-com. The quality of the relationship with, and depth of collaboration with the client is paramount. Even the most comprehensive user-centered design method and process, and resulting superior UX, cannot trump an ambivalent or poorly defined client relationship. Taking the time to build the day-to-day working partnership has little to do with our technical, design or craft expertise per se. If we do it well, it usually means many (many) years of happy marriage . . . indeed, when the &quot;parents&quot; are communicating well, the end-users have everything to gain. A lot of psychology, a lot of listening, and the building of trust over time. Have always liked Peter Block&#039;s early business books as he had the courage to say that the bulk of our work within one&#039;s own company or agency, or with another company or agency, has everything to do with personal skills. I know it initially disappointed his C-level readership, then they got it and pushed his books to the best seller lists. Keep up the great postings, kudos!   - AS</description>
		<content:encoded><![CDATA[<p>Michael, You&#8217;re onto something that many still are not, despite the lessons of the dot-com. The quality of the relationship with, and depth of collaboration with the client is paramount. Even the most comprehensive user-centered design method and process, and resulting superior UX, cannot trump an ambivalent or poorly defined client relationship. Taking the time to build the day-to-day working partnership has little to do with our technical, design or craft expertise per se. If we do it well, it usually means many (many) years of happy marriage . . . indeed, when the &#8220;parents&#8221; are communicating well, the end-users have everything to gain. A lot of psychology, a lot of listening, and the building of trust over time. Have always liked Peter Block&#8217;s early business books as he had the courage to say that the bulk of our work within one&#8217;s own company or agency, or with another company or agency, has everything to do with personal skills. I know it initially disappointed his C-level readership, then they got it and pushed his books to the best seller lists. Keep up the great postings, kudos!   &#8211; AS</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea Hill</title>
		<link>http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html/comment-page-1#comment-488</link>
		<dc:creator>Andrea Hill</dc:creator>
		<pubDate>Sat, 05 Jul 2008 05:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html#comment-488</guid>
		<description>oh and P.S. 99% of the time the client doesnt know what the user wants, anyway.</description>
		<content:encoded><![CDATA[<p>oh and P.S. 99% of the time the client doesnt know what the user wants, anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrea Hill</title>
		<link>http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html/comment-page-1#comment-487</link>
		<dc:creator>Andrea Hill</dc:creator>
		<pubDate>Sat, 05 Jul 2008 05:25:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.krotscheck.net/2008/07/04/user-experience-in-the-agency-world.html#comment-487</guid>
		<description>I SOO have to read this book! Although it may make me even more eager to return to the UX space. 

When I worked at LexisNexis, it was described to me that we were the user&#039;s voice at the decision table. You have the business folks, the tech folks, the marketing folks, the PMs.. and who speaks for the user? That&#039;s what UX is for. 

It&#039;s really what drives everything I do: when features are considered, I try to think if there are benefits for a user. A major one is authentication or registration for a service. It&#039;s fine and dandy to create the functionality, but we have to think of why the user would be motivated to use the feature. You know those services you see  (generally butt ugly, but that&#039;s beside the fact), and you just know a developer built it? Because there&#039;s all sorts of neat-o features he enjoyed building, but they may or may not be useful. 

It&#039;s funny you mention tech leading projects, because actually Jesse James Garrett&#039;s diagram of the elements of UX doesn&#039;t even include tech...</description>
		<content:encoded><![CDATA[<p>I SOO have to read this book! Although it may make me even more eager to return to the UX space. </p>
<p>When I worked at LexisNexis, it was described to me that we were the user&#8217;s voice at the decision table. You have the business folks, the tech folks, the marketing folks, the PMs.. and who speaks for the user? That&#8217;s what UX is for. </p>
<p>It&#8217;s really what drives everything I do: when features are considered, I try to think if there are benefits for a user. A major one is authentication or registration for a service. It&#8217;s fine and dandy to create the functionality, but we have to think of why the user would be motivated to use the feature. You know those services you see  (generally butt ugly, but that&#8217;s beside the fact), and you just know a developer built it? Because there&#8217;s all sorts of neat-o features he enjoyed building, but they may or may not be useful. </p>
<p>It&#8217;s funny you mention tech leading projects, because actually Jesse James Garrett&#8217;s diagram of the elements of UX doesn&#8217;t even include tech&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

