Theme

A cluster of related customer signals that share an underlying need or root cause, used as the unit of prioritization once raw feedback has been synthesized.

A theme is the synthesized unit a product team acts on, sitting one level above raw customer signals. A single complaint that "the export is broken" is a signal. Forty complaints across thirty accounts about exports — slow, missing fields, broken on large datasets, no Excel format — is a theme. The theme captures the shared underlying need; the signals are evidence of it.

Themes are the right granularity for prioritization because they're large enough to justify engineering investment and specific enough to suggest what the work looks like. A roadmap built on raw signals would have thousands of items; a roadmap built on outcomes would have five. Themes — typically a few dozen active at any time — sit in the middle.

The hard part is the split test: when do two signals belong to the same theme, and when are they different problems requiring different fixes? The honest test is whether a single engineering change would resolve both. If the same fix wouldn't address them, they're different themes — even if the language sounds similar, even if both customers complained on the same day. Conflating them produces themes too coarse to act on; over-splitting produces themes too small to bother with.