Best practices for organizing and analyzing feedback in Listen

Last updated:

Pendo Listen is designed so that feedback arrives, and is organized, with as little manual work as possible. This article describes a recommended way to categorize and analyze feedback so that each team can find the insights it needs without reviewing every feedback item.

The recommendations build on each other. Start with apps and product areas, and add labels and statuses only when a specific use case needs them.

Guiding principles

Keep the following in mind when you decide how your organization handles feedback:

  • Choose the simplest workflow that gives you value, and add to it only when you find a use case for more.
  • Use automation rules and AI to categorize feedback. Categorizing each feedback item manually doesn't scale.
  • Review themes instead of individual items. You don't need to read every feedback item to learn from your feedback.
  • Use ideas, not feedback items, to track progress and to update customers.

Start with an Explore report

Before you set up categories, use Listen Explore to find out what your feedback contains. Explore generates a report from a prompt, a set of filters, or both, and groups the results into topics. The top topics show you which parts of your product receive the most feedback, which helps you decide the product areas and feedback views you need.

Explore is available when Listen Explore is enabled for your subscription. For more information, see Enable Listen Explore, Explore feedback with AI in Listen, and Best practices for writing AI prompts in Explore.

Categorize feedback by app and product area

Apps and product areas are the foundation for everything else in this article. They tell you which application, and which part of that application, a feedback item relates to. They're also the most reliable way to send feedback to the team that owns it. Keep your product areas broad so that they stay stable as your product changes. For guidance, see Product Areas and labels in Listen.

Assign apps and product areas automatically wherever you can:

  • Guide polls. Feedback items created from guide poll responses are assigned the guide's app and product area. For more information, see Send guide poll responses to Listen.
  • Automation rules. Listen Managers can create rules in Listen > Listen settings > Automation rules. A rule can assign an app or product area based on the words in a feedback item or the source it came from. To categorize feedback that you already have, turn on Also apply rule to matching items when you create the rule. For more information, see Manage feedback and ideas with automation rules.
  • AI-based assignment. With Listen Explore, you can add context to each product area and turn on the Assign Product Areas rule. Pendo then assigns a product area to feedback that doesn't already have one from an automation rule or a manual edit. For more information, see Automatically assign feedback to Product Areas using AI.

Before you create automation rules, decide what you want them to achieve, such as sending feedback to the right team or categorizing feedback about a specific feature. A clear goal keeps the number of rules small and easier to maintain.

Create a saved view for each team

A saved feedback view is a saved set of filters. Create a view for each product team, filtered by the team's app or product area, so that each product manager has one place to find relevant feedback. New feedback that matches the filters appears in the view automatically.

Each view includes an Overview tab with a summary and charts for the feedback in that view. With Listen Explore, each view also includes a Topics tab, which groups the feedback in the view by topic and updates automatically. This means that a team can review the main themes in its view on a regular schedule, for example, monthly, instead of reading each item as it arrives.

Some feedback needs faster attention, such as bug reports or feedback from key accounts. Create a separate view for these exceptions, and use an automation rule to label the feedback that belongs in it. For instructions, see Save custom views of feedback and View feedback insights.

Use labels for specific use cases

Labels are flexible and work independently of apps and product areas. Because a label can be anything, labeling can quickly become a manual task that's difficult to maintain. Don't start with labels. Add them when you find a use case that apps and product areas can't cover, such as the following:

  • Classify feedback within a product area. For example, in a "Dashboards" product area, use labels for "Reports" and "Widgets" to show which group of features the feedback relates to.
  • Group feedback across apps and product areas. For example, add a "Localization" label to find all feedback about localization, whichever app or product area it belongs to.
  • Show that an action is needed. For example, add an "Action: Documentation" label to feedback that describes a workaround that isn't documented. The documentation team then uses a saved view filtered by that label to find its feedback.

If you only want to group similar feedback by theme, use the Topics tab of a saved view instead of labels. When you do use labels, group them with label categories, and apply them with automation rules where you can. For more information, see Organize Listen data with labels.

Use statuses only when an action is needed

Every new feedback item has a status of New, and most feedback can stay that way. Change the status to Under Review or Reviewed only to show that someone needs to act on a feedback item or has acted on it. For example, a team that works from an "Action: Documentation" view updates the status when it finishes with an item.

Avoid a workflow in which someone updates the status of every feedback item. That work grows with every new feedback source and doesn't add insight.

To track work through development and to tell customers about progress, link feedback items to ideas and update the status of the idea. For more information, see Link feedback items to ideas.

Was this article helpful?
0 out of 0 found this helpful