Productboard Reviews

So easy to record feedback through email, chrome, intercom, slack and many more integrations
Easy to use inbox for running through this feedback and matching it up with your roadmap
The look and feel of the site is excellent
Customer support is quick and very helpful
Excellent community including a slack channel with helpful tips, articles etc.
Portal is an excellent idea and great for engaging users and displaying the roadmap to prospective enterprise customers

I have been a customer for a while now and have had issues sharing the roadmap view with CEO/Investors etc. and it is still not perfect but I can see where improvements are being made to work towards this.

Product board is an easily-navigable single source of truth for all product ideas along with a single source for all product feedback. Saves so much time and hassle for product managers whilst bringing together all stakeholders from around the business.

Can't really think of anything to be honest.

Capturing feedback from external sources, prioritisation against company goals & objectives

Unfortunately, there is almost no reporting available. So although I can prioritise against company objectives, it is nearly impossible to report back on how much time and resource is allocated. I don't know how long features take to get released. Or to move from Long-term to short-term etc. I can't therefore set any metrics around speed of development, and can't report back to the board on where resources are being allocated. This makes the product useful for only half of my role.

A great way to communicate and negotiate your roadmap with stakeholders. Ability to tie direct feedback from users to specific features.

Would love more out-of-the-box integrations with work ticket tracking tools (we use Clubhouse). Also would love a free single-user level that let me experiment with ideas before I bring new people in.

It has a good deal of flexibility and is easy to grasp.

It is not really meant for multiple teams. I am having a hard time figuring out how to manage several dev teams and their unique assignments and backlog.

I love being able to see accurate customer data in relation to feature requests.

The flow from feature list to roadmap is clunky

I like that it gives you a lot of options as a product manager. Much better than to use spreadsheets. It's a great tool for conducting your work as a PM.

In certain areas, I think I would like to have a bit more flexibility in editing certain things.

The best feature to call out is the flexibility and robust capabilities provided for being able to quantitatively prioritize the features.

Of all the features, the least useful so far has been the road mapping capabilities. It's been challenging for us to shape our features and various data elements in a way that easily allows us to generate Roadmaps for our various audiences.

The Productboard has a beautiful interface design and is very easy to use. We can easily plan product roadmaps from general to the finest details.

Prioritization scores of product features are calculated automatically according to different parameters. Thus, we can clearly see which feature we should develop first.

User feedback and tools for collecting new ideas are also outdated and very useful. We can also include our users in our product development processes.

Using the Productboard first time it should be confusing to make a setup according to your needs, but when the system understood everything gets clear and runs smoothly.
Although it has very different layouts, you may not be able to create a layout for your specific needs.

As a CEO of an early stage company, I wear a lot of hats. I had to find a way to create really clear roadmaps for the team and change them as we itterate that was visual, easy an most importantly, fast. Productboard was everything I was looking for and so much more.

- The UI looks fantastic.
- There are views for every kind of roadmap discussion, whether that's sprints, waterfall, high level, releases. However you run development or create roadmaps, there's a view that supports the context of that conversation.
- Once you get an understanding of how it works, adding features and prioritizing/categorizing them is a breeze.
- The tools for prioritization and impact scoring are super easy and helpful.
- If you're like me and are a bit new to product management, the tool will actually make you better at your job and help you show up for the product team with the types of clear, visual roadmaps they need to get on board with vision.

I had a tiny bit of trouble getting a hang of the UI the first few hours. Which was frustrating at first, then I watched a few tutorials, got the hang of it, and was off to the races. Ultimately that's pretty good for a product that is as robust as this one. But do yourself a favor and watch some tutorials before you try to create your first roadmap.

The ability to link customer insights directly to the different pains and feature requests. Before Productboard much of the insights we had to go on when designing/developing solutions would be anecdotal evidence from the commercial team or the few interviews we could do with select customers. Now we have the ability to see customers' own words about their requests before we start building, without a huge effort to dig through various conversations in Intercom or our CRM.

An easy example was when I recently got a new PM joining my team. I pointed out a few of the requests that we're coming up a lot and asked him to do scoping + initial estimation on what the feature would require. Using the customer insights he could make a detailed description of the problem we needed to solve and how we could go about it. Another benefit is the more quantitative view of the most requested things, however the visualization of this is not great as I'd like to be able to better track and visualize the change in requests over time.

Last but not least it's good to help project manage the work of the PM team as we can more easily track the stages that a feature or pain is in and what more scoping we need to do before we involve other stakeholders from the product team.

There are some great missing pieces that would hugely improve the product, such as a CRM integrations, an API and a proper Zapier integration (in lack of the first two). Right now Productboard is valuable in itself, but it would extend the value so much further if we could properly link it to our other systems.

helps with roadmapping and input management. Help me organize, explain my priorities, and share internally.
They are also an example of how product mgmt should be - from new features, communication of value, ux and more

Slightly hard to get started. Might create duplications with Jira and other tool. Great for PMs but not always for the rest of the team

