Productboard has singlehandedly organized our feedback loops and our roadmap communication to our users. Productboard is very frictionless to submit feedback and our Product team is able to very easily organize and communicate what our user needs are. Prior to Productboard, we used several Google sheets and Jira boards to organize feedback and report on it quantitatively. You can imagine the disorganization and work required to maintain those documents. Productboard has also given our Product team better ways to democratize information to internal team members and customers alike. We love sharing what we're working on and Productboard gives us many ways to do that. Review collected by and hosted on G2.com.

Roadmaps. Roadmaps are a critical deliverable for the Product team. It's important to have a clean and informative roadmap, but it's also important to distribute and share that roadmap. This is where Productboard really suffers. I can create an organized roadmap that demonstrates what each of our engineering teams is working on now, what's upcoming, and what's under consideration. However, I have to screenshot the Productboard UI in order to disseminate that roadmap. Many other product tools (Productboard competitors) offer shareable URLs to share roadmaps and this is a hugely important feature that Productboard is missing. It almost makes me want to leave Productboard, but they're truly innovating, have LOTS of cash, and positioned to be the defacto tool for Product Managers. It's also painfully easy for my team to use so it would cause some internal heartburn if we decided to leave. Review collected by and hosted on G2.com.

It's very helpful for organizing large teams across a massive feature-set. Good for communicating status across departments. Review collected by and hosted on G2.com.

It's very open-ended as to style which is both a pro and a con. Teams vary with how they approach populating data which leads to some collisions. Review collected by and hosted on G2.com.

Productboard joins customer feedback with a long-term roadmap. In a rapidly changing startup environment, that's essential.

You can finally ditch the Excel spreadsheets, Slack messages and stop saying "I think that this is valuable to customers...".

By creating a relationship between feedback and features, you finally knows what features will create the most value at a glance, making for an easy priorization.

It is easy to share and collaborate together on roadmaps, and by building your views your own way, you have a lot of leeway as a power user.

Support has also been very helpful and attentive. Review collected by and hosted on G2.com.

Productboard works best when it has integrations with your development tool of choice. Right now we use Clubhouse, and the integration is currently in development. This results in some manual work and fragmentation.

It has a learning curve, but Productboard's learning materials and workshops are good. Maybe some ready-to-use templates for a basic Agile methodology would work wonders here.

Bug support could be a little better. It feels a little bolted on right now. As bugs are an integral part of the customer experience and directly affects the roadmap (if you have a policy of fixing bugs before working on new features), I think some built-in support would be better. Review collected by and hosted on G2.com.

Being able to sort and organize the huge amount of insights that we have coming in from various sources. Review collected by and hosted on G2.com.

It's clear the company is very focused on delivering roadmapping features which is a dying art. Most progressive product companies are less focused on roadmaps and prioritization formulas and more focused on looking at the learnings they are constantly getting from customers, and organizing those identified opportunities. A roadmap is only as good as your current knowledge and assumes that you will learn nothing from that point on. Having more flexible organization tools and ways to display current opportunities would be helpful. Also the segmentation is so frustrating!! We would love to have company information in there and be able to filter and sort the insights based on that, but its so frustrating that it is only based off of email domains--we'd like to import this information or have it imported from an integration. Also the user segmentation is so useless! What's the point of even using tags if you can't dynamically sort by them! Review collected by and hosted on G2.com.

I like how easy it is to create new features and subfeatures. The additional information that you can add into a feature is also very useful. It's also nice how it integrates with Jira to allow you to push features and subfeautres as Epics and User Stories. I also like the ability to gather input from external sources that allows you to better write out requirements Review collected by and hosted on G2.com.

It seems at times very difficult to navigate between views (so from features/subfeatures board to roadmaps). Visibility for others is also some times difficult. Getting features to appear on the roadmap also is confusing at first but figured it out over time. I think the ability to add more detail to the roadmap view would help. Also adding additional swimlanes, or breaking out features into different swimlanes was either not possible as I would want it, or required some manual changes. Review collected by and hosted on G2.com.

It is built by folks that understand Product Management well. In other words, it is a tool made by PMs for PMs. What could go wrong, right? Review collected by and hosted on G2.com.

Nothing really at this point. The initial setup might be complex, depending on the structure of your team and how you use it—otherwise, all good. Review collected by and hosted on G2.com.

