<?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 on: User Experience meets the bottom line</title>
	<atom:link href="http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/feed/" rel="self" type="application/rss+xml" />
	<link>http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/</link>
	<description>A blog about nothing...</description>
	<lastBuildDate>Mon, 15 Jun 2009 05:32:27 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: J J</title>
		<link>http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/#comment-29</link>
		<dc:creator>J J</dc:creator>
		<pubDate>Sun, 11 Mar 2007 03:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/#comment-29</guid>
		<description>i agree</description>
		<content:encoded><![CDATA[<p>i agree</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shripriya</title>
		<link>http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/#comment-10</link>
		<dc:creator>Shripriya</dc:creator>
		<pubDate>Wed, 07 Feb 2007 04:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/#comment-10</guid>
		<description>It&#039;s a tough balance. I agree with you that slapping on any Web 2.0 idea is silly and given the development cycle and process at eBay, also hard to justify.

However, I do think there has to be a slot for innovation and incorporating ideas into the main site.  And most importantly, the way you measure impact has to change.

For example, allowing the community to blog - would it have increased revenues? No. Would it have cost money? Yes. Would it have increased the feeling of community? Yes. Would it have improved eBay&#039;s presence in natural search? Absolutely. 

However, an idea that was proposed in 2003 has yet to happen. To me, that&#039;s a shame. It wasn&#039;t implemented because compared to US Core revenues or a new feature, it is less than a drop in the bucket. But then, you are not valuing customer loyalty and stickiness and all those things that actually do have value. Large companies have to find a way to measure these things.

Btw, I like your product posts a lot - nice job! :)

[PS: Can you get the &quot;subscribe to comments&quot; plugin? That way if there is a followup, the commenters will get an email - http://www.scriptygoddess.com/archives/2004/06/03/wp-subscribe-to-comments/]</description>
		<content:encoded><![CDATA[<p>It&#8217;s a tough balance. I agree with you that slapping on any Web 2.0 idea is silly and given the development cycle and process at eBay, also hard to justify.</p>
<p>However, I do think there has to be a slot for innovation and incorporating ideas into the main site.  And most importantly, the way you measure impact has to change.</p>
<p>For example, allowing the community to blog &#8211; would it have increased revenues? No. Would it have cost money? Yes. Would it have increased the feeling of community? Yes. Would it have improved eBay&#8217;s presence in natural search? Absolutely. </p>
<p>However, an idea that was proposed in 2003 has yet to happen. To me, that&#8217;s a shame. It wasn&#8217;t implemented because compared to US Core revenues or a new feature, it is less than a drop in the bucket. But then, you are not valuing customer loyalty and stickiness and all those things that actually do have value. Large companies have to find a way to measure these things.</p>
<p>Btw, I like your product posts a lot &#8211; nice job! :)</p>
<p>[PS: Can you get the &#8220;subscribe to comments&#8221; plugin? That way if there is a followup, the commenters will get an email &#8211; <a href="http://www.scriptygoddess.com/archives/2004/06/03/wp-subscribe-to-comments/" rel="nofollow">http://www.scriptygoddess.com/archives/2004/06/03/wp-subscribe-to-comments/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yet Another Product Manager</title>
		<link>http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/#comment-5</link>
		<dc:creator>Yet Another Product Manager</dc:creator>
		<pubDate>Fri, 02 Feb 2007 16:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://eseema.wordpress.com/2007/01/29/user-experience-meets-the-bottom-line/#comment-5</guid>
		<description>The last paragraph of your blog pretty much sums up the entire discussion. Large companies find it hard to justify small changes in the UI. As such the UI goes neglected for a long time and the change is only deemed necessary when an internal feature improvement mandates a UI change.

There could be two ways to justify the UI improvements
- Include it as 30% of maintenance/engineering/baseline changes necessary to sustain the product over a 5-year plan.
- Measure the UI improvements in terms of lowered costs to support, lowered costs to maintain documentation, lowered costs to escalations etc.

The latter is hard to do and quantify.</description>
		<content:encoded><![CDATA[<p>The last paragraph of your blog pretty much sums up the entire discussion. Large companies find it hard to justify small changes in the UI. As such the UI goes neglected for a long time and the change is only deemed necessary when an internal feature improvement mandates a UI change.</p>
<p>There could be two ways to justify the UI improvements<br />
- Include it as 30% of maintenance/engineering/baseline changes necessary to sustain the product over a 5-year plan.<br />
- Measure the UI improvements in terms of lowered costs to support, lowered costs to maintain documentation, lowered costs to escalations etc.</p>
<p>The latter is hard to do and quantify.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