I'm amazed by productboard UX that is totally covering the needs of PMs. And, eventually, the needs of the users. We can easily track all the insights and convert them to features. Amazing customer service btw.

Hm..have nothing bad to say about it. I'm using it around a year now and have never experienced any issue.

Beautifully designed. Easy to get started and learn, yet lot's of depth to the features. So hard to single out things I like the most because almost everything is top notch and a delight. One very useful thing is how it maintains a link between features and the customer input/feedback linked to those features so the team can look back at the genesis of an idea and understand the full context. A superb little touch is a one click export of email addresses for everyone whose input is linked to a feature so you can reach out to them quickly to ask for more input, or let them know that their requested feature is available.

There are a couple of tweaks I'd love to make to help with workflow: allow contributors to add/suggest tags and changes to fields like Effort, and allow them to adjust/customize their own views of the feature board. I don't want to make them full-fledged editors, because I don't want them to be able to edit other fields. An alternative would be to grant more granular access control to editors so that you can prevent them from making certain changes; or at least to require the product manager's approval after suggesting changes.

The ability to consume many sources of user feedback and the portal is really just icing on the cake. We did not hire this tool for that job but did have a need for one so that was nice.

Prioritization features are a bit much for our needs.

Higher level planning of product features with details in Jira. Ability to link stages (e.g. Design, Dev) to their individual Jira Epics. Communication of Roadmap and easier prioritization and capacity planning. Link customer feedback to Features.
Great and responsive customer support when it's needed.

Somewhat high price per admin user. We'd add more users at a different price point.

First of all productboard does have a clear and intuitive UI.
Things are arranged clearly and are easily found once the overall concept is clear.
Productboard does give different filterable views on a given set of data on timelines and as a list.
It does help with priorization by objectivizing mere words into numbers, also collecting ideas and insights.

On the downside of the product is the subscription model.
The so called "pro" licence does not include basic things like visible dependencies on the roadmap or using the strongly advertised "objectives" on features.
Only two of the four plans are available directly, the rest needs to be negotiated.
That negotiation revealed that the "scale model" would multiply the price and the contact itself was so unpleasant that the whole product became stale for our team.

We are using productboard to collaborate with our product team. It's an amazing tool you can use to give and share feedback. You can integrate it with many other tool like Slack to push things forward. They also use it to share the product map with us. We are able to see in a form of a timeline, what's under key development right now and where it's going. We can see and view priorities together.

The integration lists is quite short, though as for us we mainly add it to Slack for the Customer Support team. It comes in super handy to share feedback and have it fall in the right "product" category.

Productboard allows me to easily understand, organize, and bucket feature requests and feedback items from our customers. As a Support Leader, it's crucial to understand where our customers are running into hiccups or what features they wish they had. Productboard allows our organization to gather insights and analyze trends based on all these customer asks. It also has a great integration with Intercom, which allows our support team to seamlessly share product feedback in a customer interaction with our Product team to process.

Productboard's UI and organizational structure makes it a bit difficult to understand who specifically gave you the feedback. It's a manual process to export users' insights so that our support team can follow through on customer feedback once we've delivered on their asks. I wish it was a bit more seamless to close these feedback loops, since it does do a strong job at keeping everything organized.

The ability to organize and prioritize my product roadmap and its features with a great deal of customization and granularity. Product Board has been instrumental in achieving our business goals and detail our product roadmap every step of the way.

The cost per user is a bit high. Still has to work some UI issues that are detrimental to user experience.

It is really easy to use and navigate around. When I was first introduced to this, it took me no time to pick it up and get used to everything on the platform. It's so great at organizing. Would not know what to do without this!

I have been using this for 7 months now and I don't have a single thing that I can think of that I don't like about it.

Handles and automates the flow of data from customers to features to roadmap planning.

Would be great to use for planning what the team is working on on a weekly basis.

- All the tools you would want as a product manager (user research collection, prioritization, feedback dashboards).
- Fantastic UX that's very simple to use.
- Great scoring mechanisms
- Integrations are getting stronger!

I've been a long time user so most of the things I liked least are start to/have been fixed. I can't think of anything off the top of my head that I like the least?

Perhaps having more browser based extensions for users to submit feedback? Currently limited to Chrome.

Love the features board where I can see and view all insights. Love the addition of being able to communicate with customers.

Lack of API
Lack of automations
Lack of reporting.

We've used PB on and off for several years. It's promise is great - keeping track of requests, features, and requirements is an incredible need on complex builds, and JIRA is a nightmare for that. But PB only delivers partially on that promise.

I want to like this product, but it seems to copy so much from Jira that it becomes a second silo of features and requirements. And we already have Jira for that. The timeline and forecasting tools are weak and inflexible, the UI is sufficiently complex as to be unusable by team members that don't use it daily (making collaboration harder, just like Jira). We eventually churned and returned to spreadsheets, it wasn't as collaborative as hoped, and not as necessary as Jira.