Key Insights in Aurelius are summaries or...insights...from your user research and customer feedback that you've collected on projects.
What is a Key Insight?
Create Key Insights in Aurelius when you want to communicate a learning or insight from your user research and customer feedback with your team. Using Key Insights helps you share high level points of the research and a summary of what you've learned without having to read all your data.
A Key Insight has 5 parts:
a name (the insight itself, e.g. "The mobile sign up form was too confusing")
description (more details or comments about the key insight)
supporting notes and documents (all the notes from your research project that led to this key insight)
tags (any way of describing or organizing what kind of key insight it is)
priority (low, medium, high... you can filter by these in other areas)
type (design, feature, product, usability... you can filter by these in other areas)
Creating a Key Insight
You can create key insights several ways within you projects:
Here's how to create a Key Insight in from the Key Insights page on your project:
Go to a Project > Key Insights > + New Key Insight
Any Key Insights created on your project automatically get added to the Report.
Here's how to create a Key Insight from the Notes or Tags page on your project:
Select Notes > Create New Insight
Here's how to create a Key Insight from a Report in your project:
Go to a Project > Report > Edit > Add New Insight
Any Key Insights created on your Report automatically get added to the project.
Project Insights vs. All Insights
Any Key Insight created from your projects are automatically available from the All Insights page as well.
Your project Key Insights page will show you only Key Insights for that selected project. The All Insights page will show you Key Insights created from every project.