<?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: How Much Detail Should You Give When Answering Questions?</title>
	<atom:link href="http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/</link>
	<description>Ford Harding's Blog on Rainmaking and Business Development</description>
	<pubDate>Thu, 18 Mar 2010 00:34:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ford Harding</title>
		<link>http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/comment-page-1/#comment-22797</link>
		<dc:creator>Ford Harding</dc:creator>
		<pubDate>Thu, 09 Apr 2009 00:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/2009/03/02/how-much-detail-should-you-give-when-answering-questions/#comment-22797</guid>
		<description>Steve

Most of us do.  Keep up the fight!

Ford Harding</description>
		<content:encoded><![CDATA[<p>Steve</p>
<p>Most of us do.  Keep up the fight!</p>
<p>Ford Harding</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve S</title>
		<link>http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/comment-page-1/#comment-22738</link>
		<dc:creator>Steve S</dc:creator>
		<pubDate>Wed, 08 Apr 2009 10:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/2009/03/02/how-much-detail-should-you-give-when-answering-questions/#comment-22738</guid>
		<description>Great post Ford. It's a tiny bit hard for me to read it without wincing because the general category of "over assuming" and answering what I infer the intent of the questions is, instead of confirming it, is something that I fall victim to.

It also reinforces the related success habit I keep trying to improve on, which is to get the prospect to do as much of the talking as possible.  Personally, I struggle with this.</description>
		<content:encoded><![CDATA[<p>Great post Ford. It&#8217;s a tiny bit hard for me to read it without wincing because the general category of &#8220;over assuming&#8221; and answering what I infer the intent of the questions is, instead of confirming it, is something that I fall victim to.</p>
<p>It also reinforces the related success habit I keep trying to improve on, which is to get the prospect to do as much of the talking as possible.  Personally, I struggle with this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ford Harding</title>
		<link>http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/comment-page-1/#comment-22663</link>
		<dc:creator>Ford Harding</dc:creator>
		<pubDate>Tue, 07 Apr 2009 11:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/2009/03/02/how-much-detail-should-you-give-when-answering-questions/#comment-22663</guid>
		<description>David

Thanks for your openness.  We have all made mistakes like the one you mention.  Sales skill requires going back to the basics again and again.

In answer to your question, I am not comfortable with "slyly," because it implies a possible deception.  The exchange between buyer and seller can help advance the buyer's understanding of his own problem.  That's a high-value exchange.  But if he really wants someone with foundry experience and feels he has a compelling reason for doing so, either I've got it or I don't.  If not, either I team with someone who does, or I stop wasting the buyer's time and my own and go pursue something else that better matches my quals.

Just don't assume that this is a go-no go issue before exploring it with the buyer.

Ford Harding</description>
		<content:encoded><![CDATA[<p>David</p>
<p>Thanks for your openness.  We have all made mistakes like the one you mention.  Sales skill requires going back to the basics again and again.</p>
<p>In answer to your question, I am not comfortable with &#8220;slyly,&#8221; because it implies a possible deception.  The exchange between buyer and seller can help advance the buyer&#8217;s understanding of his own problem.  That&#8217;s a high-value exchange.  But if he really wants someone with foundry experience and feels he has a compelling reason for doing so, either I&#8217;ve got it or I don&#8217;t.  If not, either I team with someone who does, or I stop wasting the buyer&#8217;s time and my own and go pursue something else that better matches my quals.</p>
<p>Just don&#8217;t assume that this is a go-no go issue before exploring it with the buyer.</p>
<p>Ford Harding</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/comment-page-1/#comment-22637</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 07 Apr 2009 02:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/2009/03/02/how-much-detail-should-you-give-when-answering-questions/#comment-22637</guid>
		<description>Ford - 

Great post, I have a pitch this week and will keep your vignette in mind. 

I find myself sometimes answering too long/voluteering too much information. I believe its rooted in a desire to be helpful, and perhaps a bad habit from early retail sales.

Worst I ever stepped in it: an owner once asked me (after we'd worked together for a couple of years) what I thought of a centralized system in one of his facilities. I could have said "I don't know, tell me more about it" but instead commented on the failure rates I'd heard of with other installations and that I thought they were problematic - of course, the system was his idea and pet, and he let me know it; it was embarrassing, and would have been catastrophic if we didn't have a good relationship (and if he didn't take such delight in making me squirm!). 

Can one be an enthusiastic expert witness, answering short, not volunteering info, but slyly leading the questioneer?</description>
		<content:encoded><![CDATA[<p>Ford - </p>
<p>Great post, I have a pitch this week and will keep your vignette in mind. </p>
<p>I find myself sometimes answering too long/voluteering too much information. I believe its rooted in a desire to be helpful, and perhaps a bad habit from early retail sales.</p>
<p>Worst I ever stepped in it: an owner once asked me (after we&#8217;d worked together for a couple of years) what I thought of a centralized system in one of his facilities. I could have said &#8220;I don&#8217;t know, tell me more about it&#8221; but instead commented on the failure rates I&#8217;d heard of with other installations and that I thought they were problematic - of course, the system was his idea and pet, and he let me know it; it was embarrassing, and would have been catastrophic if we didn&#8217;t have a good relationship (and if he didn&#8217;t take such delight in making me squirm!). </p>
<p>Can one be an enthusiastic expert witness, answering short, not volunteering info, but slyly leading the questioneer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ford Harding</title>
		<link>http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/comment-page-1/#comment-22615</link>
		<dc:creator>Ford Harding</dc:creator>
		<pubDate>Mon, 06 Apr 2009 21:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/2009/03/02/how-much-detail-should-you-give-when-answering-questions/#comment-22615</guid>
		<description>Chris,

I think your point a good one.  We all have slightly different images of the client asking the question based on our experiences.  Depending on the client's tone of voice, posture and other communication not captured in my description, different responses are appropriate.  "Is that important to you?" works for me, depending on that context.  If the client says it is, I need to know this and would follow up with, "Tell me more, please."  

I can say "Is that important to you?" with great earnestness or lightness and communicate different things, as you can do with your suggested wording. I learned long ago that words that work well for one person don't always work for another.  But we can find words that will accomplish the same end.

In short, I generally agree with your argument not to assume anything.   We agree on ends and principals; our means differ slightly.

Thanks for the comment.

Ford Harding</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>I think your point a good one.  We all have slightly different images of the client asking the question based on our experiences.  Depending on the client&#8217;s tone of voice, posture and other communication not captured in my description, different responses are appropriate.  &#8220;Is that important to you?&#8221; works for me, depending on that context.  If the client says it is, I need to know this and would follow up with, &#8220;Tell me more, please.&#8221;  </p>
<p>I can say &#8220;Is that important to you?&#8221; with great earnestness or lightness and communicate different things, as you can do with your suggested wording. I learned long ago that words that work well for one person don&#8217;t always work for another.  But we can find words that will accomplish the same end.</p>
<p>In short, I generally agree with your argument not to assume anything.   We agree on ends and principals; our means differ slightly.</p>
<p>Thanks for the comment.</p>
<p>Ford Harding</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Zdunich</title>
		<link>http://www.hardingco.com/blog/2009/04/06/how-much-detail-should-you-give-when-answering-questions/comment-page-1/#comment-22606</link>
		<dc:creator>Chris Zdunich</dc:creator>
		<pubDate>Mon, 06 Apr 2009 17:38:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.hardingco.com/blog/2009/03/02/how-much-detail-should-you-give-when-answering-questions/#comment-22606</guid>
		<description>Ford, simply asking "How do you mean, exactly?", with a sincere, questioning look on your face opens it up for an exact response.

Then, use strong listening skills to give them time to formulate the answer that will get you closer to what they are looking for.  

You can always ask second and third level questions, when necessary, to get the detail to answer this very important, in or out, question.

Your question, in my opinion, is also assumptive.

Also, the prospective client may answer your question with a yes.  What do you do, then?  You're right back where you started.

Q:  Have you worked in a foundry?  Maybe he wants someone who was actually an employee in a foundry.

Again, don't assume anything.</description>
		<content:encoded><![CDATA[<p>Ford, simply asking &#8220;How do you mean, exactly?&#8221;, with a sincere, questioning look on your face opens it up for an exact response.</p>
<p>Then, use strong listening skills to give them time to formulate the answer that will get you closer to what they are looking for.  </p>
<p>You can always ask second and third level questions, when necessary, to get the detail to answer this very important, in or out, question.</p>
<p>Your question, in my opinion, is also assumptive.</p>
<p>Also, the prospective client may answer your question with a yes.  What do you do, then?  You&#8217;re right back where you started.</p>
<p>Q:  Have you worked in a foundry?  Maybe he wants someone who was actually an employee in a foundry.</p>
<p>Again, don&#8217;t assume anything.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
