Overall Satisfaction with ProdPad
Our product management and development organization uses ProdPad to collect user feedback, develop new feature ideas from inception through writing user stories, and communicate our roadmap internally at the company. Our customer success, sales team, and customers all provide feedback through an API-driven feedback collector in our application, product management processes that feedback for classification and attaching to existing ideas we have for new functionality. We save designs and user research in ideas, which we eventually add user stories to in order to push to our issue tracker. The roadmap collects ideas we're working on now and in the future.
- Customer feedback collection and classification.
- Present a clear and easy-to-use roadmap to users internal or external at the organization.
- More user-role driven views of the application would make it less daunting to non-product manager users.
- It has been easier to show people what we're working on, when.
- It has been far easier to collect customer feedback and correlate common challenges and needs.
- We now have one place for research and feature documentation.
Excellent quick response from team members, great opportunities to engage in design discussions for upcoming features, never had a bug last long or go unresolved. Overall, support is one of the best parts of working with ProdPad.
Do you think ProdPad delivers good value for the price?
Are you happy with ProdPad's feature set?
Did ProdPad live up to sales and marketing promises?
Did implementation of ProdPad go as expected?
Would you buy ProdPad again?
ProdPad is well suited for an organization that does upfront product ideation and user research extensively before building features. It works best when user stories and ideas are passed to implementation teams after deep validation and grooming. It's less well-suited when developers are more actively engaged in the product ideation cycles and are expected to be more proactive in creating tasks and user stories for themselves from broader ideas. Anyone doing something Agile-like with formal product management and ownership would get strong value out of ProdPad. But we do find it's hard to "convince" developers to engage with ProdPad itself; so the more back and forth between engineering and product ideation processes the less well suited the tool.