<?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: &#8220;Obscure and pregnant with conflicting meanings&#8221;</title>
	<atom:link href="http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/12/obscure-and-pregant.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/12/obscure-and-pregant.html</link>
	<description>Kevin Ertell serves up a cocktail of e-retail and cross-channel strategies, tactics, observations, and ideas.</description>
	<lastBuildDate>Tue, 07 Feb 2012 18:29:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: John H</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/12/obscure-and-pregant.html/comment-page-1#comment-198</link>
		<dc:creator>John H</dc:creator>
		<pubDate>Thu, 24 Dec 2009 14:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevinertell.com/retail-shaken-not-stirred/2009/12/16/obscure-and-pregnant-with-conflicting-meanings/#comment-198</guid>
		<description>I really like your ideas about Scenario Imagination. I can see how they would help us all do a better job finding problems in our plans. I&#039;ve got some major straget planning going on in January, and I&#039;m going to try this technique out with our team. Thanks for the great idea!</description>
		<content:encoded><![CDATA[<p>I really like your ideas about Scenario Imagination. I can see how they would help us all do a better job finding problems in our plans. I&#8217;ve got some major straget planning going on in January, and I&#8217;m going to try this technique out with our team. Thanks for the great idea!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ertell</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/12/obscure-and-pregant.html/comment-page-1#comment-189</link>
		<dc:creator>Kevin Ertell</dc:creator>
		<pubDate>Sat, 19 Dec 2009 00:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevinertell.com/retail-shaken-not-stirred/2009/12/16/obscure-and-pregnant-with-conflicting-meanings/#comment-189</guid>
		<description>Thanks for your comments, Chris. It&#039;s easy to get so optimistic on big projects that you lose site of the problem. Certainly, planning a 90% probability of success can cause some blindness to fairly obvious problems. And your point about spending to unrealistic projections is a good one. Thanks again for contributing to the conversation.
</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Chris. It&#8217;s easy to get so optimistic on big projects that you lose site of the problem. Certainly, planning a 90% probability of success can cause some blindness to fairly obvious problems. And your point about spending to unrealistic projections is a good one. Thanks again for contributing to the conversation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Eagle</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/12/obscure-and-pregant.html/comment-page-1#comment-188</link>
		<dc:creator>Chris Eagle</dc:creator>
		<pubDate>Fri, 18 Dec 2009 19:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevinertell.com/retail-shaken-not-stirred/2009/12/16/obscure-and-pregnant-with-conflicting-meanings/#comment-188</guid>
		<description>This strikes me as being related to your article on why Amazon can innovate.  Many companies ONLY look at the upside, or perfect scenario.  Even when they do contingency planning it’s only something that really won’t happen and they only go through the empty motions.  And when they deal with the problem that the dog got out, they generally only put in changes to stop the dog from getting out, not to prevent all of the other things that could happen because the door was open and unattended.
I have been involved with many companies where every project was planned to have a 90% chance of best case scenario and a 10% chance of almost-best-case scenario, and then got upset whenever the project didn’t meet those goals.  Worse yet, they often spent to those projections and then ended up hemorrhaging money because they didn’t get the projected return.
</description>
		<content:encoded><![CDATA[<p>This strikes me as being related to your article on why Amazon can innovate.  Many companies ONLY look at the upside, or perfect scenario.  Even when they do contingency planning it’s only something that really won’t happen and they only go through the empty motions.  And when they deal with the problem that the dog got out, they generally only put in changes to stop the dog from getting out, not to prevent all of the other things that could happen because the door was open and unattended.<br />
I have been involved with many companies where every project was planned to have a 90% chance of best case scenario and a 10% chance of almost-best-case scenario, and then got upset whenever the project didn’t meet those goals.  Worse yet, they often spent to those projections and then ended up hemorrhaging money because they didn’t get the projected return.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ertell</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/12/obscure-and-pregant.html/comment-page-1#comment-187</link>
		<dc:creator>Kevin Ertell</dc:creator>
		<pubDate>Wed, 16 Dec 2009 21:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevinertell.com/retail-shaken-not-stirred/2009/12/16/obscure-and-pregnant-with-conflicting-meanings/#comment-187</guid>
		<description>Excellent points, Kasey, about maintaining the business case. Certainly, things change both internally and externally during the life of a project, and those changes can absolutely affect the original business case. I really appreciate you adding to the conversation.
Also, funny comment at the end. I laughed...and I cried. :-)
</description>
		<content:encoded><![CDATA[<p>Excellent points, Kasey, about maintaining the business case. Certainly, things change both internally and externally during the life of a project, and those changes can absolutely affect the original business case. I really appreciate you adding to the conversation.<br />
Also, funny comment at the end. I laughed&#8230;and I cried. <img src='http://www.retailshakennotstirred.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kasey Lobaugh</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/12/obscure-and-pregant.html/comment-page-1#comment-186</link>
		<dc:creator>Kasey Lobaugh</dc:creator>
		<pubDate>Wed, 16 Dec 2009 21:16:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.kevinertell.com/retail-shaken-not-stirred/2009/12/16/obscure-and-pregnant-with-conflicting-meanings/#comment-186</guid>
		<description>Thanks Kevin for another insightful blog posting.   My own experience says that there may be another element that is often times missing in an organization, and that is continual business case monitoring.
My experience says that organizations tend to develop a business case to get initial funding, but once that is done, the business case goes on the shelf.    But immediately, things begin to change.  Scope changes, assumptions prove incorrect, timelines change, costs overruns occur, but the business case is seldom managed as a living thing by which organizations continue to make decisions.
Just as important as risk management (contingency planning), and scenario imagination are, I would add on-going business case management to the list.
Reading your article brings a specific incident to mind where a client of mine said &#039;Why do we have to keep talking about the risks, it just brings everyone down!&#039;
Kasey Lobaugh
Multi-Channel Retail Practice Leader
Deloitte
</description>
		<content:encoded><![CDATA[<p>Thanks Kevin for another insightful blog posting.   My own experience says that there may be another element that is often times missing in an organization, and that is continual business case monitoring.<br />
My experience says that organizations tend to develop a business case to get initial funding, but once that is done, the business case goes on the shelf.    But immediately, things begin to change.  Scope changes, assumptions prove incorrect, timelines change, costs overruns occur, but the business case is seldom managed as a living thing by which organizations continue to make decisions.<br />
Just as important as risk management (contingency planning), and scenario imagination are, I would add on-going business case management to the list.<br />
Reading your article brings a specific incident to mind where a client of mine said &#8216;Why do we have to keep talking about the risks, it just brings everyone down!&#8217;<br />
Kasey Lobaugh<br />
Multi-Channel Retail Practice Leader<br />
Deloitte</p>
]]></content:encoded>
	</item>
</channel>
</rss>

