Productboard Reviews

Pros

The workflow management because it helps to minimize risks and eliminating repetitive tasks.

Cons

The least option I liked about productboard was the collaboration tools.

Pros

1. Feedback management: we have found productboard's integration with intercom to be wonderful. They really nailed it with 95% of the features in Notes, especially for individual feedback. 2. love the diasctintion between maker and (free) viewers. This allowed us to roll out the tool to the entire company without incurring excessive costs. 3. We really like the portal feature but we are not using it yet.

Cons

1. Feature hierarchy is a difficult concept to grasp for new comers and gets messy. What I hate about the feature hiearachy is that there's not flexibility once you have listed something as a "product". You can't change it to a feature of a subfeature. This rendered us with a ginormous "product" with all features listed under one thing. integrations: 2. integration with any development platform that's not jira is completely useless. We use shortcut and we understand it's a small player and it's also fault on their part but the integration is utterly meaningless with the current state. We 3. Integration with zapier is also close to being useless given that the only trigger is "new note" or "new feature", and anything that's imported from an integration to be a new note is not editable. Why??? We would love to automate our workflow and centralize all research findings in productboard but these pain points are impossible to overcome. We are thinking about switching to something else just because of this. Honestly, if they just give us the option of another trigger event on zapier like change of status, we would already be so happy. 4. The research insights are only very qualitative focus and possibility for automation is low. It's funny that productboard owns satismeter but the satismeter integration is also not great. We ended up setting up our own satismeter integration through zapier. But, there's also no way for us to easily sort through low/high ratings or filter.

Alternatives Considered

ProductPlan

Reasons for Switching to Productboard

Feedback management, viewer option, and general usability is a bit better

Pros

- Logging in with SSO integration was easy.- You can use it to capture product feedback, even though there are much better tools out there.- Integrates with Zendesk

Cons

Where to begin???- 3 different search boxes, no unified search.There's one search for views, one search for notes, and another for topics that notes are about.This makes it slow, and difficult to know what search to use at what time.- Data is unstructuredAs far as I can tell, notes don't seem to have ability to have custom fields. Leads to ton of unstructured and poorly searchable data.- The user interfaceThere's no hierarchy to data. The UI/views are overwhelming, and feel disorganized. It's like the worst email inbox or notes app imaginable for complex feedback + data.- Votes on product feedback populate as distinct notes Makes the already bad search even harder to use

Pros

Integration with other tools has been a great benefit. However, the collaboration, prioritisation and visualization of the product roadmap is the best and most used features.

Cons

For smaller teams / startups it could be seen as relatively expensive.

Pros

In order of benefit, here's what I like most so far about Productboard:

(1) Aggregating product insights / customer requirements across all of our inboxes + Slack into one place
(2) Ability to build a quarterly roadmap w/ existing tickets in Jira + w/ ability to write new features back to Jira as tickets
(3) Ability to outline all of the components of our platform w/ features under each component - something we've never had before.

Cons

Some small nit-picks around interactions (eg. bulk selecting rows), but so far customer support has responded instantly to guide me in right direction.

Alternatives Considered

ProductPlan and ProdPad

Reasons for Choosing Productboard

After trying many other solutions we resorted back to spreadsheets. Ultimately, it becomes managed chaos in spreadsheets, so we knew we needed something to fit our growing team. We went back to demoing solutions and productboard fit our needs best.

Reasons for Switching to Productboard

See above. All were good, but productboard wound up fitting our specific needs the best. The quick support during our trial period helped seal the deal.

Pros

Consolidating insights from myself, our customers, and our team. I also really like the different views I can create and ways I can prioritize things by release and various scores. The public feedback forum is also really, really nice. Then the beautiful roadmap view is just icing on the cake.

Cons

Doesn't integrate to Clubhouse, which we are moving to from JIRA. We also didn't use the JIRA integration because we were on New JIRA. Which is why we are now on Clubhouse, which I'll save for another review. Also, I feel there are a couple of elements missing when looking at reporting and ongoing maintenance of tickets... but that's hard, and is probably something they're thinking about.

Alternatives Considered

Aha!

Reasons for Choosing Productboard

Well, JIRA isn't really a great tool for roadmap planning and prioritization. So the reality is that we _needed_ to do more strategic product planning, and JIRA didn't cut it.

Switched From

Jira

Reasons for Switching to Productboard

Aha! was simply just too much software for what we needed. productboard gave us exactly what we needed at our stage, and was more intuitive to pick up and get going.

Pros

We can channel Slack messages, support tickets and input from across all our teams to one central location.

Cons

The reporting is very customisable and you can reach in and grab data quite easily, the only limitation we found is between customer insights and their assigned customer segment, for example, an option to present the priority of feature requests over an entire customer segment isn't readily available.

Alternatives Considered

ProductPlan

Reasons for Switching to Productboard

Our primary goal wasn't to make a Road Map out of a collection of customer insights but commit to maintaining the insights we receive and calling upon the data we can gather when planning development. Productboard did seem to be the slickest for managing insights, processing details and linking to other platforms e.g. Trello, JIRA and Slack

Pros

Love the roadmapping and the ability to assign releases, and status's and organize your product as you like, extremely flexible and useful tool

Cons

The way it sometimes integrates with other tools and updates the formatting of text, and the inability to correctly format words when pasting from a microsoft word document into the Productboard

Pros

