LinkedIn Twitter Facebook

Ben Kepes is a technology evangelist, an investor, a commentator and a business adviser. His business interests include a diverse range of industries from manufacturing to property to technology. As a technology commentator he has a broad presence both in the traditional media and extensively online. Ben covers the convergence of technology, mobile, ubiquity and agility, all enabled by the Cloud. His areas of interest extend to enterprise software, software integration, financial/accounting software, platforms and infrastructure as well as articulating technology simply for everyday users.

More about Ben here.

5 responses to “Just How Public should Your Product Roadmap Be?”

  1. Mike McDerment

    I think the question you need to ask yourself is do you want to be Steve Jobs (ie don’t tell anyone what you’re up to – though admittedly leaks happen sometimes) or Bill Gates (of Longhorn/Vista fame).

    Both approaches work…it’s up to you to decide which one works for you.

  2. Ben Kepes

    You’re right Mike – horses for courses. And your strategy obviously works well for you guys.

    Cheers for the comment

  3. Rohan Jayasekera

    Counter-arguments 1 and 2 apply only if there is no roadmap at all. The solution is to have a roadmap but not reveal it outside the company.

  4. Devan

    I find a product roadmap keeps our development team focused and honest about what we are going to deliver to our customers. Sometimes it is hard to differentiate between a direction, a trend or a whim, and it helps to go back to a ‘stone tablet’ with your original promises on it.

    But at times, it can be the veritable albatross around your neck too…

  5. Sty Liskit

    You should have a public roadmap*.

    *Public to your team and invested parties. Competitors, and other negative interests must be kept out. There should be a space where your team can know and discuss about what’s up, without worrying about who will read and what will be revealed.