When does it make sense to make your roadmap publically available, and what do you include (vs your internal roadmap)

Personally, I believe in having a very transparent roadmap. Not all companies are going to be able to communicate everything that is on their roadmap for legal and/or reg...

A public roadmap can serve as a tool to attract potential customers and increase the retention of existing customers by demonstrating that you are continually investing i...

I think public roadmaps make sense once you are post product market fit but it's important to remember to only lookout 6 months or so (with safe harbor for future usage/ ...

My general rule is that you should only share projects with customers that you're at least 80% confident you're going to deliver in the timeframe you indicate. This could...

I might have given you a very different answer to this question a year ago! I used to be paranoid about hiding my roadmap from my competitors, and would share broadly int...

I'm a big fan of publicly available roadmaps. They provide current and prospective customers with insight into where you plan to focus and serve as a great resource for S...

I am a huge fan of public roadmaps! But, I think this is depends on: Organizational cultural preference Mission of the company / product (are you building a product to...

Since I have joined GitLab, where our product roadmaps are publicly accessible (https://about.gitlab.com/direction/), I don't think I will ever go back to internal roadma...

I answered this partly in the earlier question “We’re pivoting our product, and it’s difficult to plan the roadmap too far out. How do we reset expectations on what produ...

There are three high-level options: Internal roadmap only Fully public: roadmap published externally for all customers and prospects Customer-facing roadmap that your ...

Interesting question! From my experience, there are two key questions to answer when thinking about going public with your roadmap. 1) Do we have a predictable sprint vel...

Making your roadmap publicly available can be a good idea when:Sharing your roadmap publicly can build trust with your customers to show that you value their input and ar...

This is an interesting question, because I think it highly depends on the leadership and culture of the company you work in. I've seen leadership figures have very strong...

There are a few gradations of what public means in practice – i.e. 100% open (e.g. with rankings), partially open (narrative, but not prioritized), public to customers. I...

Some companies do a great job in providing a public-facing roadmap. At one company I worked at, there used to be a Trello board where customers could add features, upvote...

I am a BIG proponent of having a version of the roadmap that can be shared externally! There are some tactical things you may need to do to ensure you can share and to ...

A public roadmap makes sense for open-source projects (like GitLab), developer tools, or products with an active, engaged community that values transparency. It should al...

Making a roadmap publicly available can build transparency and trust with customers, stakeholders, and partners. However, it's essential to carefully decide when and what...