Themes

Themes are aggregations of feedback. They make the question "what are users saying together?" answerable without re-reading 500 rows.

What you'll see

• Lifecycle strip: per-status counts above the table; click a node to narrow to that status, click again to clear
• Theme list: title, ID, status, trend chip, feedback / feature / initiative counts, personas, created date, description; sorted by feedback count by default
• Filter bar: status (new | emerging | active | mature | archived; the API also accepts under-review | planned | in-progress), trend direction, created date, persona

Row drawer

• AI-generated description (re-runnable on demand)
• Status, trend and weekly growth, editable in place
• Linked feedback
• Linked features and initiatives (downstream)
• Linked personas (who experiences it)

Common actions

• ProductSense button in the toolbar for cross-theme cleanup (the m shortcut is bound on the Feedback page only)
• The standard entity-context shortcuts apply once a row has focus: ⌘O open details, ⌘I ask Copilot, N F create a feature linked to the theme, L link to existing, A assign team member

Trend chip semantics

The trend column is one of up | stable | down | growing | declining. The weekly_growth column is the underlying numeric. Both are values you set, in the drawer or through the API; nothing computes them automatically, so treat the chip as a directional signal rather than a precise number.

Data flow

Created manually, from ProductSense link suggestions, or through the API. The theme_feedback junction carries an optional confidence score per match (settable through the API; the UI doesn't show it); the theme_features junction connects themes downstream to features, and theme_personas records who experiences them.

Related

• Themes API reference
• Feedback page: upstream
• Features page: downstream