Productboard

A quick and specific example of how I use Kanban within Productboard in my day-to-day work is that we do all the sprint and backlog work, and by configuring its swimlanes, I can check from status to status where each activity is according to the team's progress across all areas: product, development, QA, all the way through to completion.

Weekly I issue reports to monitor the Kanban part and identify what we can leverage from the team's capacity, looking at some markdowns there to make decisions.

In the dashboards area, I can monitor in a very easy way the team's capacity, which is my main goal and my main focus when looking at the dashboard.

Productboard has had a positive impact on my organization as it was recommended to me and appeared as a platform different from the ones I was using at the time, but it came bringing an ease of monitoring the process.

After adopting Productboard, I have noticed concrete results such as having the dashboards available allowed me to make quick decisions regarding the sprint and things that happened related to deliveries that were going to be late, but ended up working out due to decision-making with the data being displayed there by the platform.

My experience with pricing, setup costs, and licensing is that the company paid for it, and I ended up not taking part regarding costs, but I believe it made sense for our current moment.

My main use case for Productboard is using it to build my roadmap and show it to other stakeholders, making sure that all of the Jira tickets that we have are linked to it so that any other product leaders or leaders across the company, the engineering team, or design can take a look at what is currently being worked on as well as what is up next on the roadmap.

For most initiatives and features that I have built using Productboard, it always starts with creating a top-line level Productboard feature, and then from there, if there are any sub-features, I will break those down as well using the sub-feature component of Productboard. This has really helped particularly my engineering manager to see what is going on so that she can allocate work to her engineers.

The best features that Productboard offers include the connection to Jira, which we use the most, the ability to see features both in the timeline view as well as the list view, and being able to switch between the two. Furthermore, being able to look across the organization and link dependencies helps us make sure that we are being transparent and are not stepping on each other's toes.

I find myself relying on the Jira connection all the time. I will either make my tickets directly within Jira or I will make them in Productboard and port them over. Typically, I make them within Jira and then port them over, which helps keep everything in a timeline.

Productboard has impacted our organization positively by helping us become more transparent across all the different departments, particularly when it comes to dependencies that people have on other departments and other product managers. For example, I found that another product manager was building a very similar pricing feature that I was building because of Productboard, and as a result, we were able to collaborate on that and build one system instead of two that would work for both of our products, as well as making sure that there is not any code redundancy.

Regarding how Productboard can be improved, I think what I would want more of is perhaps some more keyboard shortcuts, as I feel sometimes it is a bit difficult to navigate around and I prefer to do things extremely quickly. Typically, Productboard is not where I am ideating; it is where I am putting in things that I already know. I may have already written a PRD and now I need to create a new item or feature on Productboard to indicate that this is now in progress or this is a potential thing on the roadmap. Sometimes I think Productboard really encourages putting all of the information in at one time, but often what I need to do is add a bunch of features and items in rapid succession. I almost feel that something closer to a spreadsheet view, which I know Productboard has, but something that works more in that manner where I can easily click into something and edit it as opposed to having to click into a very specific spot or having to click on something that takes a second for a dropdown to populate could probably be improved.

I would love for a feature in Productboard that alerts you if somebody else adds a similarly titled item so that you know when someone else is working on something. It would also be nice to improve the searching for features, which I feel is a bit difficult in Productboard because of all of the different views and the number of collaborations across the company.

I have been using Productboard for three years and I was one of the first people at my company

to test and adopt it.

I find Productboard to be stable.

Productboard's scalability is good as it allows work across basically every single person in an organization.

Productboard's customer support is really good. We have had a few calls with customer support or customer success at Productboard, probably because we had a specific plan with them, and they were always very helpful in getting us up to speed and learning about all of the different features.

Before using Productboard, we were just using Google Sheets, Google Docs, and PowerPoints to communicate our roadmaps across the company, which really put product managers into silos. Everyone was using different formats as opposed to one format.

My advice for others looking into using Productboard is that it is very important to have a strong setup from the start. Part of what made it a bit difficult to use at first is that we did not have the Jira connection initially, nor the ability to see things in the table view as opposed to just the timeline view. Getting all of those things set up early on would make it really good for people to be able to get used to using it as soon as possible.

I have not seen a return on investment nor can I share relevant metrics as I am not the decision maker for purchasing Productboard. That being said, all of the things that I have mentioned in regards to collaboration definitely have seen notable improvements.

Productboard is a good tool and I would recommend most companies use it, but the things that I have shared would be really helpful to improve. I would rate this product an eight out of ten.

I primarily use Productboard for two things: requirement management to capture business requirements and maintain traceability, and as a central location for storing customer feedback.

Our customer success team uses Productboard for customer feedback, which we also use to roadmap based on complaints that we have received.

For a recent example of how I use Productboard for requirement management and customer feedback, I was working with various teams, and multiple feedbacks were coming in.

I log these multiple feedbacks, and from there, the product management team addresses the issues and helps the sales team with upsell opportunities.

The best features Productboard offers are the feedback and insights, which stand out because we get a centralized location where all feedback is stored.

From my perspective, feature prioritization, the product roadmap, and the customer portal are very helpful for traceability.

When things go down the drain, we can always trace back to where feedback came from, and user need or feature prioritization is really valuable for me.

When I share about feature prioritization and product roadmap from my experience, I have 15 customers with 10 repeat features from each customer. Based on that, I could evaluate the impact, how many customers need it, and what value it provides. This is part of our business objective, and another consideration is regulatory changes.

I noticed that there is a very big change coming up, and many of our customers in the similar domain are starting to ask for the same feature. Based on that, we could figure out the priority. Productboard breaks down the board into four different areas.

Productboard has positively impacted my organization by reducing the churn rate by two percent.

I do not see a major scope for improvement at this time, but I see more potential for GenAI. I'm seeing a GenAI scope of improvement, which is why I chose a rating of seven out of ten.

I have been using Productboard for close to two years.

My advice to others looking into using Productboard is to give your time, talk to the team, and talk to the pre-sales engineer. This feels like a slow burn.

Regarding Productboard's AI capabilities, I think its governance and security are top-notch. I also feel that the accuracy and reliability of Productboard's AI output are top-notch. I am rating this review a seven out of ten.

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.