When just getting started with Shipright, it's recommended to have a look at the setup of your themes. You can make a start with some themes that make sense to you, so you'll be able to find relevant insights easily later on. Here's how.
Configuring themes in Shipright
In Shipright, go to Insights. In the top menu, choose Manage Themes. 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.
Especially for feedback, we recommend you to tag each insight that you define on these factors:
Product component (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 insights related to for instance a screen you're planning to redesign.
Quality factor (usability, performance, security, reliability, etc)
It's common to tag based on quality factors, so that people in your team can find back insights related to their specialization. Designers may want to focus on usability issues, while engineers may be interested in problems related to performance.
Platform (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 insights that relate only to specific platforms.
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 new areas over time, especially when you're performing research activities. Themes might also be useful if you have multiple teams or departments working on separate topics, which requires a separated view of user Insights.
These factors have seemed useful for some teams using Shipright:
If you're working on multiple products in your company, but your feedback & research processes are combined, 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". Additionally, we recommend to keep each product's components as separate themes, but prefixing them in the title for clarity, like: "Product A - Notifications".
Journey (interested, onboarding, membership, growing, etc)
It can be useful to filter insights 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 user insights 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.
Other examples of factors that may be useful are emotion (frustration, excitement, etc), or research project (i.e. insights related to beta test of new Product C).
When you analyse feedback in your Dock in Shipright, you highlight interesting chunks. This can be something like a frustrated user sharing that something is not working according to his or her expectations. You can then store that particular part as an Insight. Each insight can be tagged with one or more Themes, which helps you find Insights based on a shared topic easily later on. You can assign Themes directly after creating an Insight, or you can adapt the them in the All Insights tab by clicking on the three dots menu on the far right of an Insight.
Not sure how to set up themes for your situation? Just drop us a message using in-app chat or firstname.lastname@example.org. We'd be glad to help you sort it out.