<?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: How not to use a Magic Quadrant</title>
	<atom:link href="http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Mon, 26 Dec 2011 04:43:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Lydia Leong</title>
		<link>http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/comment-page-1/#comment-4099</link>
		<dc:creator>Lydia Leong</dc:creator>
		<pubDate>Tue, 11 Aug 2009 16:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/#comment-4099</guid>
		<description>I think, looking at the MQ, that it doesn&#039;t just reflect size -- it also reflects the breadth of product portfolio and overall market presence. For instance, Rackspace and Terremark have been consistently highly placed for 5 years, even when both were small vendors.

But you&#039;re right, the MQ is not designed to show feature breakdowns. That&#039;s why I&#039;m building a critical capabilities note for cloud system infrastructure services -- because featureset is much more of a driver in cloud computing right now, whereas classically enterprise Web hosting hasn&#039;t had much genuine feature differentation, (the main differences in enterprise hosters have been service, sometimes driven by back-end technology but also sometimes driven by just raw human attention).

I feel pretty strongly that Gartner clients doing vendor selection should do an analyst inquiry call rather than just relying on the written research. There&#039;s a ton of detail and color that simply doesn&#039;t fit well into the bullet-point format of the MQ, not to mention the usefulness of custom RFP / pricing / contract review.</description>
		<content:encoded><![CDATA[<p>I think, looking at the MQ, that it doesn&#8217;t just reflect size &#8212; it also reflects the breadth of product portfolio and overall market presence. For instance, Rackspace and Terremark have been consistently highly placed for 5 years, even when both were small vendors.</p>
<p>But you&#8217;re right, the MQ is not designed to show feature breakdowns. That&#8217;s why I&#8217;m building a critical capabilities note for cloud system infrastructure services &#8212; because featureset is much more of a driver in cloud computing right now, whereas classically enterprise Web hosting hasn&#8217;t had much genuine feature differentation, (the main differences in enterprise hosters have been service, sometimes driven by back-end technology but also sometimes driven by just raw human attention).</p>
<p>I feel pretty strongly that Gartner clients doing vendor selection should do an analyst inquiry call rather than just relying on the written research. There&#8217;s a ton of detail and color that simply doesn&#8217;t fit well into the bullet-point format of the MQ, not to mention the usefulness of custom RFP / pricing / contract review.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garth Knudson</title>
		<link>http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/comment-page-1/#comment-4089</link>
		<dc:creator>Garth Knudson</dc:creator>
		<pubDate>Mon, 10 Aug 2009 20:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/#comment-4089</guid>
		<description>Lydia, thanks for the honesty. Gartner is good at distilling information into a bullet and a blurb. What I wish Gartner would do is create an actual capabilities matrix based on the MQ criteria. You probably have the beginnings of such a list, but becuase you don&#039;t deep dive into technology as far as I have seen you do not capture key details that would help clients select vendors based on capablities not size.</description>
		<content:encoded><![CDATA[<p>Lydia, thanks for the honesty. Gartner is good at distilling information into a bullet and a blurb. What I wish Gartner would do is create an actual capabilities matrix based on the MQ criteria. You probably have the beginnings of such a list, but becuase you don&#8217;t deep dive into technology as far as I have seen you do not capture key details that would help clients select vendors based on capablities not size.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Misunderstanding Magic Quadrants, MarketScopes, and More &#171; SageCircle Blog</title>
		<link>http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/comment-page-1/#comment-3052</link>
		<dc:creator>Misunderstanding Magic Quadrants, MarketScopes, and More &#171; SageCircle Blog</dc:creator>
		<pubDate>Sat, 27 Jun 2009 14:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/lydia_leong/2009/06/25/how-not-to-use-a-magic-quadrant/#comment-3052</guid>
		<description>[...] a week after Jim wrote his blog post, Gartner analyst Lydia Leong came out with her own post on How not to use a Magic Quadrant. Lydia’s post also focuses on educating research consumers about the way to use the MQ. Lydia [...]</description>
		<content:encoded><![CDATA[<p>[...] a week after Jim wrote his blog post, Gartner analyst Lydia Leong came out with her own post on How not to use a Magic Quadrant. Lydia’s post also focuses on educating research consumers about the way to use the MQ. Lydia [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

