Categorising your feedback – 3-step quick guide

After the feedback starts coming in you’ll want to bucket that into different subcategories. Here are a few of the most common ones:

  • Major product bugs. These are extremely urgent issues that prevent users from getting the core value out of your product. For example, if you have an instant messaging product and users cannot send a message.
  • Minor product bugs. These are minor issues that don’t distract from the core product value. For example, using the same hypothetical messaging product, this would be if your users couldn’t insert a specific emoji into their message.
  • Feature requests. We covered feature requests extensively in the previous section of the A.C.A.F. Customer Feedback Loop framework. The next step is prioritizing feedback based on a mixture of volume of requests, potential impact of building that feature, and opportunity costs associated with each choice. Here’s an great guide from Trello on how to manage feature requests.

You can manually categorize this feedback using a spreadsheet, assigning labels to specific columns, then creating a PivotTable or V-Lookup … but this can be time-consuming.
An easier way is leveraging a customer feedback tool that helps you categorize the feedback by assigning each insight into a project directly. Nsigtio offers just this, find out more here