Guide
What are Highlights?
A Highlight usually represents a fact, a piece of useful data.
Highlight is a special connection that captures some information from rich text field in a source entity and links it to a target entity. For example, here we capture some interesting fact from a user Interview and connect it to a product Component.
You can capture and augment some text with additional information, like highlighting severity or urgency. Highlight above can be visualised on Whiteboard View like this:
Highlights linked to a target entity are visible inside this entity. For example, the Reporting Component has all linked Highlights, so you can read them and update them (like change the Severity field, or even re-connect to some other target entity):
Why you may need Highlights?
Highlights help to capture and accumulate information/facts about something, and later it will be easier to make decisions and answer specific questions. For example, if we take product feedback management, here are the questions you will be able to answer:
What are the top problems in the product?
What to focus on next in specific product area?
What some specific customer wants?
What our target customers asked for recently?
What we should build for some specific market?
For example, here we accumulate leads and customers feedback about open problems and features, and calculates priority score based on feedback volume, customer size and segment, feedback pain level:
The most common use cases for Highlights are:
Product feedback management. Here you capture facts from Intercom chats, customer calls, and connect them to product features or areas.
User research. Here you capture observations from user interviews, and connect them to insights or problems.
Market research. Here you capture information about market from web posts, newsletters, and connect it to niches, opportunities, etc.
How to setup Highlights
Navigate to Settings → Highlights, here you should already see Highlight database created. If not, you can add Highlight database.
If you already used References to link information between text and databases, you might need to migrate from references to highlights. Check References to Highlights guide then.
In the left there are all Sources databases (you will review them and capture information here), on the right there are all Target databases (where you want to accumulate facts).
Highlight database is connected via Relations to several sources and several targets. It means, essentially, that Highlight database uses multi-relations. Single Highlight entity always has exact source entity and exact target entity.
https://youtu.be/eqBfy8dnK7E
Multiple Highlight databases
You can create and manage multiple Highlight databases and change their names and colors, just like any other database in Fibery. The only restriction is that you cannot set the same source in different Highlight databases. However, there are no restrictions for Highlight targets.
This can be helpful if you want to utilize the Highlight functionality in various scenarios.
How to capture Highlights
There are several ways to capture Highlights:
Manually, in Source entity (like open an Interview and create Highlights from text)
Using AI in Source entity
Using AI in Target entity (like open some Feature and find new Highlights related to this Feature)
Check Find Highlights (manually and with AI help) guide.
How to visualize Highlights
Highlights is a database, so you can create Views and work with Highlights as with usual databases.
Using Highlight database views
How to setup formulas for Highlights and Targets
You can use Highlights to calculate Features or Insights prioritization score.
Highlights and Targets formulas
Empty Highlight Suggestion
It can happen that the Highlight Suggestion does not find relevant matching content. Instead of giving a "No matching found" error message, we try to provide some clues on how you can increase the chance of getting matching suggestions.
For example, during the X-wing user test interviews, someone interviewed Indiana Jones. Thus, it is unsurprising that our incredible AI was unable to find any correlation between the X-wing user interview questions and the Indiana Jones story. But now you know why…