productboard vs. Zenhub

The best feature of productboard is organized features, it has a very simple structure and can be read and understood by anyone. If your roadmap is very dynamic and the executive team needs to be on top of it, productboard is the best application out there. But if you have a small product and features do not change very often, then maybe you can look at other alternatives since productboard is expensive.

Incentivized

Zenhub is incredible for the below areas: Burndown Charts, Release Reports, Velocity Tracking, Control Points Charts, Cumulative Flow Diagrams And if there is a bottleneck in your workflow, ZenHub identifies it. The most important aspect is serving as a collaboration tool for areas that are impeding implementation projects. For example when working with non-standard ERPs and having to document ERP integrations this tool is very helpful

Incentivized

• Flexibility - organize your products and features in any way you like
• Input - give your teams a way to make suggestions and provide feedback
• Integrations

Incentivized

• ZenHub continually adds to its reporting suite-- that truly allows you to track forward motion and see what issues may be the cause of any delays.
• Both our technical and non-technical staff can understand and use the functionality.
• We like the flexibility of being able to provide labels to our stories that can be customized to the way our company does things--- such as knowing if an epic is part of a module or a stream.
• We also like the flexibility of the number and labeling of the pipelines--- again, very adaptable to our organization.
• The filtering is very useful--- with and/or conditions, and allows people on different projects, doing different functions, an easy way to view what is important to them.

Incentivized

• The interface could be improved
• Input field options could be less restrictive to the capture of data
• Better notifications / updates on where insights have got to

Incentivized

• Sometimes, updates to a GitHub project can get lost if they're made through ZenHub. You do need to open the GitHub project occasionally, as you don't have exactly the same ability to modify issues and milestones from within ZenHub.
• It's great to be able to see your projects from within ZenHub, but sometimes you'll need to check in on the GitHub project itself, as well.
• I've run into some problems with updates getting lost on occasion. I think this happens when you do the update from within ZenHub instead of from GitHub itself. I also don't have quite as much control over my issues or milestones from within ZenHub.

Incentivized

Once it's up and running it's easy to use. It needs a little consideration to get set up perfectly for your own needs, but that is the same for any feature-rich software.

Incentivized

Easy to contact right through their Intercom app and incredibly fast to respond.

Incentivized

Support is good, but quite honestly, I haven't needed any support since 2015. As I remember, I was required to open a ticket and had to wait a few days for resolution. I give it a rating of 8 because of the lag in getting a solid resolution, but it was resolved adequately.

Incentivized

I have previously used Aha another product road mapping/ insights driven software. Aha had great features for the userbase of my previous products. They were allowed to create their own suggestions for the products and other users could then like or dislike the suggestion. This created a real reflection on need for product enhancements. productboard handles this slightly differently. Each user creates their own suggestions and doesn't necessarily have visibility on other users suggestions. The product/ R&D team can then tag suggestions together into the same overall suggestion. This requires more input from product/R&D with productboard. I would however, suggest that productboard is better than Aha. Aha is great for an external user point of view; however, there may be case for users to not have visibility on wider user requirements. productboard keeps more of this element hidden and would perhaps stir up less negative correlation to seeing a system requirement/suggest having had a lot of traffic and no action, compared to a more closed system that would individually update each user on the enhancement progress.

Incentivized

Way better than competition if you use github because it seamlessly integrates without doing anything. You don't need to duplicate your issues, etc. As long as your devs already use github and github issues this will be a no brainer and simple to implement. With JIRA or Trello we were doing everything twice, things got dropped, etc.

Incentivized

• Helps to save us a lot of time collecting feedback.
• Increased efficiency.
• Product prioritization can be done in a faster and more robust way.

Incentivized

• We are now able to determine output potential from our development resources based on points assignment.
• We were able to successfully implement an Agile methodology in our department.
• We have been able to better track tasks.
• We have used the releases feature to group our task to business release expections and easily filter.

Incentivized