Productboard

My main use cases for Productboard are numerous, but road mapping and presentations are the top two.

A specific example of how I use Productboard for road mapping is that we have many internal roadmaps, and we want to have a unique source of view for organizing different products and roadmaps where internal and external stakeholders can contribute. We have the possibility to have a cabin board that is objective-based and so on.

I have many product use cases for Productboard. Prioritization insights are another important one, but road mapping is the most important.

Productboard has impacted my organization, but I would say the impacts are quite weak. From a business perspective, we did not really see much positive effect from Productboard. The product is sometimes very slow and performance is an imitation compared with competitors' products.

The best features Productboard offers are the insights along with the possibility to have the impacts. Frameworks where you can see what the impact of the feature is from a business value perspective with effort into value are among the most useful use cases.

The insights and impact frameworks help my team significantly because we have many customers who write to us about what they would like in our product. It is a way to communicate and have a standardized process to get feedback from customers.

I would like to add features such as integration with Jira and other similar tools. Integration is important.

Productboard can be improved in several areas. There is potential for better AI integration, stronger integration with Jira and the direction product, stronger integration with all engineering tools, improved scalability, and more comprehensive prioritization models.

I would appreciate improvements regarding user experience and support. User experience is tricky and sometimes slow, and there are no benefits for Teams. It should be much better for stakeholder communication and the UX for Teams should be simplified, especially for sales. Regarding Productboard's AI capabilities, governance and security are quite modest, and I do not see any signs in the accuracy and reliability of output.

I have been using Productboard since eighteen months.

Productboard is stable, more or less.

Scalability is very low with Productboard.

I would rate Productboard's customer support as seven out of ten.

I previously used different solutions before Productboard. I used another solution, Jira, and Craft. We also used Notion, with which we were not happy, but we were more happy than we are now.

I have not seen a return on investment with Productboard. It still creates confusion in the sales and PM teams, so I did not see any return.

My experience with Productboard's pricing, setup cost, and licensing is that you contact their sales teams directly as they approach you. The price is standard and average, nothing exceptionally good or expensive. We have quite a few people using it, more than two hundred or three hundred seats, I guess.

Before choosing Productboard, I did evaluate more than twenty-five other options.

The advice I would give to others looking into using Productboard is that for a really small team, it is still adequate and not bad. However, if you have many teams across different geographies with big roadmaps, many partners, and many people, the situation changes. I rated this review as five out of ten.

At Megaport, I use Productboard to build a roadmap of all the initiatives, projects, and features the team is working on. This includes the front end of the roadmap showing what is in the backlog and all the things that could potentially be worked on by the development and product team, then the actual roadmap, and timelines on delivery.

Productboard has a feature that I love where you can create tiles that serve as summaries. In this case, I created a summary of potential markets that Megaport was going to enter, including Stockholm, Miami, Copenhagen, and São Paulo. The valuable aspect of Productboard is that you can share these tiles with customers and ask them to vote on them and comment on them. This was invaluable in determining where Megaport should launch next. We decided to go into Stockholm and Miami because the customer feedback was overwhelming for those two markets.

I built the roadmap of all the initiatives in flight, including all project initiatives and features that the development team and product leaders were working on. For each initiative, I developed a summary describing what we were trying to do, the business value, and how this would impact customers. This roadmap was available and used by all internal stakeholders across engineering, product, and sales, serving as the definitive source for what was in flight and when it would be coming. Productboard is really good for this purpose.

The ability to expose potential work through tiles and share those ideas with customers to get their feedback is a valuable feature. I also appreciate Productboard's roadmap capability where you can build the roadmap and tag different items such as projects, initiatives, and features with different criteria. You can sort them by due date, by what market segments they are impacting, whether they affect service providers, enterprises, or retail customers. There are different ways to filter the initiatives being displayed on the roadmap and quickly understand how it will impact timelines and customers.

Creating that transparency and keeping everyone—engineering, product, and sales—on the same page was beneficial. These stakeholders could log into Productboard and see what was being worked on and when it would be deployed. Everyone in the company remained on the same page.

I am a huge fan and believe Productboard was a good partner for Megaport during my time at the company. I have no complaints about the product itself. My only consideration involves the fact that Megaport is a small company with about 250 people. We originally purchased a 15 seat license agreement, and about a year after we made that deal, it became apparent that we really only needed two, three, or four seats. Productboard was not as quick as one would hope to adjust our contract to align with our actual needs, which was a challenge for a very small company with limited finances.

Licensing flexibility is the main area for improvement. The features, functionality, and how we used Productboard was really good. The lack of flexibility around licensing was the only challenge for us as a small company.

When I arrived, the agreement had already been set up where we had 15 licenses, and after being there for a year, we quickly realized we only needed two to three licenses because there were not many content creators, though there were about 100 content viewers. When we asked to scale back our licenses, we encountered considerable friction. This was the primary issue we faced.

I experienced no issues with lag or downtime. I should note that Megaport is a small company, so at most we would have probably 20 to 30 users visiting my roadmap or the customer tiles. We were not a big enterprise with thousands of people using the application.

I encountered no scalability issues, though I should caveat this by noting that we were growing from a user base of about 5 to 10 to 50 to 100, not from 500 to 1,000 to 10,000. This is an order of magnitude smaller, but Productboard worked perfectly fine for our needs.

I would give Productboard a 10 on customer service. It is very easy to get into and start playing around with it because it is very user-friendly. You learn by doing, but it is very easy to figure out how things work.

When I arrived at Megaport, they had already purchased and had an agreement with Productboard. I simply took that on, and we remained fans of Productboard. The only challenge was backing off the 15 user seat license agreement and getting it down to something more manageable, such as two to three seats.

When I arrived, we were already using Productboard. From what I recall, the company went with Productboard straight out. It was very stable during my time there.

Productboard is really good at enabling stakeholders to use it effectively. For example, a salesperson meeting with a customer could go into Productboard and see the features that the development team or product leaders were working on and tell the customer that these three features would likely be available in Q3 of next year, or that this project and feature would help them be more efficient and the project would be available in the coming month with the feature being prioritized for one quarter out. This had a really positive effect with customers, bringing them closer together and creating stickiness with Megaport and our development team.

Productboard absolutely helped with customer satisfaction because we also took that product roadmap and displayed it for customers, sharing the customer roadmap with them. Internal operating efficiency also improved because internal communication meant that everyone was on the same page with no miscommunication about what was expected to be delivered when. As part of this process, I met with the development teams and product teams weekly, and every Wednesday afternoon, I would update the roadmap with new additions and whether deliverables were getting delayed or moving up. The roadmap remained current. Internal efficiencies in communication meant that everyone was on the same page.

I did not use training materials at all. Everything was learned by trying things out and figuring them out. I cannot comment on how good those training materials were because we operated in a learn-by-fire environment.

At the time I used it, I thought it was pretty good, but I was not using the integration capabilities very much. I did not test that functionality. I used Productboard more as a communicator and as an evolving whiteboard where we updated the roadmap and made it available for all. There was some integration involved, but not much.

We used Productboard primarily for roadmap and tiles, so it was customizable, but I am not certain we were pushing the envelope on trying to do more customization. It was fairly customizable for how we used it, but we did not push the limits on customization.

Productboard is a great solution and it is probably faster to just go in and try it out and figure things out. If you get stuck, either talk to support or read the documentation, as it is very user-friendly. It is probably more efficient to just dig into it. I would give Productboard a rating of 9 out of 10.