Contents:
What is Feedback management
Feedback management provides the possibility to collect and organize essential end-user and stakeholder feedback in the form of insights on StoriesOnBoard. While receiving critical Feedback from stakeholders is great, you can organize these insights and if you see a pattern that can lead to a new actionable feature idea or initiative, an idea can be created on a dedicated idea board. Then, from the insight inbox you can attach insight to the right idea to keep track of them.
Although the idea board is used for internal communication and planning, there is a possibility to share your ideas and initiatives with your stakeholder over a public portal. Then, stakeholders can plan a role in prioritization as they can upvote ideas or even send feedback through the portal.
When the team took into consideration all the received information and decided that a new feature idea should make it into development, the idea itself can be pushed to the right user story map where team members can create the necessary user stories and describe their details.
To support this, on the story map interface you can even access your ideas from the idea board and access all the received and connected stakeholder insights to specific ideas in order to make informed decision and to be able to add the right tasks directly into the backlog.
Once a new feature is fairly detailed in the backlog you can also push the newly created user stories to the associated issue tracker system (Jira, Azure Devops, Trello, GitHub) for execution.
This practice ultimately supports the team to close the feedback loop as efficiently as possible and to build a better product that provides the right solution for real user's pain.
What are the components of Feedback management
Feedback management includes the following components:
Insights
Product insights can take various forms such as product bugs identified by the dev team or feature requests of users. Product feedback can come from a variety of channels, making it quite challenging to keep track of how many users on what channels actually requested a feature. When it comes to prioritization and road mapping, transparency is key. This is why collecting all product-related insights into a single pool is critical.
💡 Tip - Learn more about Insight management
Ideas
Incorporating several insights, ideas serve as the middle level in the product feedback hierarchy. Ideas should be created for features that could be pushed to development. So while insights are only crumbs of information, ideas are used to organize the noise of insights and define actionable new features or initiatives. Then connect all the related insights to the relevant ideas. This provides the internal team with flexibility to organize their upcoming activities and make meaningful discussions and prioritize what to include into the backlog.
💡 Tip - Learn more about Idea management
Portals
Portals help to share selected ideas or initiatives that the team is working on and share them with stakeholders. This way, stakeholders can gain a comprehensive overview of new features that are under consideration. Over the portal stakeholder can play a vital role in prioritization and they can also submit their feedback to the team.
💡 Tip - Learn more about Portal management
Who can access Feedback management
Only licensed users can access the internal details processed within the Feedback management module.
Subscription Admin, Admin and Members can access the insight inbox, idea board and portals. - Observer users can only submit insights for the team and access public portals.
Which plans include Feedback management
Feedback management is available in Plus and Premium plans.
Learn more about: