<?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: 7 Steps to Prepare an Engineer for a Sales Call</title>
	<atom:link href="http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/feed/" rel="self" type="application/rss+xml" />
	<link>http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=7-steps-to-prepare-an-engineer-for-a-sales-call</link>
	<description>Greg Strosaker on leadership, marketing, strategy, productivity, parenting autism, and running</description>
	<lastBuildDate>Mon, 16 Aug 2010 20:39:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Greg Strosaker</title>
		<link>http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/comment-page-1/#comment-142</link>
		<dc:creator>Greg Strosaker</dc:creator>
		<pubDate>Tue, 02 Feb 2010 16:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://gregstrosaker.com/?p=150#comment-142</guid>
		<description>Thanks for your comment Claudine.  Striking the right balance between answering and asking continues to be a challenge for us; one other issue we are struggling through with our application engineers is that they often simply respond to a customers question without understanding what is driving the question.  For example, if they are asked for a quote, they view delivering the quote as the goal, not necessarily getting the sale.  We are working with them to try and understand the customer&#039;s needs better, to see if maybe what we are quoting is not the right product after all.  On the flip side though, we have a few engineers who provide way too much information.  We are working hard to coach both ends of the spectrum on how to strike the right balance.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment Claudine.  Striking the right balance between answering and asking continues to be a challenge for us; one other issue we are struggling through with our application engineers is that they often simply respond to a customers question without understanding what is driving the question.  For example, if they are asked for a quote, they view delivering the quote as the goal, not necessarily getting the sale.  We are working with them to try and understand the customer&#39;s needs better, to see if maybe what we are quoting is not the right product after all.  On the flip side though, we have a few engineers who provide way too much information.  We are working hard to coach both ends of the spectrum on how to strike the right balance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Strosaker</title>
		<link>http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/comment-page-1/#comment-51</link>
		<dc:creator>Greg Strosaker</dc:creator>
		<pubDate>Tue, 02 Feb 2010 11:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://gregstrosaker.com/?p=150#comment-51</guid>
		<description>Thanks for your comment Claudine.  Striking the right balance between answering and asking continues to be a challenge for us; one other issue we are struggling through with our application engineers is that they often simply respond to a customers question without understanding what is driving the question.  For example, if they are asked for a quote, they view delivering the quote as the goal, not necessarily getting the sale.  We are working with them to try and understand the customer&#039;s needs better, to see if maybe what we are quoting is not the right product after all.  On the flip side though, we have a few engineers who provide way too much information.  We are working hard to coach both ends of the spectrum on how to strike the right balance.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment Claudine.  Striking the right balance between answering and asking continues to be a challenge for us; one other issue we are struggling through with our application engineers is that they often simply respond to a customers question without understanding what is driving the question.  For example, if they are asked for a quote, they view delivering the quote as the goal, not necessarily getting the sale.  We are working with them to try and understand the customer&#39;s needs better, to see if maybe what we are quoting is not the right product after all.  On the flip side though, we have a few engineers who provide way too much information.  We are working hard to coach both ends of the spectrum on how to strike the right balance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/comment-page-1/#comment-50</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Tue, 02 Feb 2010 07:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://gregstrosaker.com/?p=150#comment-50</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by GAStroz: New blog post: 7 Steps to Prepare an Engineer for a Sales Call http://bit.ly/drMzwG...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by GAStroz: New blog post: 7 Steps to Prepare an Engineer for a Sales Call <a href="http://bit.ly/drMzwG.." rel="nofollow">http://bit.ly/drMzwG..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudine Motto</title>
		<link>http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/comment-page-1/#comment-49</link>
		<dc:creator>Claudine Motto</dc:creator>
		<pubDate>Mon, 01 Feb 2010 23:06:01 +0000</pubDate>
		<guid isPermaLink="false">http://gregstrosaker.com/?p=150#comment-49</guid>
		<description>Great insights, Greg.  Your post reminds that everything, even asking questions, is best done in moderation.  Too little questions, and we&#039;re doing too much talking, and not enough listening.  Too many questions, we overwhelm the client and perhaps in some instances even make him/her feel &quot;interrogated&quot; or judged for whatever issues they may be experiencing.  This &quot;moderation&quot; applies to the follow-through as well - the answers to the customer&#039;s questions should have just enough detail to answer the question the question appropriately, with an invitation to ask for more if wanted/needed.</description>
		<content:encoded><![CDATA[<p>Great insights, Greg.  Your post reminds that everything, even asking questions, is best done in moderation.  Too little questions, and we&#39;re doing too much talking, and not enough listening.  Too many questions, we overwhelm the client and perhaps in some instances even make him/her feel &#8220;interrogated&#8221; or judged for whatever issues they may be experiencing.  This &#8220;moderation&#8221; applies to the follow-through as well &#8211; the answers to the customer&#39;s questions should have just enough detail to answer the question the question appropriately, with an invitation to ask for more if wanted/needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Strosaker</title>
		<link>http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/comment-page-1/#comment-48</link>
		<dc:creator>Greg Strosaker</dc:creator>
		<pubDate>Sat, 30 Jan 2010 12:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://gregstrosaker.com/?p=150#comment-48</guid>
		<description>Hi Jim, thanks for your comments and glad it worked this time.  I did overlook the idea that visiting a customer can (and should) be viewed as a reward for an engineer.  In fact, it should be emphasized up front that time in front of the customer is precious and should be relished.  As such, it makes appropriate preparations all that much more important, to maximize the value of this all-to-rare of an opportunity.&lt;br&gt;&lt;br&gt;Hope the year is off to a good start for you.</description>
		<content:encoded><![CDATA[<p>Hi Jim, thanks for your comments and glad it worked this time.  I did overlook the idea that visiting a customer can (and should) be viewed as a reward for an engineer.  In fact, it should be emphasized up front that time in front of the customer is precious and should be relished.  As such, it makes appropriate preparations all that much more important, to maximize the value of this all-to-rare of an opportunity.</p>
<p>Hope the year is off to a good start for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimmatorin</title>
		<link>http://gregstrosaker.com/2010/01/7-steps-to-prepare-an-engineer-for-a-sales-call/comment-page-1/#comment-47</link>
		<dc:creator>jimmatorin</dc:creator>
		<pubDate>Sat, 30 Jan 2010 12:14:32 +0000</pubDate>
		<guid isPermaLink="false">http://gregstrosaker.com/?p=150#comment-47</guid>
		<description>I enjoy your process including an engineer in a solutions based sale.  Too many companies fail to recognize how critical is it to include other members of the organization in their sales calls.  Rationale: 1.) Demonstrates commitment to the customer, 2.) Opens the eyes of the ancillary support team – being in food when I worked for a manufacturer I would involve R&amp;D, logistics or customer service so they would get a better understanding of what happens on the front line, thus understand how critical their component was in making our company successful; and C.) It was a fun break for the ancillary support team, a form of reward from their day to day routine, a way to motivate.</description>
		<content:encoded><![CDATA[<p>I enjoy your process including an engineer in a solutions based sale.  Too many companies fail to recognize how critical is it to include other members of the organization in their sales calls.  Rationale: 1.) Demonstrates commitment to the customer, 2.) Opens the eyes of the ancillary support team – being in food when I worked for a manufacturer I would involve R&#038;D, logistics or customer service so they would get a better understanding of what happens on the front line, thus understand how critical their component was in making our company successful; and C.) It was a fun break for the ancillary support team, a form of reward from their day to day routine, a way to motivate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
