With Insights collections rolling out, it seemed like the perfect time to introduce new filters you can use to define them!

New filter types

Title

Filter based on text contained, or not contained, within a note's title.

Values:

  • Contains
  • Does not contain

Content

Filter based on text contained, or not contained, within the content of the note's description field.

Values:

  • Contains
  • Does not contain

Status

Filter based on note status.

You can define your own custom inboxes by incorporating the unprocessed status filter with other types of filters when defining a collection.

Values:

  • Processed
  • Unprocessed
  • Archived

Processed by

Filter notes based on who processed them. (Notes not yet processed will never be returned.)

Values:

  • {Member}: Individual member in your workspace
  • {Team}: All members of a team in your workspace (e.g. Support team)

Created by

Filter notes based on who created them.

Values:

  • {Member}: Individual member in your workspace
  • {Team}: All members of a team in your workspace (e.g. Customer success team)

Followed by (individual member, or all members of a team)

Filter notes based on who is following them.

Values:

  • {Member}: Individual member in your workspace
  • {Team}: All members of a team in your workspace (e.g. Leadership team)

Insight importance

Filter notes based on characteristics of the highlighted insights they contain.

Values:

  • Critical — One or more insights with a 'critical' importance value
  • Important — One or more insights with an 'important' importance value
  • Nice-to-have — One or more insights with a 'nice to have' importance value
  • Unknown — At least one insight, but none with an importance value set
  • Notes without insights

Segment

Filter notes based on characteristics of the user the note is attributed to — specifically, by segment.

Values:

  • {Segments users have been assigned to in your workspace}

Hierarchy

Filter for notes containing one or more insights linked to a certain area of your product. In the example pictured, that would include all insights linked to the selected component as well as its underlying features.

The Hierarchy filter can come in handy when you want to review all insights related to a certain product area within their original context. (As opposed to a component's Insights tab in the side pane where only highlighted insights are shown.)

This filter can also be helpful for staying on top of recent insights your colleagues have linked to your product area. (Try combining it with the Processed by filter to review those notes colleagues may have processed for you.) Beyond reviewing the insights themselves, you’ll be able to provide feedback to colleagues on how best to tag and link similar insights in the future.

Did this answer your question?