What is a Discovery?
Once your product feedback is centralized, Harvestr helps you organize it into something you can act on.
Discoveries are the customer problems and product opportunities you want to explore. A Discovery can be a feature request, a recurring pain point, or an idea you want to validate against real user feedback.
Each Discovery gathers all the feedback about the same topic in one place, so you stop reading individual messages and start seeing patterns.
What a Discovery holds
Title and description
Comments from your team
A state — where this opportunity sits in your workflow
A component — the product area it belongs to
An assignee
Roadmap projects it's linked to
User and company segments — derived from the customers whose feedback is linked here
Tags, to group Discoveries under common themes or priorities
Fields, to qualify and compare opportunities
Linked issues from Jira, Linear, Trello, GitHub or GitLab
Feedback, added from your inbox or directly inside the Discovery
Customers — every user and company whose feedback is linked here
Activities, a log of every change made
Discoveries are organized in Components, accessible from the left navigation bar.
Create Discoveries
A Discovery always belongs to a Component. There are two ways to create one.
From the Product section
Go to the Component where you want it, using the left navigation bar, then click New above the list of Discoveries.
From feedback in your inbox
When you open the categorization popup on a piece of feedback, hover over a Component's name and click the + button to create a Discovery there.
Give it a title, press Enter, and the feedback you selected is linked to the new Discovery straight away.
Add feedback to a Discovery
Two ways, both from your inbox:
Select part of a piece of feedback and link just that extract
Or click "Link to" at the top to link the whole item
Most of this happens automatically. HAI suggests the right Discovery for each new piece of feedback, and you review its suggestions rather than categorizing everything by hand.
Discovery states
Discoveries evolve across your product's life cycle. Some get discarded, others become features. States are how you track where each one stands.
States are fully customizable, and each one belongs to one of three categories:
Unstarted | Opportunities you haven't committed to yet |
Started | Work underway, from discovery through development |
Completed | Shipped |
The category matters more than the name: it's what drives roadmap project progress, and what your customers see as status on a public roadmap. Name the states whatever fits your team.
Qualify and group Discoveries with tags
Tags add context to a Discovery and let you track themes across your backlog. Add them right below the Discovery's title.
Order and prioritize Discoveries
Inside each Component you get the list of its Discoveries. Sort that list to surface what's urgent — by name, state, creation date, last feedback date, feedback volume, or any field you've set up.
Click the sort button again to switch between ascending and descending.
For example, to find your most-requested integrations: open your Integrations Component and sort by feedback volume, descending.
Save the filter and sort combinations you use often as Discovery views, so you don't rebuild them every time.
Sub-discoveries
Sub-discoveries help you map problems and sub-problems, or problems and the potential solutions that could address them.
Sub-discoveries nest one level deep. A sub-discovery can't itself have sub-discoveries.
Adding feedback to sub-discoveries
Sub-discoveries appear in your table and board views, and you can link feedback to them from your inbox and from the Chrome extension, Slack, Intercom and Zendesk.
Prioritizing with sub-discoveries
When a Discovery has sub-discoveries, three things roll up to the parent so you can prioritize the problem as a whole:
feedback volume
user and company segments
