<?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: How to Find the &#8216;Trigger Events&#8217; For What You Sell</title>
	<atom:link href="http://www.shiftselling.com/2008/02/19/how-to-find-the-trigger-events-for-what-you-sell/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shiftselling.com/2008/02/19/how-to-find-the-trigger-events-for-what-you-sell/</link>
	<description>Shifting the fundamental economics of selling by leveraging 'Trigger Events'</description>
	<pubDate>Mon, 08 Sep 2008 12:45:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Skip Anderson</title>
		<link>http://www.shiftselling.com/2008/02/19/how-to-find-the-trigger-events-for-what-you-sell/#comment-164</link>
		<dc:creator>Skip Anderson</dc:creator>
		<pubDate>Thu, 22 May 2008 11:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiftselling.com/2008/02/19/how-to-find-the-trigger-events-for-what-you-sell/#comment-164</guid>
		<description>Craig, I really like your "Won Sales Analysis" tool. This type of analysis can really help bring clarity to your strengths in your market. 

When I was a sales manager, I would often ask my salespeople why this or that client purchased. Often, their answer would be nebulous or unclear. In coaching sessions, I would press this issue so that we could identify the exact reason why customers bought.</description>
		<content:encoded><![CDATA[<p>Craig, I really like your &#8220;Won Sales Analysis&#8221; tool. This type of analysis can really help bring clarity to your strengths in your market. </p>
<p>When I was a sales manager, I would often ask my salespeople why this or that client purchased. Often, their answer would be nebulous or unclear. In coaching sessions, I would press this issue so that we could identify the exact reason why customers bought.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
