<?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"
	>
<channel>
	<title>Comments on: Where&#8217;s Your Resolve?</title>
	<atom:link href="http://experiencematters.criticalmass.com/2007/12/20/wheres-your-resolve/feed/" rel="self" type="application/rss+xml" />
	<link>http://experiencematters.criticalmass.com/2007/12/20/wheres-your-resolve/</link>
	<description>Great customer experiences and what it takes to pull them off</description>
	<pubDate>Tue, 06 Jan 2009 07:48:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Joel</title>
		<link>http://experiencematters.criticalmass.com/2007/12/20/wheres-your-resolve/#comment-362</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Fri, 21 Dec 2007 15:55:24 +0000</pubDate>
		<guid isPermaLink="false">http://10.98.16.51/experience-matters/?p=108#comment-362</guid>
		<description>Optimization is a resolution that resonates with me as well - a slow website and freezing videos quickly ruin the user experience - but I think that it costs less and is more efficient to promote (both internally and externally) methodologies that produce optimized solutions the first time around, rather than try to optimize post-launch.

It takes a team of developers relatively less time (before &#38; during implementation) to identify and communicate potential performance bottlenecks v/s post-launch optimizing a bigger system without breaking something else. I understand that having a clear budget percentage allocated to optimization makes a lot of sense from the billing and corporate point of view, but from the development POV, I believe it's in the clients' best interest when there's less code rewrite involved.</description>
		<content:encoded><![CDATA[<p>Optimization is a resolution that resonates with me as well - a slow website and freezing videos quickly ruin the user experience - but I think that it costs less and is more efficient to promote (both internally and externally) methodologies that produce optimized solutions the first time around, rather than try to optimize post-launch.</p>
<p>It takes a team of developers relatively less time (before &amp; during implementation) to identify and communicate potential performance bottlenecks v/s post-launch optimizing a bigger system without breaking something else. I understand that having a clear budget percentage allocated to optimization makes a lot of sense from the billing and corporate point of view, but from the development POV, I believe it&#8217;s in the clients&#8217; best interest when there&#8217;s less code rewrite involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Cheverie</title>
		<link>http://experiencematters.criticalmass.com/2007/12/20/wheres-your-resolve/#comment-361</link>
		<dc:creator>Colin Cheverie</dc:creator>
		<pubDate>Fri, 21 Dec 2007 15:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://10.98.16.51/experience-matters/?p=108#comment-361</guid>
		<description>Great thoughts here Neil -- send the troops off for the holidays with something to think of.

Further to your "Watch, listen and take action"; let's learn to stop to smell the roses from time to time! What do I mean? Let's take a look at the work being done by our fantastic project teams. That might mean hitting up the Dell lead at lunch, or checking out Hyatt.com for possibly the first time. Get in tune with what is happening around us.

And better yet, contribute! If you are doing something you think needs to be heard, First Fridays beercamp is a perfect forum. Or maybe even write a pattern in the Design Pattern Library (we have one? - Yes! Search in on our wiki!) or check out what's happening with one of our many Communities of Practice (yes, check the wiki or blogs again!).

In 2007, we heard the term "innovation" quite a bit. I still hope to hear it a lot more in 2008, but let's add "contribute" to that, and see what the hell happens.

Happy Holidays!
Colin</description>
		<content:encoded><![CDATA[<p>Great thoughts here Neil &#8212; send the troops off for the holidays with something to think of.</p>
<p>Further to your &#8220;Watch, listen and take action&#8221;; let&#8217;s learn to stop to smell the roses from time to time! What do I mean? Let&#8217;s take a look at the work being done by our fantastic project teams. That might mean hitting up the Dell lead at lunch, or checking out Hyatt.com for possibly the first time. Get in tune with what is happening around us.</p>
<p>And better yet, contribute! If you are doing something you think needs to be heard, First Fridays beercamp is a perfect forum. Or maybe even write a pattern in the Design Pattern Library (we have one? - Yes! Search in on our wiki!) or check out what&#8217;s happening with one of our many Communities of Practice (yes, check the wiki or blogs again!).</p>
<p>In 2007, we heard the term &#8220;innovation&#8221; quite a bit. I still hope to hear it a lot more in 2008, but let&#8217;s add &#8220;contribute&#8221; to that, and see what the hell happens.</p>
<p>Happy Holidays!<br />
Colin</p>
]]></content:encoded>
	</item>
</channel>
</rss>
