<?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 for Barrall</title>
	<atom:link href="http://barrall.com/wp/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://barrall.com/wp</link>
	<description>Building Business</description>
	<lastBuildDate>Fri, 18 Mar 2011 17:48:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Don&#8217;t Engineer Anything You Can&#8217;t Sell by Ken Rosen</title>
		<link>http://barrall.com/wp/2011/03/14/dont-engineer-anything-you-cant-sell/#comment-52</link>
		<dc:creator>Ken Rosen</dc:creator>
		<pubDate>Fri, 18 Mar 2011 17:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=207#comment-52</guid>
		<description>Geoff,
It no longer surprises me when you I come to identical conclusions from different directions...and this is one more time. So many companies struggle with the Marketing/Engineering relationship and try to define it via Market Req&#039;d Docs (MRDs), Product Req&#039;t Docs (PRDs), and the like. I&#039;ve moved to getting Marketing to simply create the market-responsive brochure they&#039;d like to distribute in 12-18 months. The product plan makes sure Marketing isn&#039;t lying. It&#039;s a collaboration, of course, on both sides. But I agree that clarifying the story upfront helps prevent a long list of feature requests that don&#039;t culminate in a core, compelling, profitable result.

Cheers, Ken

Ken Rosen
Performance Works</description>
		<content:encoded><![CDATA[<p>Geoff,<br />
It no longer surprises me when you I come to identical conclusions from different directions&#8230;and this is one more time. So many companies struggle with the Marketing/Engineering relationship and try to define it via Market Req&#8217;d Docs (MRDs), Product Req&#8217;t Docs (PRDs), and the like. I&#8217;ve moved to getting Marketing to simply create the market-responsive brochure they&#8217;d like to distribute in 12-18 months. The product plan makes sure Marketing isn&#8217;t lying. It&#8217;s a collaboration, of course, on both sides. But I agree that clarifying the story upfront helps prevent a long list of feature requests that don&#8217;t culminate in a core, compelling, profitable result.</p>
<p>Cheers, Ken</p>
<p>Ken Rosen<br />
Performance Works</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by geoffbarrall</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-51</link>
		<dc:creator>geoffbarrall</dc:creator>
		<pubDate>Thu, 17 Mar 2011 20:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-51</guid>
		<description>Totally agree. A good way to sniff this out is to determine if the customer is happy to devote time to exploring alternative workarounds so they can still use your product. If they are then usually they like your product but genuinely have a problem fitting it in, if not then it&#039;s most likely a &quot;don&#039;t call us....&quot;.</description>
		<content:encoded><![CDATA[<p>Totally agree. A good way to sniff this out is to determine if the customer is happy to devote time to exploring alternative workarounds so they can still use your product. If they are then usually they like your product but genuinely have a problem fitting it in, if not then it&#8217;s most likely a &#8220;don&#8217;t call us&#8230;.&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by Robin Harris</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-50</link>
		<dc:creator>Robin Harris</dc:creator>
		<pubDate>Thu, 17 Mar 2011 19:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-50</guid>
		<description>A related issue: often customers will say they won&#039;t buy because they want feature X, while the real reason is they don&#039;t see the point. 

Either they aren&#039;t the target customer, or they don&#039;t believe the product will deliver the value promised, or they don&#039;t have the political clout to get a new vendor in the door, or ??? Whatever it is, it often isn&#039;t feature X.</description>
		<content:encoded><![CDATA[<p>A related issue: often customers will say they won&#8217;t buy because they want feature X, while the real reason is they don&#8217;t see the point. </p>
<p>Either they aren&#8217;t the target customer, or they don&#8217;t believe the product will deliver the value promised, or they don&#8217;t have the political clout to get a new vendor in the door, or ??? Whatever it is, it often isn&#8217;t feature X.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by geoffbarrall</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-29</link>
		<dc:creator>geoffbarrall</dc:creator>
		<pubDate>Tue, 09 Nov 2010 23:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-29</guid>
		<description>Well said.</description>
		<content:encoded><![CDATA[<p>Well said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by Carl</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-28</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Tue, 09 Nov 2010 23:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-28</guid>
		<description>I think some of the comments have missed the really important point - that is the sales team has to be able to sell the product/service with whatever features are there at the time. Yes you can say that perhaps that conversation with the CEO &amp; the sales rep may not have been the right approach, but thats not the point.
Sometimes businesses get sidetracked by the &#039;complex&#039; things, when really at the end of the day business is quite simple, you only survive if you can sell your product or service with whatever features/functions it has at that point in time.</description>
		<content:encoded><![CDATA[<p>I think some of the comments have missed the really important point &#8211; that is the sales team has to be able to sell the product/service with whatever features are there at the time. Yes you can say that perhaps that conversation with the CEO &amp; the sales rep may not have been the right approach, but thats not the point.<br />
Sometimes businesses get sidetracked by the &#8216;complex&#8217; things, when really at the end of the day business is quite simple, you only survive if you can sell your product or service with whatever features/functions it has at that point in time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by geoffbarrall</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-27</link>
		<dc:creator>geoffbarrall</dc:creator>
		<pubDate>Mon, 08 Nov 2010 21:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-27</guid>
		<description>Odette,

Frank understood well what his market needed and regularly kept up to date with customer requests so that should be understood. As CEO though it was not his job to manage that process directly nor to provide his sale force with a timeline for improvements. That approach most often tends to stall sales as customers and the sales reps wait for &quot;feature X&quot; to become available and usually isn&#039;t welcomed by sales management. 

I also feel that the thought process in regards to companies needing to keep up with a rapidly changing market isn&#039;t a good idea. Young product companies don&#039;t have the resources to do that and product cycles tend to remain in the 12 -18 month range just as they always have. It&#039;s worth considering the adoption rates of any real changes in the storage marketplace as I think you&#039;ll see that things change a lot less rapidly than one might think. Take iSCSI adoption or SATA adoption both of which are still really breaking ground 6 - 8 years in. Much better to focus on differentiation and not try to ride every trend (cloud storage for example) as it occurs. There is usually time during the later stages of the maturation cycle for new technology to implement it in your product line.</description>
		<content:encoded><![CDATA[<p>Odette,</p>
<p>Frank understood well what his market needed and regularly kept up to date with customer requests so that should be understood. As CEO though it was not his job to manage that process directly nor to provide his sale force with a timeline for improvements. That approach most often tends to stall sales as customers and the sales reps wait for &#8220;feature X&#8221; to become available and usually isn&#8217;t welcomed by sales management. </p>
<p>I also feel that the thought process in regards to companies needing to keep up with a rapidly changing market isn&#8217;t a good idea. Young product companies don&#8217;t have the resources to do that and product cycles tend to remain in the 12 -18 month range just as they always have. It&#8217;s worth considering the adoption rates of any real changes in the storage marketplace as I think you&#8217;ll see that things change a lot less rapidly than one might think. Take iSCSI adoption or SATA adoption both of which are still really breaking ground 6 &#8211; 8 years in. Much better to focus on differentiation and not try to ride every trend (cloud storage for example) as it occurs. There is usually time during the later stages of the maturation cycle for new technology to implement it in your product line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by Odette Faghani</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-26</link>
		<dc:creator>Odette Faghani</dc:creator>
		<pubDate>Mon, 08 Nov 2010 21:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-26</guid>
		<description>Agreed you must sell what you have, but the vision for the future comes partly from clients asking for improvements. Frank should have taken the field reps&#039; input and tried to get a timeline of when those improvements could be made while simultaneously exhorting the teams to sell what they had. His handling of the situation is quite dated, given that technology today changed at warp speed and companies that cannot keep up will falter.</description>
		<content:encoded><![CDATA[<p>Agreed you must sell what you have, but the vision for the future comes partly from clients asking for improvements. Frank should have taken the field reps&#8217; input and tried to get a timeline of when those improvements could be made while simultaneously exhorting the teams to sell what they had. His handling of the situation is quite dated, given that technology today changed at warp speed and companies that cannot keep up will falter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by geoffbarrall</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-25</link>
		<dc:creator>geoffbarrall</dc:creator>
		<pubDate>Mon, 08 Nov 2010 18:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-25</guid>
		<description>Totally agree and in fact that&#039;s something that Data Domain did too. The question isn&#039;t about getting customer feedback which I&#039;m sure everybody would agree is valuable but rather about having the ability to make sales with what&#039;s on the wagon. Feedback is valuable but you still have to make day to day sales ahead of product improvement.</description>
		<content:encoded><![CDATA[<p>Totally agree and in fact that&#8217;s something that Data Domain did too. The question isn&#8217;t about getting customer feedback which I&#8217;m sure everybody would agree is valuable but rather about having the ability to make sales with what&#8217;s on the wagon. Feedback is valuable but you still have to make day to day sales ahead of product improvement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A Lesson in Sales Management From Frank Slootman by W. Curtis Preston</title>
		<link>http://barrall.com/wp/2010/11/08/a-lesson-in-sales-management-from-frank-slootman/#comment-24</link>
		<dc:creator>W. Curtis Preston</dc:creator>
		<pubDate>Mon, 08 Nov 2010 17:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=203#comment-24</guid>
		<description>I think there&#039;s a middle ground between what you were doing at BlueArc and what Frank did.  When genuine input from the field is met with a stern-faced CEO basically threatening termination, all you&#039;re doing is making sure you&#039;ll never get any input from that salesperson again. The proper response, IMHO, is &quot;Please put that in salesforce.com. We use that to look for trends.&quot;  Then when your salesforce.com report says that 60% of lost opps were lost because you don&#039;t have SnapMirror (or something like it).</description>
		<content:encoded><![CDATA[<p>I think there&#8217;s a middle ground between what you were doing at BlueArc and what Frank did.  When genuine input from the field is met with a stern-faced CEO basically threatening termination, all you&#8217;re doing is making sure you&#8217;ll never get any input from that salesperson again. The proper response, IMHO, is &#8220;Please put that in salesforce.com. We use that to look for trends.&#8221;  Then when your salesforce.com report says that 60% of lost opps were lost because you don&#8217;t have SnapMirror (or something like it).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing a Presentation to Raise Venture CapitalAn Illustrated Example by Writing A Presentation to Raise Venture Capital : The Overview &#124; Barrall</title>
		<link>http://barrall.com/wp/2010/09/23/writing-a-presentation-to-raise-venture-capital-an-illustrated-example/#comment-17</link>
		<dc:creator>Writing A Presentation to Raise Venture Capital : The Overview &#124; Barrall</dc:creator>
		<pubDate>Mon, 25 Oct 2010 22:53:06 +0000</pubDate>
		<guid isPermaLink="false">http://barrall.com/wp/?p=129#comment-17</guid>
		<description>[...] Skip to content BlogBioContact        &#8592; Writing a Presentation to Raise Venture CapitalAn Illustrated Example [...]</description>
		<content:encoded><![CDATA[<p>[...] Skip to content BlogBioContact        &larr; Writing a Presentation to Raise Venture CapitalAn Illustrated Example [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.209 seconds -->

