2 min lesson
Define a consistent taxonomy
Explain your answer to "Why is defining a fixed tagging taxonomy before ingesting signal more important than at lower volume?" Add one concrete detail from the lesson.
Step 1 of 2
Define a consistent taxonomyso signal is comparable across channels
A theme is only countable if the same thing is tagged the same way everywhere. Pin a small, fixed vocabulary down before you ingest a single item, because retrofitting tags onto thousands of historical reports is the kind of cleanup that kills VoC programs.
- Feature area
- Tab, Agent, ⌘K, chat, indexing, models, billing - match the product's real surfaces, not vague buckets
- Severity
- Data loss / security / outage at the top, cosmetic at the bottom - drives what jumps the queue
- Sentiment
- Frustrated, confused, churning, delighted - lets you watch the emotional trend, not just volume
- Theme
- The cross-cutting label that survives ('Agent edits the wrong file') - this is what you brief on
Keep the list short. A taxonomy nobody can apply consistently is worse than none.
Every design choice - sources, tags, cadence, tooling - should be justified by whether it makes the weekly brief sharper. If a step doesn't improve the artifact leadership reads, cut it. That framing alone separates a systems-builder from a ticket-closer.
When asked "how would you set up VoC here," resist listing tools. Sketch the pipeline end to end in 60 seconds - sources in, taxonomy applied, agent-assisted clustering, human review, weekly brief out, loop closed - then say which piece you'd build first and why. Naming the first brick shows you've actually shipped one of these before.