Pendo Feedback vs. StoriesOnBoard

Receptive is very effective for multiple internal teams/department of a single product who need to scale their product feedback management effectively. We've been leveraging it for one of our products and it was so successful, that we implemented it with a second product. The main issue we ran into situationally with that was managing 2+ modules (products) in Receptive; it was a bit more difficult to present Receptive to two different customer bases/users (we couldn't change the appearance) and slightly confusing to do within the app (lots of filtering needed). I have heard that support of multiple modules is something that Receptive will likely be working on in the near future, so that's good news.

Incentivized

As mentioned earlier, we also use StoriesOnBoard to create other processes (customer and employee journey). We use the swim lanes to differentiate between measures, tools and processes and working with them is very easy and understandable for this purpose.

Less easy is the use of context, i.e. when one part of a story map depends on another story map. This cannot be avoided (at least for us) to avoid creating redundancy (and the risk of creating different stages). At appropriate places, we refer to the other map in the title.

• Captures feature requests from customers
• Organize feature requests
• Communicate progress updates to customers

Incentivized

• User role management
• Jira integration
• Keyboard shortcuts
• Filtering by personas

• Filtering in general is not easy
• I would like to be able to create a leadership priority dashboard
• I would like to know easily when something has been linked to Jira

Incentivized

• Switching the view to a vertical mode (easier to scroll).
• Better availability of information on user story mapping.
• Possibility to link to activities and steps from other maps (Context).

StoriesOnBoard works really well; all features are well thought through. It could look a bit fresher, although the new updated dashboard is already much better than it was.

I have not had a lot of contact with support, but when I do it's quick and accurate info.

Incentivized

We had UserVoice prior to Receptive but it was just too clunky and extensive for our needs. It was less about automation and still very manual work to process feedback. It also didn't provide collaboration levels that we needed for our internal teams to work together. ProdPad was a very clean tool but also didn't enable us to automate the process like Receptive does.

Incentivized

The only other competitor we looked at was cardboardit.com. Both had solid functionality, but StoriesOnBoard was more user-friendly and quick to learn and use in our opinion.

• We were managing these enhancements in our support ticketing system, using spreadsheets, and it was TERRIBLE. Being able to tell a user "Great idea! Submit it to Feedback!" has saved my support team hundreds of hours.
• We have reduced incoming support requests when the request is really an enhancement - the ability to have a "Suggest Features" widget in our software sends users straight to Feedback.
• Because we can make some fields required, we can cut down on the need to reach back out to our users for clarification.

Incentivized

• StoriesOnBoard (and story mapping in general) creates a low-cost visual method of aligning on high-level business and technical requirements early in a project and provides an ongoing reference as the project progresses. Having this alignment is critical for the later stages of the project.