Lesson 3: Find the pattern

A theme is a cluster of related feedback that reveals a pattern. It's the bridge between raw signals and anything you'd actually build.

Why themes exist

Without themes, you process feedback like a support queue: one ticket, one fix, repeat. That treats every symptom as its own disease. With themes, ten "can you add export?" requests collapse into one named problem (people can't get their data out) and you fix the cause once.

Themes also stop the loudest-voice problem. One enterprise customer asking five times feels bigger than five quiet users asking once each. A theme counts the actual signals.

What makes a good theme

• Named for the problem, not the solution. "Data is trapped in the app" beats "Add CSV export", the second forecloses better answers (an API? scheduled email reports?).
• Backed by linked feedback. A theme with zero linked signals is an opinion wearing a theme costume.
• Alive. Themes have statuses (emerging → active → mature) and trends, they grow as more signals attach.

Do it now

Open Themes and group the feedback you captured in Lesson 2:

1. Create a theme and name the underlying problem in plain words.
2. Link your related feedback items to it.
3. Or let the machine try first: on Feedback, run ProductSense → Suggest missing links. It proposes an existing theme for each unthemed row, or a new one with a draft title, you stay the editor.

One theme is enough. You now have the raw material for a feature decision.