<?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: Beyond CRM: Introducing NRM</title>
	<atom:link href="http://mercurygrove.com/blog/132/feed" rel="self" type="application/rss+xml" />
	<link>http://mercurygrove.com/blog/132</link>
	<description>Follow an application launch from the inside</description>
	<pubDate>Tue, 06 Jan 2009 10:17:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: RickDink</title>
		<link>http://mercurygrove.com/blog/132#comment-214</link>
		<dc:creator>RickDink</dc:creator>
		<pubDate>Thu, 14 Aug 2008 13:05:25 +0000</pubDate>
		<guid isPermaLink="false">http://mercurygrove.com/blog/?p=132#comment-214</guid>
		<description>Great concept. What I have seen with many other systems however is the usability of the system. There is always an ROI question by the users of the system. It needs to be easy and yet meaningful - much easier to say than to actually do. It also matters who in the organization is using the system. Very often it is the job of the sales folks to begin the process. From a sales perspective you don't want to spend a lot of time with a "prospects" information until it progresses. Who then is responsible for the information?</description>
		<content:encoded><![CDATA[<p>Great concept. What I have seen with many other systems however is the usability of the system. There is always an ROI question by the users of the system. It needs to be easy and yet meaningful - much easier to say than to actually do. It also matters who in the organization is using the system. Very often it is the job of the sales folks to begin the process. From a sales perspective you don&#8217;t want to spend a lot of time with a &#8220;prospects&#8221; information until it progresses. Who then is responsible for the information?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
