FREESKILL v1.0UPDATED 2026-08

Voice of the Customer

Voice of the Customer becomes decision material only when corpus coverage, privacy, themes, disagreement, evidence strength, and follow-through remain connected.

Anecdotes become dangerous when a small or biased sample is retold as what customers want. The loudest note can hide missing channels, opposing evidence, and the difference between a pain point and a feature request.

This playbook defines the corpus, protects identifying data, codes each item, preserves disagreement, and assigns a bounded disposition. It reports what the supplied feedback says without pretending the corpus represents the entire customer base.

The readout represents the corpus you have, not every customer you serve.

SIGNALS YOU NEED THIS

A theme has no item count, source mix, or opposing evidence.

One request is treated as a roadmap commitment.

Customer identities appear where the decision only needs the signal.

REPLACES

Anecdote ranking, false consensus, and feedback summaries that end before a decision or loop close.

PAIRS WITH

Working Backwards, Prioritization Formula, Successful Meetings, and Changelog.

0 of 4 steps complete

STEP 01Define and protect the corpus

Record the period, scope, source types, item count, and blind spots. Remove names, contact details, account identifiers, and private facts the decision does not need.

CORPUS
  Period: July
  Items: 6
  Sources: support 3, interviews 2, sales 1
  Customer scope: supplied anonymized items only
  Missing coverage: segments not supplied

STEP 02Code items without changing their meaning

Assign source, feedback type, topic, segment when supplied, and evidence strength. Keep pain points, requests, praise, pricing concerns, and experience reports distinct.

THEMES
  Export controls hard to find: pain point, 2 support items
  New search praised: praise, 1 support item
  Saved views: request, 2 interview items
  Approval history: request, 1 sales item

STEP 03Measure honestly and preserve disagreement

Count items and source coverage without converting them into prevalence. Keep opposing evidence and outliers visible when they change interpretation.

SETUP EVIDENCE
  Confusing: 2 supplied comments
  Easy: 1 supplied comment
  Conclusion: mixed evidence in this corpus
  Prevalence across customers: not established

STEP 04Choose a bounded disposition and close the loop

Use Act now, Investigate, Monitor, or No action. Explain the evidence and uncertainty, then give each action and loop-close step an owner and date without assuming the readout owner owns everything.

DISPOSITION
  Saved views: Investigate
  Reason: two interview requests, no broader coverage supplied
  Action owner: Owner needed
  Due: Date needed
  Loop-close owner: Owner needed

Download the folder into your agent's skills directory. It uses only the material you provide and makes no remote calls.

skills/voice-of-the-customer

voice-of-the-customer/
├── SKILL.md                         ← synthesize and audit modes
├── meta.yaml                        ← version, sources, test prompts, changelog
├── LICENSE.md                       ← MIT
├── assets/
│   ├── voc-readout-template.md      ← corpus, themes, and dispositions
│   └── voc-audit-scorecard.md       ← evidence and coverage audit
└── references/
    ├── coding-and-signal-guide.md   ← feedback coding and confidence
    └── decision-and-loop-guide.md   ← dispositions and loop closure

INVOKE IT LIKE THIS

"Synthesize this customer feedback into a VOC readout."

Download skill v1.0 View source files

WORKS WITHClaude Code