<?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: What Is a Capability and What Does It Matter?</title>
	<atom:link href="http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/feed/" rel="self" type="application/rss+xml" />
	<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/</link>
	<description>Economics of organizations, strategy, entrepreneurship, innovation, and more</description>
	<pubDate>Thu, 24 Jul 2008 03:30:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: David Hoopes</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54114</link>
		<dc:creator>David Hoopes</dc:creator>
		<pubDate>Thu, 04 Oct 2007 02:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54114</guid>
		<description>Steve, you are just so darn helpful.</description>
		<content:encoded><![CDATA[<p>Steve, you are just so darn helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: spostrel</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54110</link>
		<dc:creator>spostrel</dc:creator>
		<pubDate>Thu, 04 Oct 2007 01:31:20 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54110</guid>
		<description>It's tempting to just coin a new term so people don't think you're trying to be imperialistic.  Maybe call it a "bezinka" or a "gloobersnick" instead of a capability. Then you can talk about the "bezinka theory of X" or the "X hypothesis about gloobersnicks" and nobody can carp.</description>
		<content:encoded><![CDATA[<p>It&#8217;s tempting to just coin a new term so people don&#8217;t think you&#8217;re trying to be imperialistic.  Maybe call it a &#8220;bezinka&#8221; or a &#8220;gloobersnick&#8221; instead of a capability. Then you can talk about the &#8220;bezinka theory of X&#8221; or the &#8220;X hypothesis about gloobersnicks&#8221; and nobody can carp.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hoopes</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54079</link>
		<dc:creator>David Hoopes</dc:creator>
		<pubDate>Wed, 03 Oct 2007 18:07:59 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54079</guid>
		<description>REW:
My point was that I did not want to talk on and on about how many ways a capability can be defined.  As you point out, the definition is only as useful as the work it allows you to do.  I would prefer the field to converge on some definitions so that discussion can move on to substantive issues.

In: That I see my work building on Nelson and Winter (among)many others) doesn't mean I have to dismiss every other approach to capabilities.  So, I agree with you.

I think one of the patterns that the RBV gets stuck in is continually re-slicing and re-dicing how to define a resource.  I think this "discussion" becomes over-wrought when the definitions are so general and all-encompassing as to be vague.  

A lot of this "discussion" is verbal theory (since Nicolai doesn't like the term conceptual).  Without the discipline of an empirical specification or the clarity required in formal models many such "theories" end up being poorly specified.  Or, again, vague.

As implied by REW, the definition of construct is only as good as the understanding is leads to.  Steve and I like to think that our defining capabilities as "a probability density of outputs conditional on what is requested..." (Hoopes and Postrel ,2007) is important to both our empirical work and our theories of capability development.  Similarly, Tammy Madsen and I stick closer to Sid's 2000 SMJ defintion because it does make distinuishing a capability from its inputs and outputs pretty easy theoretically and empirically.  

And I don't use Sid's definition just because he is Sid.  It's because Sid is a very rigorous thinker.  He carefully builds on his own and others' previous work.  Whether everyone involved RBV debates knows it or not, his work has had a profound impact on how scholars think about capabilities and the myriad theories that use capabilities to explain things (firm and industry evolution, competitive heterogeneity, competitive advantage...)

Well that's enough said for me.</description>
		<content:encoded><![CDATA[<p>REW:<br />
My point was that I did not want to talk on and on about how many ways a capability can be defined.  As you point out, the definition is only as useful as the work it allows you to do.  I would prefer the field to converge on some definitions so that discussion can move on to substantive issues.</p>
<p>In: That I see my work building on Nelson and Winter (among)many others) doesn&#8217;t mean I have to dismiss every other approach to capabilities.  So, I agree with you.</p>
<p>I think one of the patterns that the RBV gets stuck in is continually re-slicing and re-dicing how to define a resource.  I think this &#8220;discussion&#8221; becomes over-wrought when the definitions are so general and all-encompassing as to be vague.  </p>
<p>A lot of this &#8220;discussion&#8221; is verbal theory (since Nicolai doesn&#8217;t like the term conceptual).  Without the discipline of an empirical specification or the clarity required in formal models many such &#8220;theories&#8221; end up being poorly specified.  Or, again, vague.</p>
<p>As implied by REW, the definition of construct is only as good as the understanding is leads to.  Steve and I like to think that our defining capabilities as &#8220;a probability density of outputs conditional on what is requested&#8230;&#8221; (Hoopes and Postrel ,2007) is important to both our empirical work and our theories of capability development.  Similarly, Tammy Madsen and I stick closer to Sid&#8217;s 2000 SMJ defintion because it does make distinuishing a capability from its inputs and outputs pretty easy theoretically and empirically.  </p>
<p>And I don&#8217;t use Sid&#8217;s definition just because he is Sid.  It&#8217;s because Sid is a very rigorous thinker.  He carefully builds on his own and others&#8217; previous work.  Whether everyone involved RBV debates knows it or not, his work has had a profound impact on how scholars think about capabilities and the myriad theories that use capabilities to explain things (firm and industry evolution, competitive heterogeneity, competitive advantage&#8230;)</p>
<p>Well that&#8217;s enough said for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hoopes</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54077</link>
		<dc:creator>David Hoopes</dc:creator>
		<pubDate>Wed, 03 Oct 2007 17:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54077</guid>
		<description>Paolo:
“I do not think that a theory of the firm or of organization can go very far by using such concepts which are often catch-all words.”

Well said.</description>
		<content:encoded><![CDATA[<p>Paolo:<br />
“I do not think that a theory of the firm or of organization can go very far by using such concepts which are often catch-all words.”</p>
<p>Well said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hoopes</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54076</link>
		<dc:creator>David Hoopes</dc:creator>
		<pubDate>Wed, 03 Oct 2007 17:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54076</guid>
		<description>Warren: Thanks.
Paolo:
          "Besides the concept of capabilities belongs to the realm of   potentialities"

Exactly!

         "I do not think that a theory of the firm or of organization can go very far by using such concepts which are often catch-all words."</description>
		<content:encoded><![CDATA[<p>Warren: Thanks.<br />
Paolo:<br />
          &#8220;Besides the concept of capabilities belongs to the realm of   potentialities&#8221;</p>
<p>Exactly!</p>
<p>         &#8220;I do not think that a theory of the firm or of organization can go very far by using such concepts which are often catch-all words.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ln</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54070</link>
		<dc:creator>ln</dc:creator>
		<pubDate>Wed, 03 Oct 2007 16:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54070</guid>
		<description>I understand the previous speaker's argument, yet understand that the beginning of this thread not to be about introducing a new idiosyncratic definition of capability, but rather about getting acceptance for basing one specific paper solely on Sidney Winter's definition. If one can just agree to this definition within the paper, one can move on to more workable codifications building on it, which perhaps is what the paper is about.

That I respect Sidney Winter's definition as relevant for building one or more papers on, should not be seen as discounting the contributions of numerous other great scholars, who have dealt with the definition issue.</description>
		<content:encoded><![CDATA[<p>I understand the previous speaker&#8217;s argument, yet understand that the beginning of this thread not to be about introducing a new idiosyncratic definition of capability, but rather about getting acceptance for basing one specific paper solely on Sidney Winter&#8217;s definition. If one can just agree to this definition within the paper, one can move on to more workable codifications building on it, which perhaps is what the paper is about.</p>
<p>That I respect Sidney Winter&#8217;s definition as relevant for building one or more papers on, should not be seen as discounting the contributions of numerous other great scholars, who have dealt with the definition issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: REW</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54066</link>
		<dc:creator>REW</dc:creator>
		<pubDate>Wed, 03 Oct 2007 15:13:28 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54066</guid>
		<description>As my French confreres would say, "Toujours, le dialogue des sourds continue". I readily admit to stalking out of several paper sessions in recent years where all of the authors spent half of their allotted time defending their idiosyncratic definitions of resource/capability (including the tedious recitation on dynamic/static) and no time on how their paper leads to some useful codification of the constructs beyond the asserted "correct" definition.

I understand the utility of maintaining separate niches in the intellectual landscape, so as to maximize the number of papers that might be presented/published on capabilities. However, the audience may lose interest in such a solipsistic dialogue of the deaf.</description>
		<content:encoded><![CDATA[<p>As my French confreres would say, &#8220;Toujours, le dialogue des sourds continue&#8221;. I readily admit to stalking out of several paper sessions in recent years where all of the authors spent half of their allotted time defending their idiosyncratic definitions of resource/capability (including the tedious recitation on dynamic/static) and no time on how their paper leads to some useful codification of the constructs beyond the asserted &#8220;correct&#8221; definition.</p>
<p>I understand the utility of maintaining separate niches in the intellectual landscape, so as to maximize the number of papers that might be presented/published on capabilities. However, the audience may lose interest in such a solipsistic dialogue of the deaf.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paolo  MARITI</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54032</link>
		<dc:creator>Paolo  MARITI</dc:creator>
		<pubDate>Wed, 03 Oct 2007 10:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54032</guid>
		<description>To an individual a capability is the quality of being able to do something. The deployment of a capabilitiy may require the use of resources and for this reason - as Warren points out -  the two are different.
However if you look at capabilities from the perspective of a firm, the capabilities of its 
personnel  are resources to it. 
 One can of course give as many working definitions of both capabilitiy and resource.
 since both terms are intrinsecally dialectical.
But  research conclusions and results are then bounded by those definitions and cannot be generalized.
Besides  the concept of capabilities belongs to the realm of potentialities and that makes things even more "complex"..All in all , I do not think that a theory of the firm or of organization can go very far by using such concepts which are often catch-all words.</description>
		<content:encoded><![CDATA[<p>To an individual a capability is the quality of being able to do something. The deployment of a capabilitiy may require the use of resources and for this reason - as Warren points out -  the two are different.<br />
However if you look at capabilities from the perspective of a firm, the capabilities of its<br />
personnel  are resources to it.<br />
 One can of course give as many working definitions of both capabilitiy and resource.<br />
 since both terms are intrinsecally dialectical.<br />
But  research conclusions and results are then bounded by those definitions and cannot be generalized.<br />
Besides  the concept of capabilities belongs to the realm of potentialities and that makes things even more &#8220;complex&#8221;..All in all , I do not think that a theory of the firm or of organization can go very far by using such concepts which are often catch-all words.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Warren Miller</title>
		<link>http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54000</link>
		<dc:creator>Warren Miller</dc:creator>
		<pubDate>Wed, 03 Oct 2007 03:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://organizationsandmarkets.com/2007/10/02/what-is-a-capability-and-what-does-it-matter/#comment-54000</guid>
		<description>Hear, hear, David. Dead-on on all counts. Thank you, thank you, thank you. Resources and capabilities ARE different. Sid Winter's take on capabilities does differ from Selznick's. Definitions which include the kitchen sink are, in my view, worse than no definitions at all because kitchen-sink definitions have the potential to create a false luster of intellectual respectability. And Tammy Madsen is a terrific colleague and first-rate scholar!</description>
		<content:encoded><![CDATA[<p>Hear, hear, David. Dead-on on all counts. Thank you, thank you, thank you. Resources and capabilities ARE different. Sid Winter&#8217;s take on capabilities does differ from Selznick&#8217;s. Definitions which include the kitchen sink are, in my view, worse than no definitions at all because kitchen-sink definitions have the potential to create a false luster of intellectual respectability. And Tammy Madsen is a terrific colleague and first-rate scholar!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
