Comments on: 5 reasons why sharing your product roadmap is a bad idea

By: Adam Greslye

Adam Greslye — Wed, 19 Oct 2011 12:55:12 +0000

Experience professional Sage account software with quick data entry.

By: Pashmina

Pashmina — Tue, 31 May 2011 21:49:01 +0000

Mike, while I agree with the 5 reasons you’ve outlined here, I was surprised by what LED me to your post . This forum thread: http://community.freshbooks.com/forums/viewtopic.php?id=7183 and the comments from the Freshbooks support staff didn’t spin it in such a positive manner.

From the wording and tone, the Support staff sounds powerless. Perhaps there’s a rift between the Support and PD teams. I’m optimistic and hoping that they are actually quite tightly integrated. Or perhaps it was just some subtle frustration on the part of some support staff. Either way, it does not look good.

By: Buy what we have today, not what we might have tomorrow KashFlow Accounting Software

Tue, 15 Mar 2011 13:12:50 +0000

[...] bonkers and I’ve “got a lot to learn”. No doubt. But I have a lot of respect for the others in the asylum with me, all of them. [...]

By: MercuryMinds

MercuryMinds — Wed, 29 Dec 2010 04:38:18 +0000

Very good post those who develop products like us. Thank you so much.

Dongan

By: Charles

Charles — Sat, 04 Dec 2010 14:13:28 +0000

i think its ok to expose some bits as its all about action and most people will never copy as their lazy.

By: Zach Aysan

Zach Aysan — Fri, 29 Oct 2010 17:15:33 +0000

Great post Mike. Good to see you guys are still rockin the blog

By: TechZing » TechZing 65 – Regretting The Future

TechZing » TechZing 65 – Regretting The Future — Mon, 06 Sep 2010 22:45:59 +0000

[...] AI and creating a networked version of the game, the downside to radical transparency and reasons not to disclose your product roadmap, Cargo Cultism on Hacker News, India’s red rain and Panspermia, ACH (Analysis of [...]

By: Fresh Casey

Fresh Casey — Tue, 31 Aug 2010 18:57:05 +0000

Casey from FreshBooks here…

I’m the Director of Product Management for FreshBooks.

Sahil, one thing I’ve learned working on features for FreshBooks customers is that its important to start with understanding why someone wants a particular feature. Once you start peeling that onion back and digging deeper into why, you start to discover interesting things. Its from the deeper understanding that you will build the right feature to address their true need. Once you’ve solved the “need” with a feature, customers will get really excited about it.

Hope that help.

Casey

By: Sahil P.

Sahil P. — Tue, 31 Aug 2010 18:32:15 +0000

I have noticed customers request features but once released they really don’t care about it. So, the question is if people really know what they want?

By: Darren Negraeff

Darren Negraeff — Mon, 30 Aug 2010 22:27:05 +0000

Great post – I had noticed your third point as well (delay purchase decisions) but had not put two and two together yet. Of course they’re going to delay – why didn’t I think of that!