---
title: "Taxonomy and themes"
canonical_url: https://zentrik.ai/docs/product/taxonomy-and-themes
markdown_url: https://zentrik.ai/docs/product/taxonomy-and-themes.md
category: "Product guides"
learning_track: "discovery"
last_reviewed: 2026-03-28
---

# Taxonomy and themes

**Taxonomy** is the labeling system **you** define: dimensions such as product area, segment, or severity, with values your team agrees to use. Use it for **filters and rollups** leadership can trust.

**Themes** are **semantic** groupings from the language in your evidence. They can nest (**sub-themes**) so you can browse how topics cluster without adding every phrase to the taxonomy.

## Overview

Import a few items first so you have real insights to work with ([Evidence → insights](https://zentrik.ai/docs/product/evidence-to-insights)). **Admins** configure dimensions in the product; this guide explains what PMs and leads should expect.

Rich **workspace context** (products, OKRs, personas, docs) helps classification suggestions match how your company works. Details: [Workspace context](https://zentrik.ai/docs/product/workspace-context).

## Taxonomy and themes

Use **taxonomy** when you need stable answers: “everything tagged Enterprise,” “rollup by surface,” quarter-over-quarter counts.

Use **themes** when you want to **explore**: what customers keep saying, how wording clusters, which subtopics sit under a broader pain. Themes update as language in your corpus changes.

The **same map** can show taxonomy colors or theme navigation. Pick the lens that matches the conversation: **reporting** vs **exploration**.

## Building your taxonomy

Dimensions apply to **insights**, **ideas**, and **opportunities** in your workspace. Each dimension can be **free text**, **single-select**, or **multi-select**, depending on how tight you want the vocabulary.

Describe each dimension in plain language. That text is part of how Zentrik suggests values when you classify.

You can start small: a few fields that match questions leadership already asks, then add or refine dimensions as imports grow.

## AI classification

Zentrik suggests taxonomy values using **your definitions and allowed values** plus **workspace context** (personas, products, OKRs, KPIs, features, narrative notes). Reviewers **accept, edit, or clear** suggestions on each record.

On an **insight**, classification appears **on the detail view** so you can adjust labels without leaving the card.

For ongoing curation of the insight layer itself (merge, link to older cards), see [Evidence → insights](https://zentrik.ai/docs/product/evidence-to-insights).

## Preview and bulk refresh

When you change dimensions or guidance:

1. **Adjust** the taxonomy or add context in the workspace so suggestions have better grounding.
2. **Try** settings on a limited set of records and inspect proposed labels.
3. **Preview** on a subset until PMs and admins agree on the behavior.
4. **Run bulk refresh** across insights, ideas, or opportunities when you want the whole corpus updated (for example after a taxonomy cleanup or reorg).

Many teams stay in preview and per-record review for a while before running bulk jobs. Match the pace to your review process.

## Maps and rollups

Maps, sidebars, and distribution charts reflect **current** labels and evidence. They change when new **insights** arrive, **signals** add quotes, you **edit** labels, you **bulk-refresh**, or theme clustering runs again.

Use the map in working sessions: filter by taxonomy for rollups, open **themes** to explore language, then capture agreement in **opportunities** when the team is ready ([Insights → opportunities](https://zentrik.ai/docs/product/insights-to-opportunities)).

If your workspace **requires review** before items appear in certain views, finish those steps so rollups include the cards you expect.

## Troubleshooting

### Map looks empty after import

Wait for processing on the **signal**. Check **review** or **intake** queues if your workspace hides unapproved items from some views. [Evidence → insights](https://zentrik.ai/docs/product/evidence-to-insights).

### Teams disagree on labels

Write a **one-line example** per dimension (what “P1” means here). Align on **opportunity** framing before renaming many dimensions. Use **preview** before a large **bulk** run.

### Leadership quoted a theme name like a formal metric

**Taxonomy** values are **defined and owned** by your workspace. **Themes** describe **how language clusters**. If a theme should become official, add it to taxonomy; if not, keep it as exploration-only language in decks.

## Related guides

- [Discovery: from insights to opportunities](https://zentrik.ai/docs/product/insights-to-opportunities)
- [Use Studies to learn throughout an initiative](https://zentrik.ai/docs/product/idea-studies)
- [Bring customer evidence into Discovery](https://zentrik.ai/docs/product/evidence-to-insights)