<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: “R” Does Not Have to be a Dreaded Letter</title>
	<link>http://www.esourcingforum.com/archives/2008/03/26/%e2%80%9cr%e2%80%9d-does-not-have-to-be-a-dreaded-letter/</link>
	<description>The source of information and best practices in strategic sourcing.</description>
	<pubDate>Fri, 04 Jul 2008 08:08:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Eric Strovink</title>
		<link>http://www.esourcingforum.com/archives/2008/03/26/%e2%80%9cr%e2%80%9d-does-not-have-to-be-a-dreaded-letter/#comment-11192</link>
		<dc:creator>Eric Strovink</dc:creator>
		<pubDate>Wed, 26 Mar 2008 14:59:39 +0000</pubDate>
		<guid>http://www.esourcingforum.com/archives/2008/03/26/%e2%80%9cr%e2%80%9d-does-not-have-to-be-a-dreaded-letter/#comment-11192</guid>
		<description>If "re-sourcing" includes "aggressive compliance review of existing contracts" -- which can return not only a promise of future savings, but a refund check (or credits) as well --  then I'm on board. 

One should always think before pulling the sourcing trigger.  Your current contracts may be fine -- the problem may be compliance.  Spending a lot of time and effort setting up new contracts that nobody pays attention to won't help.</description>
		<content:encoded><![CDATA[<p>If &#8220;re-sourcing&#8221; includes &#8220;aggressive compliance review of existing contracts&#8221; &#8212; which can return not only a promise of future savings, but a refund check (or credits) as well &#8212;  then I&#8217;m on board. </p>
<p>One should always think before pulling the sourcing trigger.  Your current contracts may be fine &#8212; the problem may be compliance.  Spending a lot of time and effort setting up new contracts that nobody pays attention to won&#8217;t help.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
