UserBit's global analytics section is a powerful tool to bubble up patterns and insights across projects.
Why do we need cross-project analytics?
There are several organizational use-cases where one might want to see data across projects. For example:
Say, you had a product that was used by several clients. You wanted to conduct discovery research for a new feature with each client. It would make sense to then share the result of the research with your stakeholders separated by clients. After all, you wouldn't want to share one client's data with another. So, you'd create a separate project for each client.
However, there's also a lot of value for your team/internal stakeholders to see overall statistics on things like pain points and feature requests across all the projects. This is where cross-project analytics can play a very important role.
Duplicate project to re-use same tags, questions etc.
In this scenario it makes sense to keep a separate project for each client. The best way to create multiple projects with the same questions, tags, etc. is to leverage the duplicate project functionality. This will allow you to do the work once - create the original project with tags, relevant questions, etc. and then use the original project as template for all other clients.
Analysis across project
Now that we have multiple projects, one for each client. Internally it makes a lot of sense to see some over-all stats. For example, if we want to see the biggest pain points across our entire discovery research effort, how would we do that? This is where UserBit's global analytics section comes in handy.
Select relevant projects
Select relevant tag categories
Click on chart to see the highlights categorized by projects
Note: for the analysis to be effective, it's important for tag categories and tag names to be the same across project. This is why we recommend duplicating projects so there are no typos in tag names and you can avoid the manual work of recreating tags etc.
While analyzing projects to view cumulative data is very useful, there are certain use-cases where you would want to compare multiple projects together. For example, if you wanted to see how your efforts are changing users' experience over time, you would interview a set of users every few months. You could duplicate the same project 3 months from now and use the same tags. Once you're done synthesizing the new project data, you could now compare 3-month-ago project with the current project to see how pain points and feature requests have evolved.
Together, duplicating projects and cross-project analysis serve as powerful tools that you and your team can leverage to make informed product decisions.