<?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: Decision Delusions</title>
	<atom:link href="http://blogs.gartner.com/tom_austin/2009/06/11/decision-delusions/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/tom_austin/2009/06/11/decision-delusions/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Wed, 16 Feb 2011 20:55:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Betsy Burton</title>
		<link>http://blogs.gartner.com/tom_austin/2009/06/11/decision-delusions/comment-page-1/#comment-95</link>
		<dc:creator>Betsy Burton</dc:creator>
		<pubDate>Thu, 11 Jun 2009 21:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/tom_austin/2009/06/11/decision-delusions/#comment-95</guid>
		<description>Tom -

Your posting reminds me of a “behind the scenes” tour of a major gambling casino that I had the pleasure of taking (…don’t ask why…that is a whole different posting). The executive giving the tour explained that at one time they considered automating the job of the pit bosses by creating an RFID-based system that tracked all the card, dice, chip and even drink movements on the gambling table. By the way..I learned that the pit bosses are the ones walking around the casino tracking and managing the floor. The casino did a pilot program and tried the computerized system out. In the end, they found that it couldn’t compare to the accuracy and speed of the pit bosses. 

Why not??? Thinking like a geek…I was pondering the details. Was it a problem with the RFID chips, maybe the data transfer…maybe the issue was with the analytics tools? I must have had a pretty quizzical look on my face, because my guide said… “Let me show you.”

We walked over to one of the pit bosses. He was a 50+ year old man in a dark suit leaning against a podium, tapping his pen and generally looking bored off to space. My guide said, “Hi Fred, can you tell us what’s going on?” The pit boss proceeded to instantly rattle off how long each person had been sitting in his area, how much they had bet, how much they lost and won and what they were drinking. Based on his immediate and on-going tracking of the floor he and the management could make immediate decisions about deploying resources, serving more drinks, calling security or upgrading a high value gambler.

Every once and a while the pit boss would write down a few pieces of data that that were then later input into a data repository for trend analysis etc. 

I give this organization a lot of credit because they realized that in fact there was a trade-off benefit of not automating and mechanizing everything. They realized that there was a whole generation (in fact multiple generations) of people, who had honed the internal gut skills to rapidly analyze incoming data, processes it and do something with it. AND also provide a level of customer service that was unmatched. 

Finding that balance is essential. Just automating, warehousing, consolidating, outsourcing, clouding…or pick another buzz word……without an understand of why and understanding the cost and benefit, is just missing the point. There maybe a wealth of opportunity in the experience, the gut and the skills of people within your business that you might be unwittingly missing.</description>
		<content:encoded><![CDATA[<p>Tom -</p>
<p>Your posting reminds me of a “behind the scenes” tour of a major gambling casino that I had the pleasure of taking (…don’t ask why…that is a whole different posting). The executive giving the tour explained that at one time they considered automating the job of the pit bosses by creating an RFID-based system that tracked all the card, dice, chip and even drink movements on the gambling table. By the way..I learned that the pit bosses are the ones walking around the casino tracking and managing the floor. The casino did a pilot program and tried the computerized system out. In the end, they found that it couldn’t compare to the accuracy and speed of the pit bosses. </p>
<p>Why not??? Thinking like a geek…I was pondering the details. Was it a problem with the RFID chips, maybe the data transfer…maybe the issue was with the analytics tools? I must have had a pretty quizzical look on my face, because my guide said… “Let me show you.”</p>
<p>We walked over to one of the pit bosses. He was a 50+ year old man in a dark suit leaning against a podium, tapping his pen and generally looking bored off to space. My guide said, “Hi Fred, can you tell us what’s going on?” The pit boss proceeded to instantly rattle off how long each person had been sitting in his area, how much they had bet, how much they lost and won and what they were drinking. Based on his immediate and on-going tracking of the floor he and the management could make immediate decisions about deploying resources, serving more drinks, calling security or upgrading a high value gambler.</p>
<p>Every once and a while the pit boss would write down a few pieces of data that that were then later input into a data repository for trend analysis etc. </p>
<p>I give this organization a lot of credit because they realized that in fact there was a trade-off benefit of not automating and mechanizing everything. They realized that there was a whole generation (in fact multiple generations) of people, who had honed the internal gut skills to rapidly analyze incoming data, processes it and do something with it. AND also provide a level of customer service that was unmatched. </p>
<p>Finding that balance is essential. Just automating, warehousing, consolidating, outsourcing, clouding…or pick another buzz word……without an understand of why and understanding the cost and benefit, is just missing the point. There maybe a wealth of opportunity in the experience, the gut and the skills of people within your business that you might be unwittingly missing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Jones</title>
		<link>http://blogs.gartner.com/tom_austin/2009/06/11/decision-delusions/comment-page-1/#comment-94</link>
		<dc:creator>Nick Jones</dc:creator>
		<pubDate>Thu, 11 Jun 2009 16:22:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/tom_austin/2009/06/11/decision-delusions/#comment-94</guid>
		<description>Tom, there are many ways of thinking about the issue you raise. One is that business bets that rely on a single specific future vision are dangerous. Any vision of the future can be derailed by unforeseen events. The future is defined by the fact it&#039;s unknown and largely unknowable. 

So one strategy is to bet on capabilities not products. This is, I suspect, what the folks at Google do, more or less consciously. Some days someone at Google wakes up and thinks: wouldn&#039;t it be cool if..... and something like Wave, Maps or Earth is born. When they start investing in it, they don&#039;t know exactly how it will work or even what features it will have. But they tend to create extensible and flexible capabilities that can be used in lots of different ways, and then let the community of developers find out what they&#039;re for. So in many ways Google doesn&#039;t care which future emerges, their technology will still be relevant. 

A classic product development process based on detailed market forecasts and intelligence can pay off big time if you&#039;re right, but tends to be fragile if the future doesn&#039;t turn out the way you expect. Although it&#039;s heresy to say so, as a Gartner analyst I am often worried when people ask me for detailed market forecasts, because it can sometimes indicate someone with too narrow a view of the future.

Nick</description>
		<content:encoded><![CDATA[<p>Tom, there are many ways of thinking about the issue you raise. One is that business bets that rely on a single specific future vision are dangerous. Any vision of the future can be derailed by unforeseen events. The future is defined by the fact it&#8217;s unknown and largely unknowable. </p>
<p>So one strategy is to bet on capabilities not products. This is, I suspect, what the folks at Google do, more or less consciously. Some days someone at Google wakes up and thinks: wouldn&#8217;t it be cool if&#8230;.. and something like Wave, Maps or Earth is born. When they start investing in it, they don&#8217;t know exactly how it will work or even what features it will have. But they tend to create extensible and flexible capabilities that can be used in lots of different ways, and then let the community of developers find out what they&#8217;re for. So in many ways Google doesn&#8217;t care which future emerges, their technology will still be relevant. </p>
<p>A classic product development process based on detailed market forecasts and intelligence can pay off big time if you&#8217;re right, but tends to be fragile if the future doesn&#8217;t turn out the way you expect. Although it&#8217;s heresy to say so, as a Gartner analyst I am often worried when people ask me for detailed market forecasts, because it can sometimes indicate someone with too narrow a view of the future.</p>
<p>Nick</p>
]]></content:encoded>
	</item>
</channel>
</rss>

