![\"Canny's](\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/04\/Canny-roadmap.png\")
There are huge benefits to a public product roadmap\u2014even if it feels a little intimidating.<\/p>\n\n\n\n
Let’s explore how to overcome that fear and build public roadmaps your users are drawn to. <\/p>\n\n\n\n\n\n
What is a public roadmap?<\/strong><\/h2>\n\n\n\nA product roadmap<\/a> is a visual representation of your product\u2019s direction, priorities, and progress over time. Roadmaps are a foundational product management tool.<\/p>\n\n\n\nA public product roadmap is the same, but it shares your product’s journey with the world. It’s a glimpse into what’s happening behind the scenes: upcoming features, bug fixes, and product updates<\/a>. Public roadmaps invite your users into the planning process, fostering a community feel. It’s a living document that communicates the why, what, and when of product initiatives to internal teams, stakeholders, and customers. <\/p>\n\n\n\nThis roadmap is open for everyone to see \u2013 users, customers, competitors, and more. <\/p>\n\n\n\n
Why does it matter?<\/strong><\/p>\n\n\n\n\n- Builds trust:<\/strong> shows you’re confident in your vision<\/li>\n\n\n\n
- Vision sharing:<\/strong> it aligns your team and customers with the product’s long-term vision and every new feature<\/li>\n\n\n\n
- Promotes transparency<\/strong>: makes users feel included and drives customer loyalty<\/li>\n\n\n\n
- Feedback loop:<\/strong> opens a channel for receiving and integrating customer feedback directly into the product development cycle<\/li>\n\n\n\n
- Prioritization:<\/strong> helps to make informed decisions on what to build next and focuses resources on high-impact features<\/a><\/li>\n\n\n\n
- Expectation management:<\/strong> clearly communicates upcoming changes and features, manages customer expectations<\/li>\n<\/ul>\n\n\n\n
So, with all these benefits, why wouldn’t you make your roadmap public?<\/p>\n\n\n\n
Sometimes the roadmap’s contents aren’t fit to be shared publicly. A few examples could include:<\/p>\n\n\n\n
\n- Plans that include proprietary or confidential information<\/li>\n\n\n\n
- Roadmaps for products that only have internal use<\/li>\n\n\n\n
- Top-secret projects that you can’t have a competitor learning about<\/li>\n<\/ol>\n\n\n\n
You can probably think of many other examples warranting a private roadmap (aka internal roadmap). <\/p>\n\n\n\n
When deciding whether to make your roadmap public, make sure you can tolerate the risks. Also, weigh them against the potential benefits. <\/p>\n\n\n\n
Public roadmaps are critical for SaaS companies<\/h3>\n\n\n\n
Public roadmaps are useful for all types of companies, but critical for SaaS. SaaS customers expect regular feature development. They expect their feedback to be heard. And, they want to know when you work on their feedback and resolve issues. A public roadmap helps you satisfy all those expectations.<\/p>\n\n\n\n
How do I build a public roadmap?<\/h3>\n\n\n\n
Building a public roadmap isn’t much different than building any other roadmap. You just need a way to make it publicly accessible. <\/p>\n\n\n\n
Here’s a quick list of things you’ll need to do:<\/p>\n\n\n\n
\n- Define goals<\/strong>: start with clear objectives. What do you want your roadmap to achieve?<\/li>\n\n\n\n
- Collect insights<\/strong>: involve stakeholders \u2014 customers, team members, and partners<\/li>\n\n\n\n
- Select a tool<\/strong>: Choose a roadmap tool<\/a> that suits your needs<\/li>\n\n\n\n
- Prioritize features<\/a><\/strong>: rank features based on impact and feasibility<\/li>\n\n\n\n
- Share updates<\/strong>: post updates and release notes<\/a> covering progress and changes <\/li>\n\n\n\n
- Encourage feedback<\/strong>: open channels for feedback to refine your product<\/li>\n<\/ul>\n\n\n\n
The easiest way is to use a product roadmap tool<\/a> that supports public roadmaps, feedback management, and release notes.<\/p>\n\n\n\nIf I have a public product roadmap, will competitors steal my ideas?<\/h2>\n\n\n\n
It\u2019s hard to get over the fear that a competitor might look at your public roadmap. And, they might build features exactly like the ones you\u2019re currently working on.<\/p>\n\n\n\n
Is it a possibility? Realistically, yes. If you share details of your process, it\u2019s possible that people will try to duplicate what you\u2019re doing well.<\/p>\n\n\n\n
But, the benefits of having a public roadmap outweigh this potential con. We\u2019ll get to those benefits shortly.<\/p>\n\n\n\n
Ultimately, the issue of idea theft comes down to this:<\/p>\n\n\n\n
If competitors are looking to your roadmap for inspiration, that means they\u2019re leaning on your customer base to tell them what to build\u2014not their own. At the end of the day, this will hurt them, not you.<\/p>\n\n\n\n
I reached out to Tim Soulo of Ahrefs<\/a> (and Canny customer<\/a>) to get his input. He believes there aren\u2019t any critical downsides to a public-facing roadmap:<\/p>\n\n\n\n\n\u201cIf our competitors want to focus on what customers request from us instead of what their customers request from them\u2014it’s their choice.\u201d<\/p>\n\n\n\n
– Tim<\/p>\n<\/blockquote>\n\n\n
\n![\"Ahrefs](\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\")
Ahrefs uses a public Canny roadmap<\/a> to track feature requests<\/figcaption><\/figure>\n<\/div>\n\n\nWith that said, here are 6 reasons why having a public roadmap will benefit you, and help you build a better product.<\/p>\n\n\n\n
6 reasons why you should have a public product roadmap<\/h2>\n\n\n\n1. It offers transparency<\/h3>\n\n\n\n
When you have a public roadmap, you can show your customer base exactly what you\u2019re building.<\/p>\n\n\n\n
There\u2019s hardly a better way to be transparent than by showing the world what you\u2019re working on.<\/p>\n\n\n\n
Why this matters:<\/strong><\/p>\n\n\n\nTransparency is huge when it comes to driving loyalty. In one survey on the ROI of transparency<\/a>, 94% of consumers said they are likely to be loyal to a brand that is transparent. And, 73% said they\u2019d be willing to pay more to do business with a more transparent company.<\/p>\n\n\n\nWe reached out to Tom Redman, head of product at Buffer. Anyone can access the Buffer roadmap<\/a>; For Tom, having a public roadmap aligns with Buffer\u2019s overall culture.<\/p>\n\n\n\n\n\u201cAt Buffer, we’re \u2018transparent by default.\u2019 That is, if we don’t have a compelling reason for something to be private, it’ll be shared transparently.\u201d<\/p>\n\n\n\n
– Tom<\/p>\n<\/blockquote>\n\n\n\nBuffer\u2019s roadmap<\/figcaption><\/figure>\n\n\n\nBeing upfront and honest with your customers is hugely valuable. Using a roadmap to show how your company actually takes on work is a big deal. You\u2019re giving your customers a look behind the curtain. They\u2019ll value that level of trust and commitment to transparency.<\/p>\n\n\n\n
2. It manages expectations for what you\u2019re building (and not building)<\/h3>\n\n\n\n
When users can see your roadmap, they can see what your current priorities are. They\u2019ll be able to see product direction and get a sense of your goals.<\/p>\n\n\n\n
If you\u2019re working on improving an aspect of your tool, you can show that in your roadmap. If your product doesn\u2019t have a feature, you can show that you\u2019re building it.<\/p>\n\n\n\n
And, if you\u2019re not building something, they\u2019ll see that too.<\/p>\n\n\n\n
Why does this matter?<\/strong><\/p>\n\n\n\nIf you have key planned features in the pipeline, a public roadmap gives potential users a look at what you\u2019re building. It\u2019s added value that your product might not have currently, but will soon.<\/p>\n\n\n\n
If a current customer sees active work on a feature they really want, it can prevent churn<\/a>. Similarly, a public-facing roadmap can serve as a sales tool for prospective customers<\/a>. You\u2019ll be able to show that you\u2019re actively working on certain features that they need.<\/p>\n\n\n\nAnd, on the flip side, it shows if you aren\u2019t working on a feature. Hearing a clear \u201cno, we aren\u2019t working on that right now\u201d is better than not knowing.<\/p>\n\n\n\n
\n“It’s a good way for our customers to see that their feature request is not as popular as they were hoping it would be.”<\/p>\n\n\n\n
– Tim<\/p>\n<\/blockquote>\n\n\n\n
Public roadmaps put things into perspective. You\u2019ll be able to set expectations for what isn\u2019t going to happen<\/a> as much as what is. This helps keep your users from being disappointed or feeling left in the dark.<\/p>\n\n\n\nThis is especially impactful if you\u2019re using a product roadmapping tool like Canny<\/a> with feature voting. If a suggestion has a very limited number of votes, users can better understand why you\u2019ve decided not to add a feature to your roadmap.<\/p>\n\n\n\n3. It cuts down on questions<\/h3>\n\n\n\n
When your users can see what you\u2019re working on, there\u2019s less need to reach out with questions.<\/p>\n\n\n\n
If you update your roadmap regularly, customers can easily see where you are on a certain feature. They\u2019ll have less need to reach out and ask about progress.<\/p>\n\n\n\n
Why does this matter?<\/p>\n\n\n\n
You\u2019ll lessen the load on your customer success or customer experience team<\/a>, to start. The fewer customers have to ask about the status of a feature they need, the less time you need to spend updating them. And, those teams won’t have to ask the product team for that info either. <\/p>\n\n\n\nOn the flip side, your users won\u2019t have to spend valuable time reaching out to ask questions. Instead, they can just check out your roadmap (you can also update it automatically \u2014 see #5). Eliminating unnecessary hoops to jump through makes for a better customer experience.<\/p>\n\n\n\n
\n\u201c[Transparency] was the primary driver for us to have a public roadmap, but the practical benefit is that we can send customers or others with inquiries there to see what we’re working on, vote for, or even comment on upcoming items on the roadmap.<\/p>\n\n\n\n
That’s been very helpful in sharing what our priorities are.\u201d<\/p>\n\n\n\n
– Tom<\/p>\n<\/blockquote>\n\n\n\n
4. It shows how long things really take<\/h3>\n\n\n\n
You might have a very understanding customer base. They might totally get that it takes some time to build, test, and ship updates.<\/p>\n\n\n\n
But, you might occasionally have to deal with frustration, too. When we want things, we often want them immediately.<\/p>\n\n\n\n
When you have a public roadmap, you can lay out the steps your team takes to get from A to Z.<\/p>\n\n\n\n
Users can follow along and see what\u2019s getting done and when. And, they will have a better understanding of how long it will take for new updates or features to be introduced.<\/p>\n\n\n\n
Why does this matter?<\/strong><\/p>\n\n\n\nShowing how long things take offers a sense of perspective. It grounds the process. Rather than rolling out improvements seemingly at random, users can see the steps.<\/p>\n\n\n\n
You\u2019ll also be able to better manage timeline expectations. A roadmap shows that things are happening, just not overnight.<\/p>\n\n\n
\n<\/figure>\n<\/div>\n\n\nFinally, users (and prospects) will appreciate that you\u2019re continually improving (see the conversation above from the SaaS Growth Hacks Facebook group<\/a> for an example). A company that continues to iterate is more appealing than one that builds a feature set and calls it good.<\/p>\n\n\n\n\n\u201cCustomers (both potential and existing) appreciate feature velocity.\u201d<\/p>\n\n\n\n
– Sarah<\/a><\/p>\n<\/blockquote>\n\n\n\nA roadmap doesn\u2019t just give users insight into how you work (and how long things take). It also shows that you\u2019re continually growing and improving.<\/p>\n\n\n\n
5. It\u2019s easy to keep stakeholders updated<\/h3>\n\n\n\n
The work outlined on your roadmap is probably high-value. It might be a feature that you need to attract a specific type of customer. Or, it\u2019s a fix that will make an existing important user really happy.<\/p>\n\n\n\n
Regardless, you\u2019ve likely got many different stakeholders who care deeply about what you\u2019re working on.<\/p>\n\n\n\n
A public roadmap helps involve everyone. The more you can automate the process<\/a>, the less time you\u2019ll have to spend doing it manually.<\/p>\n\n\n\nWhy does this matter?<\/strong><\/p>\n\n\n\nThis one\u2019s a bit obvious: it saves you time.<\/p>\n\n\n\n
With some roadmaps, users are automatically updated when a roadmap item is moved to the next phase or marked as complete.<\/p>\n\n\n\n
If you\u2019re using a tool like Canny to build your roadmap , you can notify key stakeholders without taking extra steps. They\u2019ll get notified immediately<\/a> with new comments or status changes.<\/p>\n\n\n\nWith Canny, you can update stakeholders about status changes.<\/span><\/figcaption><\/figure>\n\n\n\nThis isn\u2019t just limited to outside stakeholders. Being able to update your internal team is also hugely valuable.<\/p>\n\n\n\n
For example, your sales team might be waiting on a key feature that they know potential customers want. If they\u2019re always looped in, they\u2019ll be able to keep prospects updated on your timeline. And, once the feature is live, they\u2019ll know right away, and close more deals<\/a> as a result.<\/p>\n\n\n\nIf you want to explore this use case in more detail, we\u2019ve written more on the value of internal product roadmaps here<\/a>.<\/p>\n\n\n\nWith Canny, you can also integrate with your existing project management tools<\/a>. This can be incredibly helpful for looping in different members of your team.<\/p>\n\n\n\nFor instance, Canny integrates with Jira<\/a>. With this integration, members of your team who aren\u2019t working on the product can stay updated without having to log into (or even use) Jira. They\u2019ll get the notifications they need automatically from your roadmap updates.<\/p>\n\n\n\nOf course, what you have available depends on the roadmapping tool you use. Tools like Trello, which aren\u2019t really designed for roadmapping<\/a>, won\u2019t have these features built in.<\/p>\n\n\n\n6. It defines the process\u2014from feedback to feature<\/h3>\n\n\n\n
When used in conjunction with a product feedback tool<\/a>, your roadmap is a clear next step that shows how you plan to act on feedback.<\/p>\n\n\n\nWhy does this matter?<\/strong><\/p>\n\n\n\nMaybe you\u2019re using a tool like Canny to collect feedback<\/a> (and of course, we recommend you do). Maybe your product manager manually tracks the feedback you get and your most-requested features (we\u2019ve also covered how to determine if you need a feedback tool<\/a>).<\/p>\n\n\n\nWhatever the case, your users will want to know what you\u2019re doing with their input. Are you actually implementing any of their requests?<\/p>\n\n\n\n
Showing that you are taking feedback seriously, and using it to inform new features or fixes, is huge. It creates a loop. A user suggests a certain feature and can watch as your team works on it. This instills confidence in the feedback request process, and your company itself.<\/p>\n\n\n\n
Leading companies with public roadmaps<\/strong><\/h2>\n\n\n\nPublic roadmaps are incredibly common, especially in the SaaS space. With all the benefits we’ve outlined it’s easy to understand why. <\/p>\n\n\n\n
A public product roadmap is the same, but it shares your product’s journey with the world. It’s a glimpse into what’s happening behind the scenes: upcoming features, bug fixes, and product updates<\/a>. Public roadmaps invite your users into the planning process, fostering a community feel. It’s a living document that communicates the why, what, and when of product initiatives to internal teams, stakeholders, and customers. <\/p>\n\n\n\n This roadmap is open for everyone to see \u2013 users, customers, competitors, and more. <\/p>\n\n\n\n Why does it matter?<\/strong><\/p>\n\n\n\n So, with all these benefits, why wouldn’t you make your roadmap public?<\/p>\n\n\n\n Sometimes the roadmap’s contents aren’t fit to be shared publicly. A few examples could include:<\/p>\n\n\n\n You can probably think of many other examples warranting a private roadmap (aka internal roadmap). <\/p>\n\n\n\n When deciding whether to make your roadmap public, make sure you can tolerate the risks. Also, weigh them against the potential benefits. <\/p>\n\n\n\n Public roadmaps are useful for all types of companies, but critical for SaaS. SaaS customers expect regular feature development. They expect their feedback to be heard. And, they want to know when you work on their feedback and resolve issues. A public roadmap helps you satisfy all those expectations.<\/p>\n\n\n\n Building a public roadmap isn’t much different than building any other roadmap. You just need a way to make it publicly accessible. <\/p>\n\n\n\n Here’s a quick list of things you’ll need to do:<\/p>\n\n\n\n The easiest way is to use a product roadmap tool<\/a> that supports public roadmaps, feedback management, and release notes.<\/p>\n\n\n\n It\u2019s hard to get over the fear that a competitor might look at your public roadmap. And, they might build features exactly like the ones you\u2019re currently working on.<\/p>\n\n\n\n Is it a possibility? Realistically, yes. If you share details of your process, it\u2019s possible that people will try to duplicate what you\u2019re doing well.<\/p>\n\n\n\n But, the benefits of having a public roadmap outweigh this potential con. We\u2019ll get to those benefits shortly.<\/p>\n\n\n\n Ultimately, the issue of idea theft comes down to this:<\/p>\n\n\n\n If competitors are looking to your roadmap for inspiration, that means they\u2019re leaning on your customer base to tell them what to build\u2014not their own. At the end of the day, this will hurt them, not you.<\/p>\n\n\n\n I reached out to Tim Soulo of Ahrefs<\/a> (and Canny customer<\/a>) to get his input. He believes there aren\u2019t any critical downsides to a public-facing roadmap:<\/p>\n\n\n\n \u201cIf our competitors want to focus on what customers request from us instead of what their customers request from them\u2014it’s their choice.\u201d<\/p>\n\n\n\n – Tim<\/p>\n<\/blockquote>\n\n\n With that said, here are 6 reasons why having a public roadmap will benefit you, and help you build a better product.<\/p>\n\n\n\n When you have a public roadmap, you can show your customer base exactly what you\u2019re building.<\/p>\n\n\n\n There\u2019s hardly a better way to be transparent than by showing the world what you\u2019re working on.<\/p>\n\n\n\n Why this matters:<\/strong><\/p>\n\n\n\n Transparency is huge when it comes to driving loyalty. In one survey on the ROI of transparency<\/a>, 94% of consumers said they are likely to be loyal to a brand that is transparent. And, 73% said they\u2019d be willing to pay more to do business with a more transparent company.<\/p>\n\n\n\n We reached out to Tom Redman, head of product at Buffer. Anyone can access the Buffer roadmap<\/a>; For Tom, having a public roadmap aligns with Buffer\u2019s overall culture.<\/p>\n\n\n\n \u201cAt Buffer, we’re \u2018transparent by default.\u2019 That is, if we don’t have a compelling reason for something to be private, it’ll be shared transparently.\u201d<\/p>\n\n\n\n – Tom<\/p>\n<\/blockquote>\n\n\n\n Being upfront and honest with your customers is hugely valuable. Using a roadmap to show how your company actually takes on work is a big deal. You\u2019re giving your customers a look behind the curtain. They\u2019ll value that level of trust and commitment to transparency.<\/p>\n\n\n\n When users can see your roadmap, they can see what your current priorities are. They\u2019ll be able to see product direction and get a sense of your goals.<\/p>\n\n\n\n If you\u2019re working on improving an aspect of your tool, you can show that in your roadmap. If your product doesn\u2019t have a feature, you can show that you\u2019re building it.<\/p>\n\n\n\n And, if you\u2019re not building something, they\u2019ll see that too.<\/p>\n\n\n\n Why does this matter?<\/strong><\/p>\n\n\n\n If you have key planned features in the pipeline, a public roadmap gives potential users a look at what you\u2019re building. It\u2019s added value that your product might not have currently, but will soon.<\/p>\n\n\n\n If a current customer sees active work on a feature they really want, it can prevent churn<\/a>. Similarly, a public-facing roadmap can serve as a sales tool for prospective customers<\/a>. You\u2019ll be able to show that you\u2019re actively working on certain features that they need.<\/p>\n\n\n\n And, on the flip side, it shows if you aren\u2019t working on a feature. Hearing a clear \u201cno, we aren\u2019t working on that right now\u201d is better than not knowing.<\/p>\n\n\n\n “It’s a good way for our customers to see that their feature request is not as popular as they were hoping it would be.”<\/p>\n\n\n\n – Tim<\/p>\n<\/blockquote>\n\n\n\n Public roadmaps put things into perspective. You\u2019ll be able to set expectations for what isn\u2019t going to happen<\/a> as much as what is. This helps keep your users from being disappointed or feeling left in the dark.<\/p>\n\n\n\n This is especially impactful if you\u2019re using a product roadmapping tool like Canny<\/a> with feature voting. If a suggestion has a very limited number of votes, users can better understand why you\u2019ve decided not to add a feature to your roadmap.<\/p>\n\n\n\n When your users can see what you\u2019re working on, there\u2019s less need to reach out with questions.<\/p>\n\n\n\n If you update your roadmap regularly, customers can easily see where you are on a certain feature. They\u2019ll have less need to reach out and ask about progress.<\/p>\n\n\n\n Why does this matter?<\/p>\n\n\n\n You\u2019ll lessen the load on your customer success or customer experience team<\/a>, to start. The fewer customers have to ask about the status of a feature they need, the less time you need to spend updating them. And, those teams won’t have to ask the product team for that info either. <\/p>\n\n\n\n On the flip side, your users won\u2019t have to spend valuable time reaching out to ask questions. Instead, they can just check out your roadmap (you can also update it automatically \u2014 see #5). Eliminating unnecessary hoops to jump through makes for a better customer experience.<\/p>\n\n\n\n \u201c[Transparency] was the primary driver for us to have a public roadmap, but the practical benefit is that we can send customers or others with inquiries there to see what we’re working on, vote for, or even comment on upcoming items on the roadmap.<\/p>\n\n\n\n That’s been very helpful in sharing what our priorities are.\u201d<\/p>\n\n\n\n – Tom<\/p>\n<\/blockquote>\n\n\n\n You might have a very understanding customer base. They might totally get that it takes some time to build, test, and ship updates.<\/p>\n\n\n\n But, you might occasionally have to deal with frustration, too. When we want things, we often want them immediately.<\/p>\n\n\n\n When you have a public roadmap, you can lay out the steps your team takes to get from A to Z.<\/p>\n\n\n\n Users can follow along and see what\u2019s getting done and when. And, they will have a better understanding of how long it will take for new updates or features to be introduced.<\/p>\n\n\n\n Why does this matter?<\/strong><\/p>\n\n\n\n Showing how long things take offers a sense of perspective. It grounds the process. Rather than rolling out improvements seemingly at random, users can see the steps.<\/p>\n\n\n\n You\u2019ll also be able to better manage timeline expectations. A roadmap shows that things are happening, just not overnight.<\/p>\n\n\n Finally, users (and prospects) will appreciate that you\u2019re continually improving (see the conversation above from the SaaS Growth Hacks Facebook group<\/a> for an example). A company that continues to iterate is more appealing than one that builds a feature set and calls it good.<\/p>\n\n\n\n \u201cCustomers (both potential and existing) appreciate feature velocity.\u201d<\/p>\n\n\n\n – Sarah<\/a><\/p>\n<\/blockquote>\n\n\n\n A roadmap doesn\u2019t just give users insight into how you work (and how long things take). It also shows that you\u2019re continually growing and improving.<\/p>\n\n\n\n The work outlined on your roadmap is probably high-value. It might be a feature that you need to attract a specific type of customer. Or, it\u2019s a fix that will make an existing important user really happy.<\/p>\n\n\n\n Regardless, you\u2019ve likely got many different stakeholders who care deeply about what you\u2019re working on.<\/p>\n\n\n\n A public roadmap helps involve everyone. The more you can automate the process<\/a>, the less time you\u2019ll have to spend doing it manually.<\/p>\n\n\n\n Why does this matter?<\/strong><\/p>\n\n\n\n This one\u2019s a bit obvious: it saves you time.<\/p>\n\n\n\n With some roadmaps, users are automatically updated when a roadmap item is moved to the next phase or marked as complete.<\/p>\n\n\n\n If you\u2019re using a tool like Canny to build your roadmap , you can notify key stakeholders without taking extra steps. They\u2019ll get notified immediately<\/a> with new comments or status changes.<\/p>\n\n\n\n This isn\u2019t just limited to outside stakeholders. Being able to update your internal team is also hugely valuable.<\/p>\n\n\n\n For example, your sales team might be waiting on a key feature that they know potential customers want. If they\u2019re always looped in, they\u2019ll be able to keep prospects updated on your timeline. And, once the feature is live, they\u2019ll know right away, and close more deals<\/a> as a result.<\/p>\n\n\n\n If you want to explore this use case in more detail, we\u2019ve written more on the value of internal product roadmaps here<\/a>.<\/p>\n\n\n\n With Canny, you can also integrate with your existing project management tools<\/a>. This can be incredibly helpful for looping in different members of your team.<\/p>\n\n\n\n For instance, Canny integrates with Jira<\/a>. With this integration, members of your team who aren\u2019t working on the product can stay updated without having to log into (or even use) Jira. They\u2019ll get the notifications they need automatically from your roadmap updates.<\/p>\n\n\n\n Of course, what you have available depends on the roadmapping tool you use. Tools like Trello, which aren\u2019t really designed for roadmapping<\/a>, won\u2019t have these features built in.<\/p>\n\n\n\n When used in conjunction with a product feedback tool<\/a>, your roadmap is a clear next step that shows how you plan to act on feedback.<\/p>\n\n\n\n Why does this matter?<\/strong><\/p>\n\n\n\n Maybe you\u2019re using a tool like Canny to collect feedback<\/a> (and of course, we recommend you do). Maybe your product manager manually tracks the feedback you get and your most-requested features (we\u2019ve also covered how to determine if you need a feedback tool<\/a>).<\/p>\n\n\n\n Whatever the case, your users will want to know what you\u2019re doing with their input. Are you actually implementing any of their requests?<\/p>\n\n\n\n Showing that you are taking feedback seriously, and using it to inform new features or fixes, is huge. It creates a loop. A user suggests a certain feature and can watch as your team works on it. This instills confidence in the feedback request process, and your company itself.<\/p>\n\n\n\n Public roadmaps are incredibly common, especially in the SaaS space. With all the benefits we’ve outlined it’s easy to understand why. <\/p>\n\n\n\n\n
\n
Public roadmaps are critical for SaaS companies<\/h3>\n\n\n\n
How do I build a public roadmap?<\/h3>\n\n\n\n
\n
If I have a public product roadmap, will competitors steal my ideas?<\/h2>\n\n\n\n
\n
![\"Ahrefs](\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/04\/Ahrefs-roadmap.png\")
6 reasons why you should have a public product roadmap<\/h2>\n\n\n\n
1. It offers transparency<\/h3>\n\n\n\n
\n
![\"Buffer\u2019s](\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/04\/Buffer-roadmap.png\")
2. It manages expectations for what you\u2019re building (and not building)<\/h3>\n\n\n\n
\n
3. It cuts down on questions<\/h3>\n\n\n\n
\n
4. It shows how long things really take<\/h3>\n\n\n\n
![\"Conversation](\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/04\/facebook-clickup.jpg\")
<\/figure>\n<\/div>\n\n\n\n
5. It\u2019s easy to keep stakeholders updated<\/h3>\n\n\n\n
![\"Notification](\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/04\/Notification.png\")
6. It defines the process\u2014from feedback to feature<\/h3>\n\n\n\n
Leading companies with public roadmaps<\/strong><\/h2>\n\n\n\n
![\"should](\"https:\/\/canny.io\/blog\/wp-content\/uploads\/2020\/04\/public-roadmap-helps.jpg\")
<\/figure>\n<\/div>\n\n\n![\"Canny](\"https:\/\/no-cache.hubspot.com\/cta\/default\/5705808\/e1d55d08-a2cf-44a3-a9a0-f3ca5ff21dfa.png\")
<\/a><\/figure>\n<\/div>\n\n\n