<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Creativity &#38; Analogy Blog &#187; inference</title>
	<atom:link href="http://www.structured-analogy-consultants.com/CreativityBlog/tag/inference/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.structured-analogy-consultants.com/CreativityBlog</link>
	<description>A Structured Analogy Consultants Weblog</description>
	<lastBuildDate>Sun, 11 Apr 2010 03:26:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A Baseball Analogy for Thinking About Innovation</title>
		<link>http://www.structured-analogy-consultants.com/CreativityBlog/2008/06/a-baseball-analogy-for-thinking-about-innovation/</link>
		<comments>http://www.structured-analogy-consultants.com/CreativityBlog/2008/06/a-baseball-analogy-for-thinking-about-innovation/#comments</comments>
		<pubDate>Sun, 15 Jun 2008 01:12:42 +0000</pubDate>
		<dc:creator>C.Sifonis</dc:creator>
				<category><![CDATA[Analogy]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[inference]]></category>
		<category><![CDATA[knowledge]]></category>
		<category><![CDATA[process]]></category>

		<guid isPermaLink="false">http://creativityblog.structured-analogy-consultants.com/2008/06/14/a-baseball-analogy-for-thinking-about-innovation/</guid>
		<description><![CDATA[This article by Scott Anthony at Harvard Business Weekly Publishing is a wonderful example of using analogy for communicating about innovation.  The analogy used in the article is between the Major League Baseball draft and the way a company manages innovation.
Because the analogy and its use for innovative thinking is presented so well, I [...]]]></description>
			<content:encoded><![CDATA[<p>This article by <a title="Bseball draft and innovation analogy" href="http://discussionleader.hbsp.com/anthony/2008/06/innovation_lessons_from_the_ba.html">Scott Anthony at Harvard Business Weekly Publishing</a> is a wonderful example of using analogy for communicating about innovation.  The analogy used in the article is between the <strong>Major League Baseball draft</strong> and the way a <strong>company manages innovation</strong>.</p>
<p>Because the analogy and its use for innovative thinking is presented so well, I am going to go all recursive on you and use the article as a showcase of the right ways of using analogy for innovation and for communicating about innovation.</p>
<p><span id="more-23"></span>The first step in any analogy is pointing out to the audience the <strong>relevant correspondences between the concepts</strong>:</p>
<blockquote><p>&#8220;<em>Baseball teams have to assemble the best talent possible, just like companies have to bet on the best innovation opportunities. A baseball team chooses between acquiring talent on the free agent market or drafting and building talent. A company chooses between acquisitions or organic growth.</em>&#8220;</p></blockquote>
<p>A good analogy focuses on <strong>deep structural correspondences</strong> between  concepts:</p>
<blockquote><p>&#8220;<em>Acquisitions are expensive, but perceived to be lower risk, because the talent (or idea) has proven itself demonstrably in the marketplace (for baseball, that means success on a major-league diamond). Organic growth is typically cheaper, but perceived to be risky because many times highly touted initiatives or prospects don’t pan out.</em>&#8220;</p></blockquote>
<p>What this means is that the author isn&#8217;t just drawing correspondences between the elements of the two concepts (e.g., &#8220;acquiring talent on the free agent market&#8221; = &#8220;acquisitions&#8221;). He is explaining how <strong>elements and the relationships between them</strong> in one concept correspond to elements and the relationships between them in the other concept.</p>
<p>These <strong>correspondences then lead to certain inferences</strong>. Inferences, that are important to the point the author is making about innovation:</p>
<blockquote><p>&#8220;<em>Just as a baseball team doesn’t have complete information about what a player’s true level of ability is on draft day, you don’t know the real potential of any one innovation project&#8230;. Good teams collect as much data as possible. They have sophisticated models to project how rough performance can project to the major league level.</em>&#8220;</p></blockquote>
<p>Leads to the inference that for companies:</p>
<blockquote><p>&#8220;<em>With a well-organized scouting team, you should gather multiple data points in preparation to “draft” innovation opportunities</em>.&#8221;</p></blockquote>
<p>By pointing out the correspondences between rich concepts such as the ones being used in the Baseball Analogy article, the audience is then able to make their own inferences u<strong>sing their own detailed knowledge of the concepts</strong> in the analogy:</p>
<blockquote><p>&#8220;<em>Of course, the market for companies is more liquid than the market for baseball players. We bet you if you ran the data the absolute best return on investment would be acquiring a hitter who has proven himself at a critical midpoint&#8230;.Ask yourself: What is the equivalent inflection point in our market?</em>&#8220;</p></blockquote>
<p>It is by working out the inferences resulting from correspondences such as these that innovation is made possible.  However, these inferences are<strong> not </strong>possible <strong>unless </strong>your <strong>audience possesses detailed knowledge of the concepts used in the analogy</strong>.  I, for one, know next to nothing about the Major League Baseball draft.  Consequently, I can follow the analogy made by the author and the points being made but would be absolutely unable to determine an &#8220;<em>equivalent inflection point</em>&#8221; at which I would be most likely to receive the &#8220;<em>absolute best return on investment.</em>&#8221;</p>
<p>Using analogy for communicating about innovation or for innovation itself requires knowledge of BOTH the concepts used in the analogy.  This knowledge can be provided by the person making the analogy or through personal experience, but acquired it must be for innovation to happen.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.structured-analogy-consultants.com/CreativityBlog/2008/06/a-baseball-analogy-for-thinking-about-innovation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bad analogy</title>
		<link>http://www.structured-analogy-consultants.com/CreativityBlog/2007/10/bad-analogy/</link>
		<comments>http://www.structured-analogy-consultants.com/CreativityBlog/2007/10/bad-analogy/#comments</comments>
		<pubDate>Tue, 30 Oct 2007 07:04:29 +0000</pubDate>
		<dc:creator>C.Sifonis</dc:creator>
				<category><![CDATA[Analogy]]></category>
		<category><![CDATA[Creativity]]></category>
		<category><![CDATA[analogical mapping]]></category>
		<category><![CDATA[bad analogy]]></category>
		<category><![CDATA[inference]]></category>
		<category><![CDATA[mapping]]></category>
		<category><![CDATA[source domain]]></category>
		<category><![CDATA[structure]]></category>
		<category><![CDATA[target domain]]></category>

		<guid isPermaLink="false">http://creativityblog.structured-analogy-consultants.com/2007/10/30/bad-analogy/</guid>
		<description><![CDATA[
So, the question is &#8220;Is Ratbert making another bad analogy?&#8221;  I believe the answer to this question depends on the mapping between the source and target domain.
Quick refresher: &#8220;Source domain&#8221; refers to the domain/knowledge from which the information is being &#8220;imported&#8221; so to speak.  In the case of the cartoon, the source domain [...]]]></description>
			<content:encoded><![CDATA[<p><a title="Bad analogy 1" href="http://www.structured-analogy-consultants.com/CreativityBlog/wp-content/uploads/2007/10/dilbert_analogy.gif"><img src="http://www.structured-analogy-consultants.com/CreativityBlog/wp-content/uploads/2007/10/dilbert_analogy.gif" alt="Bad analogy 1" /></a></p>
<p>So, the question is &#8220;Is Ratbert making another bad analogy?&#8221;  I believe the answer to this question depends on the mapping between the source and target domain.</p>
<blockquote><p>Quick refresher: &#8220;Source domain&#8221; refers to the domain/knowledge from which the information is being &#8220;imported&#8221; so to speak.  In the case of the cartoon, the source domain would be knowledge about the aging of good wine.</p>
<p>&#8220;Target domain&#8221; refers to the domain/knowledge to which the information is imported or the analogy is being drawn.  In the cartoon, knowledge of Ratbert is the target domain.</p>
<p>&#8220;Mapping&#8221; refers to the drawing of correspondences between the source and target domain. In the cartoon, this would involve establishing the ways in which Ratbert is like a fine wine and herein lies the determination of whether this is a good or a bad analogy.</p></blockquote>
<p>Ratbert is making the correct inference for this particular analogy &#8211; that Dogbert is saying that initially Ratbert&#8217;s wisdom may be lacking but over time will improve with age.</p>
<p>However, in verifying this inference, Dogbert reveals that there is more to the analogy that meets the eye.</p>
<blockquote><p>He is probably quite correct in making the statement that the analogy holds to the extent that Ratbert resembles a grape.  The crux of the matter is exactly HOW Ratbert resembles the grape.</p>
<p>If the resemblance is confined to the fact that Ratbert is  round, covered in a thin skin, and grape-colored, then the analogy falls apart. However, if it is because Ratbert shares some of the <strong>structural </strong>characteristics with grapes that result in fine wine (thick skin, late to ripen, possessing complex flavors that are only revealed with age), the analogy holds.  In other words, analogies succeed, not because of physical similarities between the source and the target domain but because of structural similarities.</p>
<p>For Ratbert&#8217;s wisdom to age to perfection with time, the wine analogy would suggest that it would help for him to have a &#8220;thick skin&#8221; (the better to withstand the ravages of the environment), be &#8220;slow to ripen&#8221; (play, not take life too seriously, take each stage of life as it comes and gain a range of diverse experiences in the process) and be a complex individual with many facets to his personality and many interests.</p></blockquote>
<p>The structural mapping between source and target domain is the critical component to the success of an analogy.  When the mapping only involves mapping the surface features between domains, you have a useless or even misguided analogy at worst and a trivial analogy at best.</p>
<p>Insight, inferences, problem solutions,and effective communication are all made possible by the  structured mapping of correspondences between the source and target domain.</p>
<blockquote><p>The greater the depth and complexity of the mapping &#8211; the better the result.  Not an easy task by any means but one well worth the effort.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.structured-analogy-consultants.com/CreativityBlog/2007/10/bad-analogy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