When we adopted ProductBoard we were looking for a tool that would allow us to organize our products into clear buckets of value and tie that back to various views for managing engineering, stakeholder communication, and our own research and discovery processes.

So far (it's been about 6months), we've effectively managed the project management bits of execution with eng to keep status well represented and keep iterating on the key movers ie. design/requirements/UAT, etc.

We've also leveraged Portal as a way to keep stakeholders at bay and as a resource for all completed features to contain release notes, demo videos, etc.

The tool is incredibly powerful given the right amount of time to experiment with various setups. The flexibility forces you to think about the organization of your products which produces clarity, ie. you have a lot of freedom to group and work by releases, objectives, etc and being able to truly think about your objectives against the broader product organization forces good thinking time about the product vs simply chasing the next "task". This has helped instill good habits in our more JR PMs. Review collected by and hosted on G2.com.

I wish there were better ways to organize features not just by hierarchy but almost by versions of similar products we want to produce. We are a B2B SASS that tends to need to iterate more on our customer's cycles for our big bang stuff, and don't leverage similar patterns to your heavy A/B B2C product tendencies. There are ways to achieve this but versioning/treating PB as a true repository of the products is hard to get a good visual of. Maybe something that mindmaps features to allow your product to be visually represented as relationships / nested articles would be helpful as a complement to the hierarchy view.

More concrete ask... I wish could nest multiple groupings much like Airtable. I sometimes want to see a release + objectives or teams within vs having very long lists by release or needing to break out various releases for various teams. Right now the 1 level of grouping in non-hierarchy views is a bit painful for us.

Lastly, I wish there were better ways to capture feedback / organize feedback. This includes having not only the feedback repository but a way to see key clients and all feedback grouped into that key client + roadmapped items in progress aligned with their needs to assist in any areas where we need to help manage a relationship. All this research is hard to put together. Review collected by and hosted on G2.com.

I love how simple they have made the macro-level workflows with the four key buckets Insights, Features, Roadmaps, and Portal. I feel we, as product leaders, can easily fall into the trap of complicating our workflows due to the sheer volume and complexity of our product. ProductBoard has become my favorite way of getting to what truly matters quickly and efficiently. I have found that ProductBoard has help me develop some very disciplined habits. Also, one additional favorite of mine is the objective based timelines within Roadmaps. Stakeholders do not want to spend a bunch of time looking over all the various features, but rather, would prefer to understand what you are trying to achieve on the macro levels. ProductBoard has allowed me to clearly state, through Objectives, what my intent is on a roadmap. Being able to get buy-in with stakeholders easily makes this tool worth every dollar. Review collected by and hosted on G2.com.

The process of connecting highlighted notes within Insights to a feature from the Insights window is a bit tedious. After highlighting, the window for selecting a feature is too small and only allows me to create a single feature at a time. Having the ability to create multiple features for a highlighted insight without closing the window could add some value. I believe this would allow me the ability to formulate quick thoughts around a full set of features quickly and not slow down my workflow. Review collected by and hosted on G2.com.

Productboard has an easy-to-use interface with a flexible model that allows us to track various inputs on each of our feature requests and planned components. This makes it easy to compare and evaluate features for upcoming development. Finally, Productboard easily integrates with our development tool (JIRA) to communicate across teams. Review collected by and hosted on G2.com.

The primary method of capturing customer input (insights) does not link to the process of evaluating potential features in the features section, requiring this tracking to be performed manually. This limits our ability to tie our development directly to user input.

Further, the relatively high cost of the per-user pricing model limits accessibility for various stakeholders to provide a simple scoring input on the features as part of the evaluation, limiting collaboration within the tool. Review collected by and hosted on G2.com.

I love being able to collect all related feedback, issues, recommendations, etc against features or even just components. It's best if you structure your features in a jobs-to-be-done framework so even if you don't have a solution planned you can group the problems to solve. We're able to link Slack comments, notes from meetings, notes from customer interviews, support tickets, emails, etc all on a feature. This helps to see what is getting the most attention but also when scoping you don't miss a scenario Review collected by and hosted on G2.com.

The road mapping tools are continuously improving but there need to be some improvements on summing effort from sub-features to features. Additionally, it would be helpful if we could set planned "capacity" so the roadmap could help us group or alert if we're overcommitted

A great improvement for Portal would be a way for users to see what others have listed for insights and vote so we don't have to manually group common feedback Review collected by and hosted on G2.com.