<?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/"
		>
<channel>
	<title>Comments on: Rainmaking Problem #22:  Team Selling for the First Time</title>
	<atom:link href="http://www.hardingco.com/blog/2009/09/16/rainmaking-problem-22-team-selling-for-the-first-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hardingco.com/blog/2009/09/16/rainmaking-problem-22-team-selling-for-the-first-time/</link>
	<description>Mimi Spangler&#039;s Blog on Rainmaking and Business Development</description>
	<lastBuildDate>Sat, 17 Dec 2011 22:48:43 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Ford Harding</title>
		<link>http://www.hardingco.com/blog/2009/09/16/rainmaking-problem-22-team-selling-for-the-first-time/comment-page-1/#comment-36818</link>
		<dc:creator>Ford Harding</dc:creator>
		<pubDate>Mon, 21 Sep 2009 12:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=434#comment-36818</guid>
		<description>Ian:

These are good suggestions.  You also make me cringe when I think back to some of my own earlier behaviors.

Ford Harding</description>
		<content:encoded><![CDATA[<p>Ian:</p>
<p>These are good suggestions.  You also make me cringe when I think back to some of my own earlier behaviors.</p>
<p>Ford Harding</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Brodie</title>
		<link>http://www.hardingco.com/blog/2009/09/16/rainmaking-problem-22-team-selling-for-the-first-time/comment-page-1/#comment-36817</link>
		<dc:creator>Ian Brodie</dc:creator>
		<pubDate>Sun, 20 Sep 2009 15:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=434#comment-36817</guid>
		<description>I&#039;ve found that Pete&#039;s Point #3 - that you now have 2 people who want to say something - to be particularly challenging. 

It&#039;s often really difficult for professionals who derive a lot of their feelings of worth from &quot;being an expert&quot; to just keep quiet at times.

I know from painful experience from early(ish) in my career, where I&#039;ve been in the relationship role and introduced an expert to a client for a sales meeting.  Because I actually knew a lot about the area being covered, I trod on the toes of the expert I brought in. I was too concerned with wanting the client to be dazzled by my brilliance. So I took airtime from both the other consultant, and the client. It took me a while to learn to swallow my ego.

The same happens in more formal presentations where often 3 or 4 people will attempt to &quot;build on&quot; each others&#039; answers, thinking their additions will add value &amp; credibility - where in fact they just add complexity and confusion. As John said, you need to agree roles for who coordinates answers. And in my experience, a &quot;1 answer only&quot; rule is useful too. Even if everyone feels the original answerer didn&#039;t do a perfect job, additions very rarely improve the client&#039;s perception of the answer.

In these more formal presentations, I also advise people to try to &quot;pair up&quot; with their equivalents from the client organisation: senior exec with senior exec, project lead with project lead, etc. This again needs to be planned up-front.

Ian</description>
		<content:encoded><![CDATA[<p>I&#8217;ve found that Pete&#8217;s Point #3 &#8211; that you now have 2 people who want to say something &#8211; to be particularly challenging. </p>
<p>It&#8217;s often really difficult for professionals who derive a lot of their feelings of worth from &#8220;being an expert&#8221; to just keep quiet at times.</p>
<p>I know from painful experience from early(ish) in my career, where I&#8217;ve been in the relationship role and introduced an expert to a client for a sales meeting.  Because I actually knew a lot about the area being covered, I trod on the toes of the expert I brought in. I was too concerned with wanting the client to be dazzled by my brilliance. So I took airtime from both the other consultant, and the client. It took me a while to learn to swallow my ego.</p>
<p>The same happens in more formal presentations where often 3 or 4 people will attempt to &#8220;build on&#8221; each others&#8217; answers, thinking their additions will add value &amp; credibility &#8211; where in fact they just add complexity and confusion. As John said, you need to agree roles for who coordinates answers. And in my experience, a &#8220;1 answer only&#8221; rule is useful too. Even if everyone feels the original answerer didn&#8217;t do a perfect job, additions very rarely improve the client&#8217;s perception of the answer.</p>
<p>In these more formal presentations, I also advise people to try to &#8220;pair up&#8221; with their equivalents from the client organisation: senior exec with senior exec, project lead with project lead, etc. This again needs to be planned up-front.</p>
<p>Ian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ford Harding</title>
		<link>http://www.hardingco.com/blog/2009/09/16/rainmaking-problem-22-team-selling-for-the-first-time/comment-page-1/#comment-36816</link>
		<dc:creator>Ford Harding</dc:creator>
		<pubDate>Sat, 19 Sep 2009 14:24:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=434#comment-36816</guid>
		<description>Pete and John:

Thanks for these thoughtful comments.

Ford Harding</description>
		<content:encoded><![CDATA[<p>Pete and John:</p>
<p>Thanks for these thoughtful comments.</p>
<p>Ford Harding</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Warshaw</title>
		<link>http://www.hardingco.com/blog/2009/09/16/rainmaking-problem-22-team-selling-for-the-first-time/comment-page-1/#comment-36815</link>
		<dc:creator>Pete Warshaw</dc:creator>
		<pubDate>Fri, 18 Sep 2009 14:59:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=434#comment-36815</guid>
		<description>(1) I agree that preparation for the call is a must, but it&#039;s important to back up to the goals for the call.  For example, if one peer has the contact and the other is being set up to lead the work, it&#039;s very important that that second person play a major role in the discussion.  (2) In addition, following your advice, Ford, it&#039;s very helpful that the second person play the role of &quot;auditor&quot;, listening and watching for any disconnects and interjecting a question to get things back on track.  (3) The biggest challenge in team selling is that you now have two people who often want to say something when the goal is to have the prospect do the talking.  (4) Processing the call immediately afterward is a must, with the focus on the prospect&#039;s responses vs. points scored by the sellers.
Pete</description>
		<content:encoded><![CDATA[<p>(1) I agree that preparation for the call is a must, but it&#8217;s important to back up to the goals for the call.  For example, if one peer has the contact and the other is being set up to lead the work, it&#8217;s very important that that second person play a major role in the discussion.  (2) In addition, following your advice, Ford, it&#8217;s very helpful that the second person play the role of &#8220;auditor&#8221;, listening and watching for any disconnects and interjecting a question to get things back on track.  (3) The biggest challenge in team selling is that you now have two people who often want to say something when the goal is to have the prospect do the talking.  (4) Processing the call immediately afterward is a must, with the focus on the prospect&#8217;s responses vs. points scored by the sellers.<br />
Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John M. Walker</title>
		<link>http://www.hardingco.com/blog/2009/09/16/rainmaking-problem-22-team-selling-for-the-first-time/comment-page-1/#comment-36814</link>
		<dc:creator>John M. Walker</dc:creator>
		<pubDate>Wed, 16 Sep 2009 14:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/?p=434#comment-36814</guid>
		<description>Team selling can be highly effective, but it must be coordinated. In my experience, nothing will kill a potential sale or a presentation faster in team selling than an uncoordinated presentation. The prospect becomes confused and loses interest as well as confidence in the firm. 

The team must select a single person to make and to control the presentation. The others on the team can answer technical questions in their area only if the presenter passes the question to them. Once they have answered, the control and focus returns to the presenter. 

Before the meeting, the team must consider and agree on the objectives of the meeting and align their expectations. 

After the meeting, only the team member who presented should send the follow up communication with the prospect. To allow other team members to do so will create confusion. Confusion kills opportunity. 

John</description>
		<content:encoded><![CDATA[<p>Team selling can be highly effective, but it must be coordinated. In my experience, nothing will kill a potential sale or a presentation faster in team selling than an uncoordinated presentation. The prospect becomes confused and loses interest as well as confidence in the firm. </p>
<p>The team must select a single person to make and to control the presentation. The others on the team can answer technical questions in their area only if the presenter passes the question to them. Once they have answered, the control and focus returns to the presenter. </p>
<p>Before the meeting, the team must consider and agree on the objectives of the meeting and align their expectations. </p>
<p>After the meeting, only the team member who presented should send the follow up communication with the prospect. To allow other team members to do so will create confusion. Confusion kills opportunity. </p>
<p>John</p>
]]></content:encoded>
	</item>
</channel>
</rss>