- ability to gather, tag and process insights from both clients and internal staff
- semi automatic prioritization
- ability to create public roadmaps for clients without duplicating the inputs for them (however this is tricky, as it requires from you to keep internal notes very clean and "client ready")
- well working integration with jira (two way sync)

Cons

- To use it properly you must work using objectives, which for some features may be tricky
- the features dependencies are limited to "blocks / is blocked", misses quite important one "shall be developed in parallel with"
- jira integration is not visible from jira (when I browse jira project I don't know that certain task was linked with productboard)

Pros

I see the sharing speed of products as an effective application in terms of reaching the market and a very efficient application in terms of reaching people in real need more quickly.

Cons

We are having trouble using the application multiple times and not being able to progress this application synchronously with my colleagues.

Pros

It is intuitive and a great solution to manage product roadmap,.

Cons

It is not always easy to see the dependencies and for that reason gets difficult buy in from engineering.

Pros

As PMs know, the key is getting lots of insights then filtering down into the ones that bring about actual value. Productboard enables everyone in the company to contribute ideas and insights. Once PMs have done prioritization, they can visualize the plan in multiple dynamic roadmap dashboards. Overall this works well as a product-focused tool which can also integrate with other systems.

Cons

Feature-wise it's still a bit sparse. From an insight perspective, it would be nice to add constraints or templates to help structure the feedback. This would help when pruning the backlog of items.

Pros

The best part about productboard is how teams can vet and plan improvements to their products based on how much those improvements support and achieve a company's objectives. It's so easy to get things in, annotated, and shaped that you actually do it; you don't just say you will eventually.

To start, you can use just the parts that are the most important to get up and running, and then you can use more of it as your team begins to integrate productboard into their process. And it's not hard work to get your ideas and backlog in and move forward—it's cathartic.

Cons

The biggest thing for me is performance. Sometimes some parts of the UI feel a little sluggish when lots of items are displayed and clicks get delayed. It would also be a little nicer to have the Drivers feature available at the lowest level of pricing.

Pros

Productboard is an amazing tool. It permits our team to stay in touch with the product team and give feedback. It also also allows us to track down where they are at in terms of development of the product itself. Another thing is that, you can link it to external software like Slack to give direct feedback and "push" things to product board. Product team also have a roadmap of important and not so important things they work on, we can based on that give our point of viw and help them set priorities.

Cons

This tool isn't essential for all the tools IF the product team doesn't teach others how to use it. Once everyone understand how valuable of a tool it is, it's hard to use something else.

Pros

Productboard is a very intuitive tool for our Product Management that allows us to track the features from the insights we gather to the delivery. The shareable roadmap is essential for the communication to other services (R&D, sales, support…) and the UI makes it easy to use and to understand.

Cons

The integration list has to grow to be able to synchronize the items with external project management softwares like Notion. Also, a better version of the Portal to be able to follow the insights would be appreciated.

Pros

The inbox for insights, the way to handle all problems and features and then align that to roadmap views to give visibility to the company

Cons

Lack of flexibility in building the prioritization score

Pros

Productboard is an excellent tool to help you make sure your roadmap is driven by real user feedback and value to your customers.

Cons

Productboard is a fairly young company and is still building out some "no brainer" features, but they also release fantastic updates often!

Alternatives Considered

Jira, ProductPlan and Aha!

Pros

A product management service should be designed, right? Not always but product board does a good job of making it easy for the entire org to capture and share insights. The 'inbox' is where the majority of these get funneled. Insights can have labels associated with them so you can implement all types of filtering and prioritization. The product roadmaps are well-designed and are dynamic to adjust for the necessary audience.

Cons

Interestingly, I received feedback that the onboarding for non-PMs was a bit challenging. Team members weren't quite sure how to use the tool to provide feedback. The inbox can get quite cluttered and it's best to educate team members on how to submit ideas.

Pros

- 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!

Cons

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.

Pros

I love that with Productboard you can collect all the customer feedback easily and customize it according to your needs. Thanks to this, it's easy to see what should be implemented first and which requests can wait

Cons

It can be a bit overwhelming at the beginning as it has a lot of different functionalities. However, [SENSITIVE CONTENT HIDDEN] was amazing on the calls and explained to us how everything works.

Alternatives Considered

ProdPad

Reasons for Choosing Productboard

Price, UX of the tool, integrations

Switched From

ProdPad

Pros

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

Cons

Lack of API
Lack of automations
Lack of reporting.

Pros

- central location for gathering all your product feedback from several locations
- easy collaboration with a team (e.g. comments)
- data driven decision support (e.g. user impact score, driver impact)
- roadmap preparation capabilities

Cons

There are definitely minor thing to improve, but nothing that would prevent us from using the tool efficiently. Really, we love using Product Board on a daily basis.

Pros

It's very easy to use for both a user and from a client standpoint. I'm on our biz dev team and based on conversations we have, we add needs or gaps to the feature roadmap. Very easy to add notes directly within or to send emails to a specified address that automatically adds them into productboard.

Cons

A little cumbersome when searching for content. I will search for items that I know are in the board and no results come up. I'm sure it's just a semantics issue most of the time though!

Pros

Easy to hack and smash without corrupting data. Linkage between other systems that doesn't get in the way. Different views for managing tactical & presenting strategic (using the same set of data). It doesn't look or behave like Jira or Aha! (I feel like your designers must scrutinize everything).

Cons

I'm not sure there's anything bad to say

Pros

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.

Cons

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