"Wow, you guys are onto something."

“Our Solutions Architect’s approach was consultative – he got to know us. We took him through our deliberations, and he showed us different approaches we could think about when using Productboard. It was a really successful journey and we’ve landed quickly on a pragmatic model that’s made a substantial difference …

"I’ve been doing product management for nearly 20 years now, and I’ve always been looking for a tool like this."

“We chose Productboard because of all the different views we were able to set up and manipulate as well as the flexibility of being able to use different prioritization criteria.”

“It was a logistical nightmare to know if an integration was going to go ahead and setting expectations for users was impossible.”

“It was easy for me and the other product managers to visualize our current workflow and replicate it in Productboard with minimal effort.”

“Productboard is now the default thing to do when you have feedback to give to the product team at Tray.io.”

“We have one product manager on my team who is just the king of spreadsheets. He's got half a million for any project that he spins up. It was nice to see how he reduced that behavior to really drive things forward using Productboard.”

“Productboard solves a cross-functional challenge. A developer can work in Jira to get their tasks done, but Productboard helped the team coordinate across the entire business.”

“Our product team all leverage Productboard to plan and prioritize features, and designers, marketers, and customer success team members can view the current status and priority of planned and in progress features in Productboard.”

“With this approach to the roadmap, we can look at a feature and say ‘wow, that matches our strategy. No one asked for it, but it would pay for itself in less than a month.’ Or, ‘Wow, that feature is requested by so many people, but given how long it …

“This is something Productboard seems built for. You take your strategic initiatives, drivers, objectives, feedback channel, and a scoring algorithm as an input into the process, and let it essentially help recommend what to do next.”

“If we’re looking at a feature that is attached to a lot of red accounts or a larger customer who has a major impact on our revenue, we can really get into that segmentation in Productboard.”

“Productboard’s roadmap is where I spend most of my time in planning because it’s easy to move things around. In our recent release, we wound up pushing things out to the ‘later’ column and created a whole new release plan based on that — the next one just fell out …

“We started with Productboard because we had a need to collate feedback and action on it, and what it turned out to be was a mechanism to transform the business — from a technical feature factory to a user-centric value driver. That was the big change.”