 




<?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>Oh I See! Getting CIOs to view their jobs from a different angle &#187; One-stop-shop</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/Oh-I-See/tag/one-stop-shop/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/Oh-I-See</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 17:40:37 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>One Stop Shop?</title>
		<link>http://itknowledgeexchange.techtarget.com/Oh-I-See/one-stop-shop/</link>
		<comments>http://itknowledgeexchange.techtarget.com/Oh-I-See/one-stop-shop/#comments</comments>
		<pubDate>Tue, 22 May 2012 05:01:50 +0000</pubDate>
		<dc:creator>Arun Gupta</dc:creator>
				<category><![CDATA[CIO]]></category>
		<category><![CDATA[One-stop-shop]]></category>
		<category><![CDATA[outsourcing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/Oh-I-See/?p=517</guid>
		<description><![CDATA[The common interpretation of One Stop Shop is to take the customer to his destination with no stops. But that rarely happens in outsourcing engagements.]]></description>
				<content:encoded><![CDATA[<p>The IT industry has many types of vendors; some focusing on niche solutions, some specializing in specific technologies or domains, some who offer a menu of products / services ranging from infrastructure to applications, and then there are large diversified companies who do everything from consulting to implementation of technology solutions or packages backed by support services in a local, offshore or multi-location model. The big guys manage all kinds of requirements and bring to the discussion table a comprehensive <a href="http://itknowledgeexchange.techtarget.com/Oh-I-See/outsourcing-travails/" target="_blank">long-term engagement model</a>.</p>
<p><a href="http://searchcio.techtarget.in/news/1517407/Seven-outsourcing-criteria-for-service-provider-evaluation" target="_blank">Different vendors set different expectations</a> on what they can deliver; the niche providers do not promise a breadth of services, they stay focused on their expertise. The big ones claim to have expertise across the legacy to contemporary and cutting edge; they have industry practices and business consultants who profess incremental to transformational change capabilities. You name it we can do it; even if you cannot put a name to it, we will find a way to do it!</p>
<p><strong>Complexities in governance</strong></p>
<p>The large one-stop-shop engagements typically begin with setting of scope and expectations on delivery, timelines, and quality of service, rewards, penalties, force majeure, arbitration, cost, escalations and a lot more. The larger the scope, or the longer the time period of the contract, the governance becomes complex. We know that <a href="http://searchcio.techtarget.in/tip/Optimize-your-IT-outsourcing-strategy-with-this-guide" target="_blank">Total or Strategic outsourcing</a> can cover everything; in recent times though the number of such deals has been dwindling.</p>
<p>So it was an interesting debate when a few CEOs on a panel berated the one-stop-shop companies giving it a new twist. Consider you wanting to reach a far-far away destination and the only option is to go by bus. Every bus gets you there, some are slower than others, some offer many comforts through the journey; the cheaper ones just get you there. Depending on what you can afford, there are many options to choose from. Caveat is once you have bought a ticket, a change is difficult and painful.</p>
<p>When someone advertises &#8216;one-stop-shop&#8217;, the conventional understanding is that I get from where I am to the final destination with no stops with the advertised and agreed comfort. Reality as we know is not always as advertised. A CEO remarked on his journey with one of the global biggies; he signed up for a long journey wanting to focus on his business. Very quickly he was on the discussion table with the bus driver, conductor and the entire fleet management company.</p>
<p>Why is my journey <a href="http://itknowledgeexchange.techtarget.com/Oh-I-See/omg-outsource-manage-groan/" target="_blank">so excruciatingly slow?</a> Why is the transformation promised not happening? When will I see any impact to my employees, stakeholders, customers, or for that matter any efficiency to business operations? Whatever happened to the pre-sales promises made by the various function heads of your company on various domains and technologies? Pat came the answer, “we are a one-stop-shop company; we go one stop at a time. This is what we promised; we did have a driver change and a breakdown; that is part of the contract. We meet defined service levels.”</p>
<p><strong>Devil lies in the detail</strong></p>
<p>Both are right in their frame of reference; so where is the problem? I believe that any such engagement should have common definition of reference points with clear understanding of step-by-step process, impact and governance. Otherwise the semantics of the one-stop-shop can be painful for everyone involved, the deliverer and the recipient. The bus is still moving but not in the way that makes <a href="http://searchcio.techtarget.in/news/2240022834/Free-outsourcing-management-templates-for-Indian-organizations" target="_blank">the journey a pleasure</a>. CIOs will be at the receiving end if there are such gaps.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/Oh-I-See/one-stop-shop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
