China Voice of Customer Analysis Template
Use a China voice of customer analysis template to preserve source language, code evidence consistently, compare segments and platforms, and turn themes into testable actions.
- VERSION
- 2.0.0
- UPDATED
- 2026-08-01
- LICENSE
- MIT
- FILES
- 04
npx skills add fffffrost/market-skills --skill voice-of-customer-synthesisPreserve the customer's words before you compress the pattern.
VOC synthesis becomes unreliable when quotes lose their source, loud channels stand in for the market, or themes are named before coding. Keep original language and context attached, compare patterns across segments, and show how much evidence supports each decision.
Define the decision
State what the analysis must inform, the target segment, time window, included sources, exclusions, and sampling limits.
Which decision will this evidence change?Preserve source context
Retain original Chinese wording, date, channel, segment, journey stage, consent or access status, and stable source reference.
Can a reviewer return to the original context?Apply a consistent codebook
Code jobs, triggers, pains, desired outcomes, objections, alternatives, language, intensity, and evidence quality.
Would another reviewer assign the same code?Compare before merging
Separate roles, regions, customer stages, channels, and source types before describing an overall pattern.
Where does the pattern hold, and where does it break?Build evidence-backed themes
Attach representative quotes, counterexamples, frequency, intensity, coverage, confidence, and material unknowns.
Does each theme have support and a visible limit?Convert insight into a test
Map themes to messaging, product, content, sales, or research actions with owners and validation signals.
What can the team test instead of merely believing?CHINA VOICE OF CUSTOMER ANALYSIS TEMPLATE
DECISION AND SAMPLE
Decision to inform:
Priority segment:
Time window:
Included sources:
Exclusions:
Known sampling bias:
SOURCE RECORD
Source ID | Original wording | Date | Channel | Segment | Journey stage | Context / access
CODEBOOK
Job / desired progress:
Trigger:
Pain / friction:
Desired outcome:
Objection / risk:
Alternative:
Customer language:
Intensity / evidence quality:
THEME TABLE
Theme | Supporting sources | Counterexample | Coverage | Confidence | Unknown
SEGMENT COMPARISON
Segment / region / stage | Shared pattern | Difference | Implication
ACTION MAP
Theme | Messaging / product / sales / research action | Owner | Test | Signal
REVIEW
Reviewer disagreement:
Missing voices:
Next research need:
Decision date:Four safeguards against turning comments into folklore.
This is a research pattern, not a representative China consumer finding. Production analysis must disclose sample and access limits.
Keep original wording, channel, date, role, and journey stage attached to every excerpt.
State which voices are overrepresented, absent, or inaccessible before generalizing.
Show frequency, intensity, coverage, and contradictory evidence instead of selecting only vivid quotes.
Turn the theme into a message, research, product, or sales hypothesis with a decision owner.
- Chinese research materials
- Source metadata
- Audience segments
- Decision question
- Evidence-backed themes
- Verbatim quotes
- Segment differences
- Action matrix
Know where the workflow must stop.
- Cannot generalize a small or convenience sample to the China market
- Does not replace quantitative research or continuous social listening
- Must not process personal data without an appropriate basis
These conditions distort the result.
- Translation removes the original customer wording before analysis
- Platform audience and customer stage are mixed into one theme
- Findings are counted without preserving source and sampling boundaries
How the skill works
- 01Define the China decision
- 02Preserve source and language context
- 03Code observations
- 04Compare platform and segment patterns
- 05Build evidence-backed insights
- 06Convert insights into tests
Inspect the source before installing.
Instructions, templates, compatibility, and dependencies remain in one open directory.
- ├─SKILL.md
- ├─agents/openai.yaml
- ├─listing.yaml
- ├─references/voc-template.md