Voice of Customer (ECHO Framework)
Design a Voice-of-Customer program that turns raw feedback into routed, prioritized, evidence-backed actions - not a quarterly NPS report nobody reads. ECHO replaces ad-hoc surveys with a multi-source signal pipeline that PMs, CS, and marketing all rely on.
Core Principle
VoC fails when it conflates collection with insight. A survey isn't a program. ECHO standardizes how signal is elicited, themed, prioritized, and closed - with the loop back to the customer being the most often skipped step.
The ECHO Framework
| Letter |
Stage |
The Question |
| E |
Elicit |
What sources are tapped, with what cadence, and how is bias controlled? |
| C |
Categorize |
How is feedback themed, tagged, and made queryable? |
| H |
Highlight |
What prioritization frame separates signal from noise? |
| O |
Operationalize |
Who owns the action, what's the SLA, and how is the loop closed with the customer? |
Elicitation Sources
A robust program reads from multiple channels and triangulates:
| Source |
Quality |
Volume |
Bias Risk |
| Surveys (NPS, CSAT, CES) |
Quantitative + open-ended |
High |
Survey fatigue, selection bias |
| Win / loss interviews |
Deep qualitative |
Low |
Selection bias toward closed deals |
| Customer advisory board |
Strategic qualitative |
Very low |
Top-customer bias |
| Support tickets |
Reactive, problem-focused |
Very high |
Skewed to broken, not desired |
| Product analytics |
Behavioral, not stated |
Very high |
Observation without intent |
| CSM call notes |
Contextual qualitative |
High |
CSM filter |
| Sales call recordings |
Pre-sale voice |
High |
Sales-stage filter |
| Community / public reviews |
Honest, public |
Medium |
Vocal-minority bias |
| Churn / contraction interviews |
High-signal |
Low |
Painful but most actionable |
Theming & Tagging
Without disciplined theming, VoC becomes a junk drawer. Adopt:
| Field |
Spec |
| Theme |
Standardized taxonomy (refreshed quarterly, not ad-hoc) |
| Severity |
Critical / Major / Minor - based on revenue impact, not emotion |
| Source |
Channel of origin (survey, ticket, call, etc.) |
| Segment |
ICP segment, plan tier, motion |
| Stage |
Pre-sale / Onboarding / Adoption / Renewal / Churn |
| Evidence Count |
Number of distinct customers raising the theme |
| Revenue at Risk / Opportunity |
ARR exposure or expansion potential |
Prioritization Frame
| Lens |
Question |
| Frequency |
How many distinct customers, by segment? |
| Severity |
Revenue impact if unaddressed (churn risk, deal blocker) |
| Solvability |
Effort vs leverage of the fix |
| Strategic Fit |
Does the fix advance the platform thesis or fix a wart? |
| Reach |
What share of ARR or users does the change touch? |
Combine into a RICE-style score, but never let the score replace judgment - leadership review is part of the process.
Operationalize: Route, Act, Close
| Theme Type |
Owner |
SLA |
| Product bug / friction |
PM / Eng |
Triaged in 5 business days |
| Onboarding gap |
CS Ops |
Updated playbook in 10 business days |
| Messaging / positioning gap |
Product Marketing |
Refreshed asset in 15 business days |
| Pricing / packaging objection |
Pricing Council |
Quarterly review |
| Roadmap signal |
PM Leadership |
Roadmap update in next planning cycle |
| Service quality |
Support Ops |
Triaged in 5 business days |
Loop closure with the customer is non-negotiable. Every customer who raised a theme should hear back when a related change ships - closes trust loop and earns the next round of feedback.
Output
Save to outputs/voice-of-customer-[scope]-[YYYY-MM-DD].md
| Artifact |
Description |
| Source Pipeline |
Inventory of channels, cadence, bias controls |
| Theme Taxonomy |
Standardized themes with definitions and examples |
| Prioritization Spec |
Scoring criteria, weights, refresh cadence |
| Routing Map |
Theme types → owners → SLAs |
| Loop-Closure Protocol |
How and when customers are informed of action taken |
| VoC Operating Cadence |
Weekly triage, monthly review, quarterly roadmap sync |
| VoC Dashboard |
Theme volume, severity distribution, action SLA performance, NPS / CSAT trend, closed-loop rate |
Process
- Inventory sources and design the cadence; eliminate redundant surveys
- Standardize the taxonomy with PM, CS, and marketing co-sign
- Score and prioritize with a written rubric, leadership review monthly
- Route to owners with SLAs; track action time, not just intent
- Close the loop with every customer who raised an actioned theme
- Refresh the taxonomy quarterly - emergent themes deserve their own bucket
Tips
- Survey fatigue is real - cap touches per customer per quarter
- Triangulate sources - single-source insights are usually wrong
- Behavioral data beats stated preference - pair always
- Loop closure is the most under-invested step - and the highest-leverage one
- VoC is a system - one-off projects don't compound
Pairs With
- customer-success - VoC themes feed CS risk plays and EBR agendas
- customer-analytics - Behavioral data complements stated feedback
- journey-architect - Stage tags align VoC with journey gates
- enablement-forge - Updated objection handling responds to recurring VoC themes
1---2name: voice-of-customer3description: Voice of Customer program - multi-source signal collection, theming and prioritization, evidence-to-action routing, and product / CS / marketing feedback loop closure. Use when: voice of customer, VoC program, customer feedback, NPS / CSAT / CES, qualitative theming, feedback synthesis, product feedback loop, customer insight engine.4---56# Voice of Customer (ECHO Framework)78Design a Voice-of-Customer program that turns raw feedback into routed, prioritized, evidence-backed actions - not a quarterly NPS report nobody reads. ECHO replaces ad-hoc surveys with a multi-source signal pipeline that PMs, CS, and marketing all rely on.910## Core Principle1112**VoC fails when it conflates *collection* with *insight*.** A survey isn't a program. ECHO standardizes how signal is elicited, themed, prioritized, and *closed* - with the loop back to the customer being the most often skipped step.1314## The ECHO Framework1516| Letter | Stage | The Question |17|--------|-------|--------------|18| **E** | Elicit | What sources are tapped, with what cadence, and how is bias controlled? |19| **C** | Categorize | How is feedback themed, tagged, and made queryable? |20| **H** | Highlight | What prioritization frame separates signal from noise? |21| **O** | Operationalize | Who owns the action, what's the SLA, and how is the loop closed with the customer? |2223## Elicitation Sources2425A robust program reads from **multiple channels** and triangulates:2627| Source | Quality | Volume | Bias Risk |28|--------|---------|--------|-----------|29| **Surveys (NPS, CSAT, CES)** | Quantitative + open-ended | High | Survey fatigue, selection bias |30| **Win / loss interviews** | Deep qualitative | Low | Selection bias toward closed deals |31| **Customer advisory board** | Strategic qualitative | Very low | Top-customer bias |32| **Support tickets** | Reactive, problem-focused | Very high | Skewed to broken, not desired |33| **Product analytics** | Behavioral, not stated | Very high | Observation without intent |34| **CSM call notes** | Contextual qualitative | High | CSM filter |35| **Sales call recordings** | Pre-sale voice | High | Sales-stage filter |36| **Community / public reviews** | Honest, public | Medium | Vocal-minority bias |37| **Churn / contraction interviews** | High-signal | Low | Painful but most actionable |3839## Theming & Tagging4041Without disciplined theming, VoC becomes a junk drawer. Adopt:4243| Field | Spec |44|-------|------|45| **Theme** | Standardized taxonomy (refreshed quarterly, not ad-hoc) |46| **Severity** | Critical / Major / Minor - based on revenue impact, not emotion |47| **Source** | Channel of origin (survey, ticket, call, etc.) |48| **Segment** | ICP segment, plan tier, motion |49| **Stage** | Pre-sale / Onboarding / Adoption / Renewal / Churn |50| **Evidence Count** | Number of distinct customers raising the theme |51| **Revenue at Risk / Opportunity** | ARR exposure or expansion potential |5253## Prioritization Frame5455| Lens | Question |56|------|----------|57| **Frequency** | How many distinct customers, by segment? |58| **Severity** | Revenue impact if unaddressed (churn risk, deal blocker) |59| **Solvability** | Effort vs leverage of the fix |60| **Strategic Fit** | Does the fix advance the platform thesis or fix a wart? |61| **Reach** | What share of ARR or users does the change touch? |6263Combine into a RICE-style score, but never let the score replace judgment - leadership review is part of the process.6465## Operationalize: Route, Act, Close6667| Theme Type | Owner | SLA |68|------------|-------|-----|69| **Product bug / friction** | PM / Eng | Triaged in 5 business days |70| **Onboarding gap** | CS Ops | Updated playbook in 10 business days |71| **Messaging / positioning gap** | Product Marketing | Refreshed asset in 15 business days |72| **Pricing / packaging objection** | Pricing Council | Quarterly review |73| **Roadmap signal** | PM Leadership | Roadmap update in next planning cycle |74| **Service quality** | Support Ops | Triaged in 5 business days |7576**Loop closure with the customer is non-negotiable.** Every customer who raised a theme should hear back when a related change ships - closes trust loop and earns the next round of feedback.7778## Output7980Save to `outputs/voice-of-customer-[scope]-[YYYY-MM-DD].md`8182| Artifact | Description |83|----------|-------------|84| **Source Pipeline** | Inventory of channels, cadence, bias controls |85| **Theme Taxonomy** | Standardized themes with definitions and examples |86| **Prioritization Spec** | Scoring criteria, weights, refresh cadence |87| **Routing Map** | Theme types → owners → SLAs |88| **Loop-Closure Protocol** | How and when customers are informed of action taken |89| **VoC Operating Cadence** | Weekly triage, monthly review, quarterly roadmap sync |90| **VoC Dashboard** | Theme volume, severity distribution, action SLA performance, NPS / CSAT trend, closed-loop rate |9192## Process93941. **Inventory sources** and design the cadence; eliminate redundant surveys952. **Standardize the taxonomy** with PM, CS, and marketing co-sign963. **Score and prioritize** with a written rubric, leadership review monthly974. **Route to owners** with SLAs; track action time, not just intent985. **Close the loop** with every customer who raised an actioned theme996. **Refresh the taxonomy quarterly** - emergent themes deserve their own bucket100101## Tips1021031. **Survey fatigue is real** - cap touches per customer per quarter1042. **Triangulate sources** - single-source insights are usually wrong1053. **Behavioral data beats stated preference** - pair always1064. **Loop closure is the most under-invested step** - and the highest-leverage one1075. **VoC is a *system*** - one-off projects don't compound108109## Pairs With110111- **customer-success** - VoC themes feed CS risk plays and EBR agendas112- **customer-analytics** - Behavioral data complements stated feedback113- **journey-architect** - Stage tags align VoC with journey gates114- **enablement-forge** - Updated objection handling responds to recurring VoC themes
varunk130