Customer Feedback Taxonomy

Standardized tagging schema for personas, lifecycle stages, drivers, and sentiment.

Published by @gtmagents·0 agent reads / 30d·0 saves·

Customer Feedback Taxonomy Skill

When to Use

  • Normalizing surveys, interviews, support logs, or community chatter before synthesis.
  • Auditing existing VoC datasets for drift or inconsistencies.
  • Onboarding new teams to shared tagging standards.

Framework

  1. Persona Layer – map ICP, role, and influence level.
  2. Lifecycle Layer – awareness, onboarding, adoption, expansion, renewal, advocacy.
  3. Driver Layer – product, service, pricing, experience, relationship, outcomes.
  4. Sentiment Layer – strength, urgency, confidence, sample size.
  5. Metadata Layer – ARR, region, industry, channel, last touch.

Templates

  • CSV/Sheet taxonomy with dropdowns and validation rules.
  • JSON schema for tagging automation or webhook ingestion.
  • Governance checklist for quarterly taxonomy refresh.

Tips

  • Keep taxonomy lean (<30 drivers) to encourage adoption.
  • Version every change so historical analyses remain comparable.
  • Pair with run-voc-listening-tour to auto-tag new signals.

More on the bench

SKILL0

Knowledge Management

Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.

customer-success+2
0
SKILL0

Customer Research

Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.

customer-success+1
0
SKILL0

Launch Readiness

Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.

product-management+2
0