Here's our current process at Salesmachine.io (from customer feedback to push in production): 1/ Our CSM and support teams collect product feedback and requests from our customers and prospects via our Intercom live chat. 2/ They send these requests to a dedicated Slack channel so they can collaborate with the product team (this is where the voice of the customers meets the builders). 3/ The product team logs the feature & improvement requests in a Trello board 4/ When the product team decides to build a feature or an improvement, they create a use story in Jira for the dev team It worked well so far but as we got more and more feature requests, we begin to struggle to visualise everything clearly with Trello columns. I'm looking for a simple tool to organize feature requests by product category and allow us to manage priority (impact they would have on our customers). Not product roadmap or product management tools.
- It is better to have a detailed look at Hygger's functionality, especially its new possibility - there is a classical 2x2 prioritization matrix! Such a function makes it convenient to classify all the tasks by four different categories in accordance with a particular task's importance and urgency. Also Hygger provides the possibility to operate your project development activity with backlog page and work with the relevant feature implementation. Try it and make sure it's awesome!
- At Heetch, we do the following: - all stakeholders can share their insights and feedbacks through a Product Board email address - all Zendesk Tickets can be sent to Product Board - all PMs can add feedbacks & Insights to Product Board directly based on personal experiences and ideas of the product, or user interviews. Those feedbacks are then parsed by PMs daily, assigned to an already existing feature or create a new feature based on that feedback in a product space matching their product scope. Each features are then ranked according to our own prioritization system, and lead techs add workloads. We try to maintain workloads as they tend evolve with our system evolutions. Things can get easier thanks to an opportunistic refactorisation. This then let us plan up the next quarter quite easily as you have a clear idea of all customers requests and feedbacks (in terms of volume) as well as qualitive snippets from the actual requests, and your own analysis matrix. Once we decide to commit to a feature by including it in our quaterly roadmap, we define all steps: - problem statement & research - design - development (with a handy « push to Jira » that creates an epic) - shipped - post analysis We tend to do all steps as a team, meaning that all the team is involved in the entire process, with a lead that changes depending on the stage (PM for problem statement, designer for design, and so on) This is only used for product strategy, the usual software pipeline is managed through classical project management tool. Hope this helps.
- I recommend using hellonext which is gaining more popularity due to its ease of use and affordability compared to others in the market. hellonext has a simple platform design that doesn't intimidate your customers and allows them to provide feedback comfortably.hellonext also has an upvoting feature for customers to upvote others’ requests, allowing you to know what the most popular requests are and prioritize accordingly. hellonext solves the user engagement problem by having comment threads for the request submissions, tags like ‘under review’, ‘planned’, ‘in progress’ and automatically updates users through email. Plans start as cheap as $20/month making it really cost-effective compared to others in the market. hellonext is also releasing an ios and android app. You can try the demo or free trial to see how it works for you !