Do you keep a public roadmap ?
Anil Matcha
37 replies
Replies
Kartike Bansal@kraten
@matcha_anil Yes, we started using the public roadmap recently. We'll soon update the roadmap with more details. You can check it out at: https://roadmap.hansei.app
Btw, we're launching today on PH!
Will appreciate your support and feedback: https://www.producthunt.com/post...
Share
@dot_brand With the public roadmap, users get better visibility and more trust in the development lifecycle of the product. The roadmap allows us to align our features what we're building with the user feedback.
Thanks Kevin for the follow :)
@dot_brand @kraten Completely agree. I find it keeps our users involved and contributing to our decisions. That said, when we trail launch dates and commitments, it does mean I need to communicate those decisions. I think it's worth that though and our community really appreciates it.
Hey! Yes, and it's really important for our community to see our product's development. We're including the requests of our community members in our roadmap too. People feel that we care about their feedback, and we really do :)
https://www.retable.io/roadmap
@arzuozkan I love this... Kanban style too, makes it simple to read and understand. I especially love that you list the 'completed' parts of the roadmap... that helps demonstrate that as a user, you've already experienced and benefited from development.
@arzuozkan @drewsalesplaybookbuilder It's indeed inspiring! I will discuss with my programmer and use this method! XD
I created mine recently, divided into two sections.
The Feedback section is very convenient to allow people to vote on feature-request and report bugs.
Also very convenient is the Changelog section, to which users can subscribe and receive email notifications about updates, for example.
You can check it out here: https://feedback.botrush.io/
@tailormeta UI looks awesome :)
Will be happy to try it out.
Are you planning to add kanban board section too?
Yes. We have been doing it with Product Board https://www.morgen.so/roadmap but are now moving over to Canny https://morgen.canny.io/ (it's not as visually nice but is more transparent and community oriented).
We've ask for user requests via salesforge.canny.io
QQ for those who have public roadmaps - what if you change plans/priorities and have customers waiting for a feature as they've learnt about it from a roadmap?
no... but I will in 3 hours ;)
Yes, I think a public roadmap is a great way to show your customers and potential customers that you live and breath truth and transparency. It can also bring you closer to people in a community kind of way. It's important to be able to give people the chance also to add their suggestions for your future roadmap, maybe you missed something big (or small) that could make or break your chances of success.
It allows users to stay informed about upcoming features and improvements, creating a sense of involvement and anticipation. Moreover, a public roadmap can serve as a valuable feedback loop, enabling you to gauge user priorities and align development efforts accordingly.
@mani_abod Indeed! I even do this to my investors, trying to keep everything informed, and this makes them trusting me more and willing to back us more!
There is no public road map here. Actually, I find them to be somewhat limiting. I prefer the ability to change course without disappointing others.
Does anyone have any experience with the benefits/drawbacks of this for really early stage companies that do not have a lot of users yet?
@vincentropy So far, I only see the benefits. If some requests are wayyyy too off, I would spend time to explain to them the reason behind every iteration~ Most of them understand it and they even feel we really put our souls and hearts in the product!
We did not, but will soon be publishing it on our website- https://www.quido.fi/
The reason we decided to do it is because it gives more transparency to our users regarding what we are working on currently and what features are coming next.
Yes, I don’t understand why founders make a mystery out of everything. If you are not developing a time machine or any other unique technology, then there is not much to hide. Plus, this is good marketing so that users understand what will happen next.
@nickanisimov Totally agree. Recently I've got a newsletter from a big SaaS brand that was like "We will be announcing something big soon. But we can't tell what, but trust us, it's big. But sign up for the webinar". Very convincing, very... :)
Currently we do not but we haven’t released our product to the public yet. I’d be curious to hear the benefits though of this. I feel it could limit you to plan to far in advance and not listen to your customers for that perfect product market fit.
Yes, we started sharing our roadmap publicly recently, after a few users asked to see it! So now it's available in our forum. If anyone's curious, you can check it out here: https://forum.rea.ch/latest?boar... 🚀
Currently, we don't have a public roadmap for Booomerang.io but we are considering making it public in the future. I know it's important to be transparent with the community but we want to focus on marketing efforts right now.
If anyone thinks I'm doing it wrong, please let me know your thoughts :)
Yes, using LoopedIn https://app.loopedin.io/lyrist
No... Mostly I keep things to myself and prioritize according to what I feel is the most important next. I think Public Roadmaps change so often they are pointless.
Yes, we maintain a public roadmap to transparently communicate our company's upcoming plans, features, and product developments with our users and stakeholders. This enables us to gather feedback and keep our community informed about our progress and future direction.