Links
💡

Insights

Insights are valuable pieces of information you want to link to a feature.
We see feedback like a diamond 💎.
At first, it is rough, unfaceted, and unpolished. But with some work, it gets extremely valuable.

Table of content

Intro

Here's how to create Insights from Feedback... or polish your diamond.
  1. 1.
    Highlight the relevant piece of text in the feedback
  2. 2.
    Click on 💡 (or hit ⌘1) to create an Insight
  3. 3.
    Link it to the right 🌱 feature, or create a new one
Feedback-Insight-Feature is the default configuration. In a Pro plan, you can customize your hierarchy with additional layers like epic, bug, feature, user story, etc. You can always rename these to fit your own taxonomy.
Try it yourself 👇
Every insight you create will appear in the insights panel on the right. They will also inherit the properties of the feedback they came from.
This includes:
  • Customer – Who gave the feedback?
  • Assignee – Who's in charge of processing the feedback or acting on it?
  • Source – Where did the feedback come from?
  • Custom properties – You'll use them to organize feedback the way you see fit.
Once you're done extracting Insights from Feedback, mark the Feedback as "processed"
Mark feedback as processed once you're done extracting Insights
You'll find them all in your Insights section on the left side panel.
Once you create an insight, it will appear in the "insights panel" on the right panel of the feature you linked it to. From there, you can also create insights manually.
Create an insight manually
You can hover over the highlighted piece of text in the feedback, the insights panel will scroll right to the corresponding insight.
Insights are always linked to a parent doc type which is one of your product Features.
You can't edit an insight's customer once the insight is linked to a Feature. If you need to edit an insight's customer, you'll have to do so at the feedback level. The insight will automatically get updated.

Feedback content as quote

Sometimes, the feedback content is clear and explicit ; in this case all you want is to capture it all as a quote.
Within any piece of feedback, simply click on "Add Insights" and select "Use feedback content as quote" to use the full content in your insights.

Leverage your insights

Insights bring your users' voices into your documents.
Get in a second which company gave this feedback with the logo.
Here are the most common actions you can do with insights:
  • Go back and forth between sources (feedback) and Features u by clicking on insights on the right panel
  • Show more to get the full content
  • Copy quotes in your PRD
  • Copy emails to send updates to customers
  • Edit quotes to correct typo
  • Have a cover
  • Edit properties
Have a look at the Arcade below to discover how.

Bulk update insights

Want to split a Problem into Features and roll down insights from one to the others?
Tip: To select Hit X while hovering Insights, Cmd+A, or tick them one by one.

Copy or export all insights

You can now all quotes from the right-side panel. This makes it easy to compile, summarize, and incorporate your insights into your PRDs.

Create new views

A view is a filtered and structured way to visualize your Cycle Insights. They can take a kanban or list shape and be filtered on or grouped by properties.
Here's an example of a view with all "Small" Features grouped by "Status". The idea is the same to create new Insights views.
Only "Makers" can create views. If you are the first to join yourn workspace, you're a "Maker" by default. If not, ask a Maker to change your role.
In an insight view, you'll see the content of the insights, no matter whether they have a title.
This means you can see customer quotes, essential pain points, and other key information right away, in your insight view.
Customer voice

Some use cases

👉 Feel the importance of the pain for certain features you are working on
👉 Check the status of different insights shared by specific clients
Now that you're familiar with creating Insights from feedback and linking them to features, let's learn how to prioritize features and write your PRDs 👀.