Product feedback comes in a lot of forms, covering a lot of dimensions. With Requests, you're already bundling similar feedback under one Request.

With Themes, you're able to organize even further. You can organize your Requests by product component, by feedback type (e.g. 'request', 'improvement'), by quality factors (e.g. 'usability', 'performance'), by team, and many other dimensions you find convenient.

Let us explain further, and help you with a few examples and best practices.

Editing themes in Shipright

You'll find your theme setup in your settings. Here you can add/remove/rename themes and move them around between groups.

To move themes around between different groups, you can use drag&drop. Within one group, themes are automatically sorted by alphabet. It's also possible to add, delete and rename groups to restructure your themes.

For product feedback, it's really helpful to tag each Requests that you define on these factors:

  • Product component (e.g. account settings, billing, notifications, etc) You should customize these based on important components (main features or screens) of your product. This will help you later on to quickly find important Requests related to for instance a screen you're planning to redesign.
  • Feedback type (e.g. feature request, improvement, pain, bug, love) Using feedback types helps to zoom in on particular feedback. 'request' or 'need' might help you filter down and see what is most often requested by your users. If you combine this with 'Product component' themes, you can even see what is most requested in a certain area of your product. Combine it with 'User filtering', and you're able to see what a certain customer segment demands most.
  • Quality factor (e.g. usability, performance, security, reliability, etc) It's common to tag based on quality factors, so that people in your team can find back Request related to their specialization or in case you want to work on a particular kind of improvement. Designers may want to focus on usability issues, while engineers may be interested in problems related to performance.
  • Platform (e.g. iOS, Android, Web, etc) If your product is multi-platform, it can be useful to create themes for these as well. This helps you find Requests that relate only to specific platforms.
  • Team In case you have multiple teams working on separate topics related to the product, you can link Requests to one or multiple teams. This makes it easy for the respective teams to filter on Requests that only relate to what they're working on.

Optional themes

Depending on what your company works on, other factors can be relevant as well. It's quite normal that your themes evolve over time, so don't worry about getting it perfect at the start. Sometimes you discover or develop new areas over time.

These factors have seemed useful for some teams using Shipright:

  • Product If you're working on multiple products in your company, you could add the various products as themes (i.e. Product A and Product B). ¬†This way, you can for instance find "usability issues related to Product A".¬†
  • Journey (e.g. interested, onboarding, churned) It can be useful to filter Requests based on where in the user journey they occur. An example: when it seems that many people are falling off in the first period of using your product, you might want to focus on Requests related to the onboarding part of a user journey. If your user journey is complex, and efforts are often planned based on these journeys, it could be smart to add themes for these.

Need help?

Not sure how to set up themes for your situation? Just drop us a message using in-app chat or We'd be glad to help you sort it out.

Did this answer your question?