StoriesOnBoard Feedback Management gathers product feedback from customers, users & your team into a single repository and organizes them for you based on rules you create.
Replies
Best
Hey StoriesOnBoard Feedback Management Team,
I was wondering whether it is possible to have all our feedback sent into to the tool if we receive most customer feedback via e-mail?
Hey @kazi! Thanks for the question. Yes, actually, the way this works in StoriesOnBoard is the following: StoriesOnBoard will generate a random e-mail address for you for feedback collection. If you forward any e-mails to that address, they will land automatically in your inbox. If you already have an e-mail address for customer feedback in use, we recommend setting up automatic forwarding from that e-mail address to the one StoriesOnBoard generated for you. This way, if your e-mail address ever gets spammy, you can simply swap it out for another one.
Report
@mercedesznemes Thanks!
We have a messaging and bug reporting form built into our app. This sends a copy of these messages to our inbox via email. I think I'll hook it up to your service and have these messages sent directly to this application. The automation feature looks promising too, I can mark these messages with a label just like we have it in GSuite.
Hey Hunters and Makers!👋
We’re stoked to roll out StoriesOnBoard Feedback Management that takes user-centric product management to a whole new level. 🚀
💡For those of you who haven’t used StoriesOnBoard before: We used to be a user story mapping tool above all that facilitated the discovery process, conversations & shared understanding between the dev team & customers as well as release planning. Since user story mapping effective during the discovery process, we wanted to give a tool to our user base of PMs dedicated to creating lovable products that will give them that user-centric approach further along the way.
StoriesOnBoard Feedback Management is now here to upgrade you entire product management process:
☑️ Automate customer feedback collection into a single repository
☑️ Sort & organize product feedback based on custom rules automatically
☑️ Group user feedback to create actionable feature ideas
☑️ Collaborate with your team to work on feature ideas
☑️ Validate ideas on a public roadmap among internal & external stakeholders
☑️ Close the feedback loop & reach out to users who provided feedback
☑️ Plan releases on a user story map
Want to know more? Start here: https://storiesonboard.com
P.S. Beside hoping to deliver significant value for your feedback management process, we have something else for you. If you sign up today, you can use StoriesOnBoard Feedback Management for FREE for 2 months.
Cheers,
Report
Very cool addition to story mapping! I’ve been a story mapping user for a while and have been keeping an eye on your updates. The only thing that is still unclear for me how you fit story mapping into your new process?
Hey @barpaff! We appreciate the question!
When we designed this new product, our vision was to create a tool that supports cyclical iterations. Story mapping can come into the picture either at the beginning for product discovery when you’re starting at zero and want to come up with an MVP or later, when you’re continuously developing your product and you need to place feature requests you receive and want to develop on the story map to plan releases. The latter you can do by selecting an idea on the idea board and push it to a story map of your choice. On the story map, the idea appears automatically under non-scheduled release. You can take the idea and drag it to a release and user step of your choice.
Report
Hey team! I find your system very interesting and your integrations could work really well for me, but I was wondering how to try the app if I don’t want to pull all my data into the app at first? Thanks in advance!
Hey @klajko_dora ! Thanks for your question. While collecting your product insights into our repository automatically is undoubtedly the most convenient option, you also have the option to do it manually. We would advise you to start small by taking a single feature idea and first adding all insights belonging to that feature idea to StoriesOnBoard. (you could also pick a single product, or any other smaller piece - whatever makes sense to you) You can add insights manually, install the Chrome extension and experiment with that or generate a custom email address and simply send all insights to that and they’ll automatically appear in StoriesOnBoard. Start experimenting with only a handful of insights first, tag them sort them into different lists and when you’re ready to proceed, create a feature idea out of them. Once you have your feature idea ready, you can invite your team mates to collaborate with you in developing that feature idea. The key takeaway is: you don’t have to pull in all your data right away, you can start small by processing only a handful of product feedback.
Report
Hey Makers of storiesonboard! I checked out the app and would love to try it out at our company, but we manage multiple products. I can see only one platform here for feedback collection. Is there a way to differentiate between different products?
hey @inez_b, you have a couple of options for that. If you handle multiple clients and their data is sensitive, you can always create different workspaces for them. If you don’t mind having all feedback & data in a shared pool, we recommend assigning custom tags to insights or creating custom lists for them. This way, you can keep feedback belonging to different products separately.
Hey @mattcrail ! So far we have integrations with Jira, Trello and Azure because most of our users use those issue trackers. If the need for any other integration comes up, we'll make sure to validate them on a public roadmap. ;)
Thanks for the question @tamas_parvanyik ! Actually, we get this quite often.
We believe that to create a buzz around your product, you need to build up a community proactively. Users who make their voices heard (actually take the time to send feedback in) already show a certain level of engagement. If you actually reach out to them later and follow up on their feedback (for example that their idea has been implemented), they’re more likely to become power users and advocates of your product. StoriesOnBoard Feedback Management helps you with that by always having the contact information of the feedback source available at any stage of feedback management - from feedback collection to feature idea design. This way you can reach out to whoever the feedback came from anytime.
Report
Pumped to have all my feedback finally sorted out! Great stuff!
Hi Storiesonboard team,
I have been looking for a way to organize feature requests for a while now. I receive a lot of those from both our team and the customer. Is there a way in Storiesonboard to differentiate between the two?
@peter_wright12 Absolutely!
As the first step, you can streamline lead sources into the same inbox. Lead sources are highlighted on each insight (email, external users, insights from the public roadmap, internal user, customer support etc.).
I recommend using the automation feature where you can set up triggers and actions - so that new insights can be organized into groups without spending a minute sorting your inbox. Moreover, you can add tags or link new insights directly to the relevant feature idea fully automatically.
Our product team put a lot of effort into the automation to save time for our users ;-)
Replies
StoriesOnBoard
StoriesOnBoard
StoriesOnBoard
StoriesOnBoard
StoriesOnBoard
Taskable
StoriesOnBoard
StoriesOnBoard
StoriesOnBoard
StoriesOnBoard
StoriesOnBoard
StoriesOnBoard