productboard-expert

What this skill does

# Productboard Expert

Master-level expertise in Productboard workspace configuration, Insight inbox triage, Driver-based prioritization, Feature hierarchy management, Releases and Roadmap views, REST API operations, and two-way integration with Jira, Linear, Azure DevOps, Salesforce, Intercom, and Slack. Productboard is one of the top dedicated PM tools (alongside Aha! and ProductPlan); PMs adopting it benefit from a structured guide because the data model and prioritization mechanics differ meaningfully from generic issue trackers.

## Overview

Productboard sits between customer-feedback intake (Slack/Intercom/Salesforce/email) and the engineering tracker (Jira/Linear). Its strength is the explicit separation of three layers:

1. **Insights** — the inbound customer evidence (a sales note, a support ticket comment, an interview quote).
2. **Features** — the candidate product changes, organized in a hierarchy of Components and parent/child Features.
3. **Drivers and Releases** — the prioritization framework (Drivers = weighted criteria, Releases = time-boxed delivery groupings).

Insights link to Features (many-to-many); Features score against Drivers; high-scoring Features get added to Releases; Releases push down to Jira/Linear epics and stories. The flow is **inbox → triage → prioritize → ship**, and Productboard is opinionated about each step.

The job of a Productboard expert is to operate fluently inside this model, configure the workspace cleanly, run the Insight inbox without backlog, design Driver weightings that match the company's strategy, and write API automations for the workflows the UI does not cover.

### When to Use

- Setting up a new Productboard workspace or onboarding a new team
- Designing the Component hierarchy and Feature taxonomy
- Configuring Drivers and weighting them against strategic objectives
- Running the Insight inbox triage workflow (the highest-leverage daily ritual)
- Configuring two-way Jira/Linear/Azure DevOps integration
- Building Roadmap views for executives, customers, and internal teams
- Writing API calls to bulk-create Insights, update Features, or read prioritization data
- Integrating with Slack/Intercom/Salesforce/Zendesk for Insight capture
- Migrating from spreadsheet-based prioritization to Productboard
- Troubleshooting "Insights aren't flowing to Features", "scores aren't updating", and similar workflow failures

## Concepts

### Data Model

| Entity | Purpose | Key fields |
|---|---|---|
| **Workspace** | Top-level account; one company has one workspace | `name`, `plan_tier`, `members[]` |
| **Product** (legacy) / **Workspace** | Top-level container in some plans | varies |
| **Component** | Hierarchical grouping for Features (e.g. `Reporting > Dashboards > Filters`) | `id`, `name`, `parent_id` |
| **Feature** | The atomic prioritization unit; can have parent and child Features | `id`, `name`, `description`, `status`, `component_id`, `parent_id`, `tags[]`, `custom_fields` |
| **Insight** (also called "Note") | An inbound customer evidence item; lives in the Insights inbox until linked to Features | `id`, `title`, `content`, `source`, `customer{}`, `tags[]`, `feature_links[]` |
| **Customer** | A profile that can be associated with Insights and Companies | `id`, `email`, `external_id`, `company` |
| **Company** | An account-level grouping of Customers (typically pulled from CRM) | `id`, `name`, `mrr`, `segment` |
| **Driver** | A weighted prioritization criterion (e.g. "Revenue Impact", "Strategic Fit", "Customer Demand") | `id`, `name`, `weight`, `scoring_scale` |
| **Objective** | A strategic theme; Features can be linked to Objectives | `id`, `name`, `time_horizon` |
| **Release** | A time-boxed grouping of Features for delivery planning | `id`, `name`, `start_date`, `end_date`, `feature_ids[]` |
| **Release Group** | A category of Releases (e.g. "Q3 2026") | `id`, `name`, `release_ids[]` |
| **Roadmap view** | A saved configuration of Features filtered and grouped for presentation | UI construct |
| **Custom field** | User-defined Feature attribute (single select, multi-select, number, text, date) | `id`, `name`, `type`, `options[]` |

### Insights vs Features vs Drivers — the three layers

The mental model that makes Productboard click:

```
INSIGHTS (evidence)          FEATURES (candidates)         DRIVERS (criteria)
─────────────────            ──────────────────            ──────────────────
Slack message    ──┐
Salesforce note  ──┼──link──> Feature: "Shareable read-only link"  ──score──>  Revenue impact: 8/10
Intercom thread  ──┤                                                            Strategic fit:   7/10
NPS verbatim     ──┘                                                            Cust demand:     9/10
                                                                                ─────────
                                                                                composite: 8.1
```

Insights are evidence; Features are decisions; Drivers are the scoring system. The Insight-to-Feature link is the system's most important relationship: it lets the team answer "how many real customers asked for this and who are they?" with a click.

### Importance × Evidence

Productboard's Driver scoring is a 2D model: each Feature gets a score (Importance) per Driver, and each Driver has a weight. The composite Feature score is the weighted average.

Evidence (linked Insights) is the supporting data; it does not directly compute the score but is visible alongside the score for context. A high score without supporting Insights is a flag — the team is prioritizing based on opinion rather than evidence.

## Core Workflows

### 1. Workspace and Hierarchy Setup

1. Create the workspace. Set timezone, locale, currency.
2. Invite members; assign roles (Admin, Maker, Contributor, Viewer). Roles in Productboard are global; team-level restrictions come via Features access controls (paid tiers).
3. Define the **Component hierarchy** before adding Features. Common patterns:
   - By product area: `Reporting`, `Onboarding`, `Integrations`, `Billing`, `Platform`
   - By customer journey: `Acquisition`, `Activation`, `Retention`, `Expansion`
   - By team ownership: maps Component to engineering team — useful if engineering teams are stable, fragile if reorgs are frequent.
4. Decide on **Feature naming convention**. Avoid embedding solutions in names. Prefer "Shareable read-only dashboard view" to "PDF export button".
5. Create **Tags** for orthogonal attributes (e.g. `customer-segment/enterprise`, `effort/L`, `theme/AI`).
6. Create **Custom fields** for anything that doesn't fit Tags. Common custom fields: T-shirt size, Engineering owner, Design owner, External ticket ID.
7. **HANDOFF TO**: team leads to start populating Features and linking Insights.

### 2. Insight Inbox Triage (daily ritual)

Productboard's Insight inbox is the central inbound surface. Untriaged Insights pile up quickly if there's no daily ritual.

**Daily inbox triage** (one PM, ~15 minutes):

1. Filter the inbox to "Not yet processed" Insights.
2. For each Insight:
   - **Read the verbatim**. Resist paraphrasing.
   - **Link to one or more Features**. If a matching Feature doesn't exist, create one.
   - **Tag with relevant attributes** (customer segment, theme, source).
   - **Mark "processed"**.
3. If an Insight doesn't map to a Feature within 60 seconds, park it in the "Needs discussion" view and come back to it in the weekly review.

Anti-pattern: creating one Feature per Insight. This explodes Feature count and dilutes scoring. Multiple Insights should commonly map to the same Feature.

See `assets/productboard-insight-triage-workflow.md` for a full SOP.

### 3. Driver Configuration

Drivers are how the team's strategy becomes scoring weight. Configuration steps:

1. Decide on 3-5 Drivers. More than 5 Drivers becomes noise; fewer than 3 gives insufficient resolution.
2. Common Driver sets:
   - **General SaaS**: Revenue Impact, St