<?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: Best Buy tries its hand at being small.</title>
	<atom:link href="http://refactr.com/blog/2008/06/best-buy-tries-its-hand-at-being-small/feed/" rel="self" type="application/rss+xml" />
	<link>http://refactr.com/blog/2008/06/best-buy-tries-its-hand-at-being-small/</link>
	<description>informs on and evangelizes best practices of using  &#60;a href="http://refactr.com/the-agile-manifesto/"&#62;agile methods&#60;/a&#62; when designing and developing what are currently being called “Web 2.0” products and applications.</description>
	<pubDate>Wed, 07 Jan 2009 07:36:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Brent</title>
		<link>http://refactr.com/blog/2008/06/best-buy-tries-its-hand-at-being-small/#comment-15736</link>
		<dc:creator>Brent</dc:creator>
		<pubDate>Fri, 13 Jun 2008 18:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://refactr.com/blog/?p=163#comment-15736</guid>
		<description>I'd argue this model is less risky than their previous one.  It's certainly a departure from the normal corporate model, but when you look at the potential downside of that old model, and how much time and money could be wasted on something that never ends up producing, the new model just makes better business sense.  Crap ideas are thrown out before it's too late, and good ideas get more funding.

Really, the reason I like it is that it helps empower employees.  With design-by-committee projects, no one feels a sense of ownership of a process and it can be very demoralizing to a staff.  If you empower your employees to grab hold of ideas and let the best ones percolate to the top, everyone to some degree is invested in the company beyond just collecting a paycheck.  Empowered employees tend to make better products.</description>
		<content:encoded><![CDATA[<p>I&#8217;d argue this model is less risky than their previous one.  It&#8217;s certainly a departure from the normal corporate model, but when you look at the potential downside of that old model, and how much time and money could be wasted on something that never ends up producing, the new model just makes better business sense.  Crap ideas are thrown out before it&#8217;s too late, and good ideas get more funding.</p>
<p>Really, the reason I like it is that it helps empower employees.  With design-by-committee projects, no one feels a sense of ownership of a process and it can be very demoralizing to a staff.  If you empower your employees to grab hold of ideas and let the best ones percolate to the top, everyone to some degree is invested in the company beyond just collecting a paycheck.  Empowered employees tend to make better products.</p>
]]></content:encoded>
	</item>
</channel>
</rss>


