<?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: 5 reasons why sharing your product roadmap is a bad idea</title>
	<atom:link href="http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/</link>
	<description>A blog about our thoughts on entrepreneurship, teamwork, our services, the Web and anything we find interesting.</description>
	<lastBuildDate>Sat, 21 Nov 2009 07:27:46 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ignacio G del Valle</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-68117</link>
		<dc:creator>Ignacio G del Valle</dc:creator>
		<pubDate>Sat, 24 Oct 2009 17:33:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-68117</guid>
		<description>I agree with most of your points, but I think if you are receiving lot of input from your customers, is good to manage their expectations, in such a way they don&#039;t need to look elsewhere to satisfy their needs.
Maybe a compromise is to publish a partial roadmap, so you keep some surprises under the hood, but at the same time are showing your commitment to deliver the new features your customers expect.
I think this is specially important if you are offering a web-based service, or if you are offering a maintence contract.</description>
		<content:encoded><![CDATA[<p>I agree with most of your points, but I think if you are receiving lot of input from your customers, is good to manage their expectations, in such a way they don&#8217;t need to look elsewhere to satisfy their needs.<br />
Maybe a compromise is to publish a partial roadmap, so you keep some surprises under the hood, but at the same time are showing your commitment to deliver the new features your customers expect.<br />
I think this is specially important if you are offering a web-based service, or if you are offering a maintence contract.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Kamuchau</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-67086</link>
		<dc:creator>John Kamuchau</dc:creator>
		<pubDate>Wed, 15 Jul 2009 02:54:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-67086</guid>
		<description>I agree with this to a huge extent especially a commercial product. My strategy has always been to set up a landing page with a teaser of what the product can do and one or more screenshots and then wait until launch or when the product is mature enough to for private beta. 
However , for open source projects , i believe that a road map is critical.</description>
		<content:encoded><![CDATA[<p>I agree with this to a huge extent especially a commercial product. My strategy has always been to set up a landing page with a teaser of what the product can do and one or more screenshots and then wait until launch or when the product is mature enough to for private beta.<br />
However , for open source projects , i believe that a road map is critical.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Ingle</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-67066</link>
		<dc:creator>Phillip Ingle</dc:creator>
		<pubDate>Thu, 09 Jul 2009 15:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-67066</guid>
		<description>I think that you need also to consider the old maxim that ‘the customer is always right’. At the end of the day the customer does pay the Freshbooks staff wages, and pay for the development costs of the product. You should not discount them completely. 

I tend to think that May Chu’s bullish and Sonia Simones engaged customers, customers who might have already invested significant resources in choosing a system, and significant cost in paying for yours do have the right to request features, and to have some idea of whether those features are in the pipeline, or shelved. By not keeping those customers up to date, you are failing to provide them with a sense of security in your product/system and you risk losing them.</description>
		<content:encoded><![CDATA[<p>I think that you need also to consider the old maxim that ‘the customer is always right’. At the end of the day the customer does pay the Freshbooks staff wages, and pay for the development costs of the product. You should not discount them completely. </p>
<p>I tend to think that May Chu’s bullish and Sonia Simones engaged customers, customers who might have already invested significant resources in choosing a system, and significant cost in paying for yours do have the right to request features, and to have some idea of whether those features are in the pipeline, or shelved. By not keeping those customers up to date, you are failing to provide them with a sense of security in your product/system and you risk losing them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kaimaan &#187; Secrecy or Transparency?</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-65142</link>
		<dc:creator>Kaimaan &#187; Secrecy or Transparency?</dc:creator>
		<pubDate>Wed, 10 Dec 2008 13:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-65142</guid>
		<description>[...] process.  This morning I ran into interesting conversation between two blogs Read Write Web and Freshbook. Freshbook is trying to keep everything for them selves before the release while Read Write Web [...]</description>
		<content:encoded><![CDATA[<p>[...] process.  This morning I ran into interesting conversation between two blogs Read Write Web and Freshbook. Freshbook is trying to keep everything for them selves before the release while Read Write Web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Cornish</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-65092</link>
		<dc:creator>Dan Cornish</dc:creator>
		<pubDate>Fri, 28 Nov 2008 15:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-65092</guid>
		<description>I will argue that a discussion forum and user group are  another way for customers to gang up on you. Look at the discussion forums at 37 Signals. The gripes of customers provides a development roadmap to build a competitive product.  Also if enough customers say you suck, you will be forced to veer off your own plan to cut the noise down. Sometimes product development can cause you to have a tin ear to your customers but sometimes you just end up oiling the squeaky wheel.</description>
		<content:encoded><![CDATA[<p>I will argue that a discussion forum and user group are  another way for customers to gang up on you. Look at the discussion forums at 37 Signals. The gripes of customers provides a development roadmap to build a competitive product.  Also if enough customers say you suck, you will be forced to veer off your own plan to cut the noise down. Sometimes product development can cause you to have a tin ear to your customers but sometimes you just end up oiling the squeaky wheel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Abraham</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-65088</link>
		<dc:creator>Roy Abraham</dc:creator>
		<pubDate>Fri, 28 Nov 2008 05:10:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-65088</guid>
		<description>Insightful post. 

I made that sales mistake once in the past (telling a potential client about upcoming features).

Besides there&#039;s something odd about a product if it needs to sell itself by telling you what it plans to do in the future.</description>
		<content:encoded><![CDATA[<p>Insightful post. </p>
<p>I made that sales mistake once in the past (telling a potential client about upcoming features).</p>
<p>Besides there&#8217;s something odd about a product if it needs to sell itself by telling you what it plans to do in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sonia Simone &#124; Remarkable Communication</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-65078</link>
		<dc:creator>Sonia Simone &#124; Remarkable Communication</dc:creator>
		<pubDate>Thu, 27 Nov 2008 04:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-65078</guid>
		<description>It&#039;s fascinating to me to watch passionate, engaged customers become so certain that they have the RIGHT to all of your business processes and closed-door information. It&#039;s a great sign but it&#039;s still a pain in the ass.</description>
		<content:encoded><![CDATA[<p>It&#8217;s fascinating to me to watch passionate, engaged customers become so certain that they have the RIGHT to all of your business processes and closed-door information. It&#8217;s a great sign but it&#8217;s still a pain in the ass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike McDerment</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-65067</link>
		<dc:creator>Mike McDerment</dc:creator>
		<pubDate>Tue, 25 Nov 2008 14:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-65067</guid>
		<description>@todd good to hear from you :)

re printing cheques: i hear you, and the specter of handwriting is indeed painful - we&#039;ll keep it in mind.</description>
		<content:encoded><![CDATA[<p>@todd good to hear from you <img src='http://www.freshbooks.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>re printing cheques: i hear you, and the specter of handwriting is indeed painful &#8211; we&#8217;ll keep it in mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: todd lucier</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-65062</link>
		<dc:creator>todd lucier</dc:creator>
		<pubDate>Mon, 24 Nov 2008 14:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-65062</guid>
		<description>Hi Mike,
I can see why you moved away from the PaddlingOntario type projects into this exciting venture.  Its really nice to see how your service has evolved.  And future evolutions.... hmmm.  I have one wish:
Printing Cheques...
Coming from Simply Accounting, going back to handwriting cheques will be a pain.  Any way to simplify the process for offline payments?</description>
		<content:encoded><![CDATA[<p>Hi Mike,<br />
I can see why you moved away from the PaddlingOntario type projects into this exciting venture.  Its really nice to see how your service has evolved.  And future evolutions&#8230;. hmmm.  I have one wish:<br />
Printing Cheques&#8230;<br />
Coming from Simply Accounting, going back to handwriting cheques will be a pain.  Any way to simplify the process for offline payments?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dragonwize</title>
		<link>http://www.freshbooks.com/blog/2008/11/11/5-reasons-why-sharing-your-product-roadmap-is-a-bad-idea/comment-page-1/#comment-65023</link>
		<dc:creator>dragonwize</dc:creator>
		<pubDate>Tue, 18 Nov 2008 17:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.freshbooks.com/?p=2324#comment-65023</guid>
		<description>&quot;Releasing on a specific date what you said you would is a packaged software thing...&quot;

I completely agree with this statement. But I would also agree that being secretive is also a part of that same industry.

I believe that is more about how your industry and business model that will determine how much information you can share and do well. Being transparent is a great thing but it does not work with all business models and vice versa.

In the end, it is the company management that is the key factor in determining what will work.</description>
		<content:encoded><![CDATA[<p>&#8220;Releasing on a specific date what you said you would is a packaged software thing&#8230;&#8221;</p>
<p>I completely agree with this statement. But I would also agree that being secretive is also a part of that same industry.</p>
<p>I believe that is more about how your industry and business model that will determine how much information you can share and do well. Being transparent is a great thing but it does not work with all business models and vice versa.</p>
<p>In the end, it is the company management that is the key factor in determining what will work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
