Skip to main content

Organize your product space with Components

Structure your product backlog into areas, themes, or teams.

Written by Marina Salmon

What is a Component?

Components let you organize your product backlog into areas, themes, or teams. They contain your Discoveries — the product opportunities and ideas you explore and prioritize.

You can nest multiple levels of Components and sub-Components to mirror your product's hierarchy. They're accessible from the left navigation bar in the Product section.

Components are mutually exclusive. A Discovery belongs to exactly one Component. This is deliberate — Components are the backbone of your product organization, so an opportunity has one home rather than several.

If you need a Discovery to appear across several axes, use tags or fields instead.

How to organize your Components

The right structure depends on how your products and teams are already organized. Some common approaches:

  • By product area — Onboarding, Home, Dashboard, Settings

  • By product team — one Component per squad

  • By objective — Acquisition, Activation, Retention

Here are three real examples, from us and from our customers.

The Harvestr example

We organize our Components around our main product areas and Jobs-to-be-Done: Feedback, Integrations, Discovery, and so on.

We added a Transversal Component for opportunities that don't belong to any single area, and a Competition Component where we centralize every piece of feedback comparing us to competitors — a useful way to see our strengths and weaknesses in one place.

We deliberately kept the hierarchy simple, with a single level of sub-Components.

An international online bank

A bank operating in several countries could use one top-level Component per country, given the differences in user experience and regulation, with sub-Components for product areas underneath.

A CRM software company

A CRM vendor could organize top-level Components by persona, since each persona experiences the product differently and has access to different features. Alongside those, a Component for integration requests and another for product growth experiments.

Start simple. One or two levels is enough to begin with. A structure you have to think about before filing something is a structure nobody will use. You can always refine later.

Create Components

Use the Add component button at the bottom of your Components list.

Create sub-Components

Add sub-Components inside an existing Component to go one level deeper.

Edit and delete Components

Click a Component's name in the upper section to open its settings, where you can rename or delete it.

Add Discoveries to a Component

Discoveries always belong to a Component or sub-Component. You can create one either from the Product section, by clicking New inside the Component, or directly from a piece of feedback in your inbox.

Both routes are covered step by step in Turn feedback into product opportunities with Discoveries.

Where to go next

Did this answer your question?