Grow product insights into killer feature ideas with Feedback Management - STEP 1 Streamline product feedback collection - STEP 2 Automate product feedback sorting & management - STEP3 Create actionable feature ideas from insights - STEP 4 Develop product feedback into actionable feature ideas - STEP 5 Validate ideas on a feedback portal - STEP 6 Push ideas to a story map - STEP 7 Close the feedback loop

1. USER FEEDBACK
MANAGEMENT
Grow product insights into killer feature ideas
with Feedback Management
www.StoriesOnBoard.com
Slack
SalesForce
ZenDesk

2. What is StoriesOnBoard User Feedback Management?
StoriesOnBoard User Feedback Management is a collaborative tool for
gathering valuable product feedback from both internal and external
stakeholders, developing actionable feature ideas and validating them
on a public portal.
StoriesOnBoard.com
Record all product insights along with related contact information
coming from:
->
User feedback forwarded by the support team
->
Ideas of the dev or product team
->
Feature requests of the client
->
Insights gained from user interviews or surveys
->
Bits of some inspiring articles you found online
You can come back later and sort them into ideas, archive the ones
you don’t need for now or push them to the ‘Incubated’ list, meaning it
needs some nurturing before proceeding to the next phase of ideation.
Storing contact information of users and stakeholders providing
insights will help you later with closing the feedback loop.

3. How to use Feedback Management
STEP 1 STREAMLINE product feedback collection
Track user & stakeholder feedback
coming from different channels in
one place
Capture product insights quickly
while you're browsing the web
Store source of insights and product
ideas so that you can follow up on
them later
Incubate insights that you're not yet
ready to work on
-
->
->
-
Forget about manually going through
each piece of feedback you get
Set up custom automations to tag
and sort your product insights
Start working with a well-organized
insights backlog
-
->
->
STEP 2 AUTOMATE product feedback sorting & management
StoriesOnBoard.com

4. How to use Feedback Management
STEP 3 CREATE actionable feature ideas from insights
Group product insights into higher-
level feature ideas
Add user & stakeholder insights
later to an idea
Keep track of product feedback
that belongs to the same idea
-
->
->
Collaborate with your team to
develop feature ideas
Add attachments such as mockups
and links to feature ideas
Assign different tags to ideas to
categorize them
-
->
->
STEP 4 DEVELOP product feedback into actionable feature ideas
StoriesOnBoard.com

5. How to use Feedback Management
STEP 5 VALIDATE ideas on a feedback portal
Create a roadmap to let
stakeholders know what's on
your radar in development
Make your portal public or
share only with a selected few
Allow your power users to vote
and comment on ideas
-
->
-
Plan iterations by pushing ideas
to a story map
Find the right place for your
idea on the user story
Weigh alternative user steps
and set priorities
-
->
->
STEP 6 PUSH ideas to a story map
StoriesOnBoard.com

6. 5 quick wins for involving executives
STEP 7 CLOSE the feedback loop
Notify all concerned users and
stakeholders easily
Improve engagement through
expressing appreciation
towards their feedback
Build a power user base
around your product
-
->
-
“The biggest challenge for me as a Product Manager has always been
keeping things organized whether that's feedback from clients, the dev
team or just random ideas. StoriesOnBoard is saving me so much time I
would be spending on getting lost among e-mails, notes and Trello cards.”
Olivia Rios
Product Manager
You’ve got a question?
Let us know and let’s discuss
what are the best practices.
Book a demo
StoriesOnBoard.com

7. Get the most out of StoriesOnBoard
User Feedback
Management
User Story
Mapping
What type of feedback can I manage with StoriesOnBoard?
You can collect all types of feedback in StoriesOnBoard coming from
different channels, should those be external (users, clients or
customers) or internal sources (development team, design team, sales,
marketing or support).
We encourage you to start collecting small bits of information first (not
entire feature ideas) - we call these ‘insights’ in StoriesOnBoard. This
will give you plenty of flexibility later to group some of these ideas and
issues into user-centric feature ideas.
StoriesOnBoard.com

8. Can I send feedback from customers directly into my feedback repository?
Steps of the product discovery with JIRA
Yes, you can do this in a number of ways. The most convenient might be
to generate a specific e-mail address in StoriesOnBoard for feedback
collection. All e-mails sent to this e-mail address will automatically land in
your insights inbox.
Using our Zapier integration, you can set up highly customised zaps that
will allow you to channel customer feedback from different customer-
facing apps directly into StoriesOnBoard.
We’re also constantly working on expanding on our integrations, so make
sure to check the latest ones out.
Steps of the product discovery with JIRA
Yes, you may decide to give permission to users to send insights directly
into StoriesOnBoard. You can do this by generating a specific e-mail
address in StoriesOnBoard.
If you choose to do that, we recommend to create a company e-mail
address like feedback@yourcompany.com and forward incoming e-mails
to the address you created in StoriesOnBoard.
This way you’ll keep your branding and the opportunity to generate
another e-mail address in StoriesOnBoard in case it gets spammed
heavily in the future.
Can users send feedback directly into my feedback repository?
Can I send feedback from surveys & different channels into StoriesOnBoard?
Yes, StoriesOnBoard can store and help you manage any feedback and
information regarding your product whether external or internal feedback.
What’s more, having different types of feedback may help you have a
broader perspective to develop user-centric ideas.
StoriesOnBoard.com

9. Does contact information of the source get stored with the feedback?
Steps of the product discovery with JIRA
Yes. If you specify contact information of the source (or if it is specified
automatically in case of automations), it gets stored with the insight
directly. Later, when you start developing feature ideas and validating
them on a public portal, insights (smaller bits of feedback that led to the
feature idea) will still be linked to the idea, storing contact information of
the source.
This way, you can always reach out to both external and internal
stakeholders if you have further questions or just to let them know their
idea has been implemented without having to spend time on digging up
their contact information.
Visit us for product development best practices
StoriesOnBoard.com
You’ve got a question?
Let us know and let’s discuss
what are the best practices.
Book a demo
JOIN US!
Start FREE trial
Grow product insights into killer feature ideas with Feedback
Management and push them to a story map
Let us help you to build the best products with user story mapping