Productboard Expert

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 sits between customer-feedback intake (Slack/Intercom/Salesforce/email) and the engineering tracker (Jira/Linear), with an opinionated three-layer model that differs meaningfully from generic issue trackers.

Overview

Productboard separates three layers: Insights (inbound customer evidence), Features (candidate product changes organized in Components and parent/child hierarchy), and Drivers + 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. The flow is inbox → triage → prioritize → ship.

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 company strategy, and write API automations for what the UI does not cover.

Core Capabilities

• Workspace & hierarchy setup — Components, Feature taxonomy, Tags, custom fields, roles
• Insight inbox triage — the highest-leverage daily ritual; verbatim discipline, multi-Feature linking
• Driver configuration & Feature scoring — 3-5 weighted Drivers, composite scoring, quarterly re-weighting
• Releases & Roadmap views — time-boxed delivery, audience-specific views, Portal for customers
• REST API automation — bulk Insight/Feature operations, webhooks, custom-field updates, pagination
• Two-way integration — Jira/Linear/Azure DevOps (Features↔Epics) and Salesforce/HubSpot/Intercom/Zendesk (Insight capture)

When to Use

• Setting up a new Productboard workspace, Component hierarchy, or 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 or CRM customer sync
• Building Roadmap views for executives, customers, and internal teams
• Writing API calls to bulk-create Insights, update Features, or read prioritization data
• Migrating from spreadsheet-based prioritization, or troubleshooting "Insights aren't flowing", "scores aren't updating", and similar workflow failures

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

• references/operations-playbook.md — concepts (data model, three layers, Importance×Evidence), all 9 core workflows (setup, triage, Drivers, scoring, Releases, integrations, capture, bulk ops), inline API call catalog, best practices, troubleshooting table, and success criteria. Read this for any setup, triage, scoring, or API task.
• references/productboard-api-patterns.md — full REST API call catalog with curl examples and JSON shapes. Read when scripting against the API.
• references/productboard-vs-jira-vs-linear.md — when to use Productboard alongside (or instead of) Jira/Linear; concept translation. Read when positioning the tool in an existing stack.
• references/red-flags.md — common ways this skill's output goes wrong, with fixes. Read before finalizing a workspace design or prioritization recommendation.
• Assets: assets/productboard-feature-template.md (Feature structure), assets/productboard-insight-triage-workflow.md (daily triage SOP), assets/productboard-driver-template.md (Driver definitions). Official docs: https://developer.productboard.com/ · https://help.productboard.com/

Scope & Limitations