<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: &#8220;Branding&#8221; Your IT Organization</title>
	<atom:link href="http://vaughanmerlyn.com/2010/02/22/branding-your-it-organization/feed/" rel="self" type="application/rss+xml" />
	<link>http://vaughanmerlyn.com/2010/02/22/branding-your-it-organization/</link>
	<description>Vaughan Merlyn on the Changing Role of the IT Organization</description>
	<lastBuildDate>Wed, 07 Dec 2011 19:30:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: itorganization2017</title>
		<link>http://vaughanmerlyn.com/2010/02/22/branding-your-it-organization/#comment-1216</link>
		<dc:creator><![CDATA[itorganization2017]]></dc:creator>
		<pubDate>Tue, 02 Mar 2010 22:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://vaughanmerlyn.com/?p=1968#comment-1216</guid>
		<description><![CDATA[Well, thank you very much!  It&#039;s comments such as yours that keep us blogging!  Happy commenting!]]></description>
		<content:encoded><![CDATA[<p>Well, thank you very much!  It&#8217;s comments such as yours that keep us blogging!  Happy commenting!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Watch Shrek</title>
		<link>http://vaughanmerlyn.com/2010/02/22/branding-your-it-organization/#comment-1215</link>
		<dc:creator><![CDATA[Watch Shrek]]></dc:creator>
		<pubDate>Tue, 02 Mar 2010 22:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://vaughanmerlyn.com/?p=1968#comment-1215</guid>
		<description><![CDATA[I hardly ever leave comments on posts, but your article encouraged me to applaud your blog. Thank you for the read, I&#039;ll make sure to bookmark this site and check in occasionally. Happy blogging.]]></description>
		<content:encoded><![CDATA[<p>I hardly ever leave comments on posts, but your article encouraged me to applaud your blog. Thank you for the read, I&#8217;ll make sure to bookmark this site and check in occasionally. Happy blogging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: itorganization2017</title>
		<link>http://vaughanmerlyn.com/2010/02/22/branding-your-it-organization/#comment-1209</link>
		<dc:creator><![CDATA[itorganization2017]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 15:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://vaughanmerlyn.com/?p=1968#comment-1209</guid>
		<description><![CDATA[Brad, thanks very much for this excellent and important reminder of the dangers inherent here.

I&#039;m actually very conflicted over this (my post) whole line of reasoning.  On the one hand, one can argue that the &#039;IT organization&#039; as such should be &#039;invisible&#039;.  When great infrastructure works, it should be like great background music - soothing and satisfying at a subconscious level but never intruding into the foreground.  On the other hand, one can argue that the distinction between &#039;business&#039; and &#039;IT&#039; should by now be moot - the two have become seamlessly integrated.

However, I think &#039;Intel Inside&#039; might be the most relevant branding exemplar in this space.  To most PC users, the internal processor is invisible - but Intel Inside reinforces an assurance of quality.  When we buy a PC branded this way we know that the primary label (HP, Dell, Lenovo, etc.) is where &#039;the buck stops&#039; so to speak, but we generally feel good about having a quality (Intel) component at the core.  This, I think, is the right balance between the processor&#039;s (Intel) branding and the PC manufacturer&#039;s (HP, et al) branding.

But your caution is well taken - any time we do something visible that is about &#039;the IT organization,&#039; we risk reinforcing the &quot;we/they&quot; dichotomy, which is always risky!

Thanks, as ever, for your most insightful comment!]]></description>
		<content:encoded><![CDATA[<p>Brad, thanks very much for this excellent and important reminder of the dangers inherent here.</p>
<p>I&#8217;m actually very conflicted over this (my post) whole line of reasoning.  On the one hand, one can argue that the &#8216;IT organization&#8217; as such should be &#8216;invisible&#8217;.  When great infrastructure works, it should be like great background music &#8211; soothing and satisfying at a subconscious level but never intruding into the foreground.  On the other hand, one can argue that the distinction between &#8216;business&#8217; and &#8216;IT&#8217; should by now be moot &#8211; the two have become seamlessly integrated.</p>
<p>However, I think &#8216;Intel Inside&#8217; might be the most relevant branding exemplar in this space.  To most PC users, the internal processor is invisible &#8211; but Intel Inside reinforces an assurance of quality.  When we buy a PC branded this way we know that the primary label (HP, Dell, Lenovo, etc.) is where &#8216;the buck stops&#8217; so to speak, but we generally feel good about having a quality (Intel) component at the core.  This, I think, is the right balance between the processor&#8217;s (Intel) branding and the PC manufacturer&#8217;s (HP, et al) branding.</p>
<p>But your caution is well taken &#8211; any time we do something visible that is about &#8216;the IT organization,&#8217; we risk reinforcing the &#8220;we/they&#8221; dichotomy, which is always risky!</p>
<p>Thanks, as ever, for your most insightful comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad King</title>
		<link>http://vaughanmerlyn.com/2010/02/22/branding-your-it-organization/#comment-1208</link>
		<dc:creator><![CDATA[Brad King]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 14:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://vaughanmerlyn.com/?p=1968#comment-1208</guid>
		<description><![CDATA[When &quot;branding&quot; an internal IT organization I would recommend an extra measure of attention to how the marketing campaign might be felt by the business.  
Vaughan, you may recall working with me to bring together several disparate IT organizations in order to enable some transformational enterprise level initiatives (ERP, CRM, Y2K, etc.)  We &quot;branded&quot; the new organization &quot;eIT&quot; (for &quot;Enterprise IT&quot;) and used that overarching theme to create a shared vision within the organization and throughout the enterprise.  
While it would be hard to argue with the theme&#039;s usefulness in aligning the IT team with the vision and the ultimate business outcomes, I was late to recognize that we had created a strong undercurrent of resentment amongst certain &quot;C-suite&quot; managers who felt that the real agenda was to create a separate IT &quot;empire&quot;.   While we recognized the potential for that we nonetheless created barriers to future collaboration with those leaders.  In retrospect, we fell into the trap of assuming that our branding &quot;message&quot; of partnership with the business was successful.  That was a significant error that should have been avoided - after all, some of those same managers had lost their absolute control of IT resources in the creation of an enterprise level IT organization.   
So, the CIO must balance branding of the internal IT organization with an oversized emphasis on making sure that IT behaviors clearly reflect an ethos of partnership with internal clients.  This hard work is made more difficult by the fact that the CIO must continually walk the razor&#039;s edge of partnership and governance.  That isn&#039;t easy.]]></description>
		<content:encoded><![CDATA[<p>When &#8220;branding&#8221; an internal IT organization I would recommend an extra measure of attention to how the marketing campaign might be felt by the business.<br />
Vaughan, you may recall working with me to bring together several disparate IT organizations in order to enable some transformational enterprise level initiatives (ERP, CRM, Y2K, etc.)  We &#8220;branded&#8221; the new organization &#8220;eIT&#8221; (for &#8220;Enterprise IT&#8221;) and used that overarching theme to create a shared vision within the organization and throughout the enterprise.<br />
While it would be hard to argue with the theme&#8217;s usefulness in aligning the IT team with the vision and the ultimate business outcomes, I was late to recognize that we had created a strong undercurrent of resentment amongst certain &#8220;C-suite&#8221; managers who felt that the real agenda was to create a separate IT &#8220;empire&#8221;.   While we recognized the potential for that we nonetheless created barriers to future collaboration with those leaders.  In retrospect, we fell into the trap of assuming that our branding &#8220;message&#8221; of partnership with the business was successful.  That was a significant error that should have been avoided &#8211; after all, some of those same managers had lost their absolute control of IT resources in the creation of an enterprise level IT organization.<br />
So, the CIO must balance branding of the internal IT organization with an oversized emphasis on making sure that IT behaviors clearly reflect an ethos of partnership with internal clients.  This hard work is made more difficult by the fact that the CIO must continually walk the razor&#8217;s edge of partnership and governance.  That isn&#8217;t easy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C K Venkatraman</title>
		<link>http://vaughanmerlyn.com/2010/02/22/branding-your-it-organization/#comment-1192</link>
		<dc:creator><![CDATA[C K Venkatraman]]></dc:creator>
		<pubDate>Thu, 25 Feb 2010 03:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://vaughanmerlyn.com/?p=1968#comment-1192</guid>
		<description><![CDATA[Interesting. I would say that this was true throughout history of Commercial computing.]]></description>
		<content:encoded><![CDATA[<p>Interesting. I would say that this was true throughout history of Commercial computing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

