From Mirror to Motor: Rethinking Voice of Customer

The honest place to start is with how VoC sees itself.

Most VoC teams define themselves by what they produce: dashboards, scores, NPS waterfalls, sentiment heat-maps. After a while, that's all they own. The dashboards keep getting better. The decisions don't.

Three things are going wrong at the same time.

Quantitative data tells you what changed. It almost never tells you why.

Jean Felix, a CX practitioner who writes regularly on this blog, makes that argument. For most of VoC's history, he says, the why-question was a budget problem: structured customer conversation simply didn't scale. That excuse is gone.

“Surveys and analytics tell us what changed. AI now lets us go one step further at scale — transcribe, cluster, and synthesize hundreds of structured customer conversations in the time it used to take to write the discussion guide. The new VoC stack isn't another dashboard. It's a human practitioner asking better questions, with AI doing the listening, the tagging, and the surfacing in the background. The teams still running quarterly NPS as their primary instrument aren't behind on data. They're behind on technology.”

Lemon and Verhoef's landmark mapping of customer experience across the journey identified the same gap on theoretical grounds ⁽³⁾ — but the practical fix needed tooling that didn't exist yet. More recent text-as-data research in the Journal of Marketing ⁽⁴⁾ shows that AI-driven analysis of customer conversation now produces measurable lifts in marketing-decision quality, at unit costs VoC budgets can absorb. 

The qualitative-versus-quantitative trade-off used to be real. Today, it's a tooling decision dressed up as a methodology debate.

Michel Stevens points out that VoC is rarely the first thing to break in a business. It's usually the last symptom of a deeper failure: the organization doesn't agree on what the customer journey actually looks like.

“If your business doesn’t agree on what the journey actually looks like, your VoC program will end up being three different stories told in three different rooms. The dashboard isn’t the problem — the missing journey underneath it is.”

Homburg, Jozić, and Kuehnl make this explicit in their reference framework for Customer Experience Management ⁽⁵⁾, where the journey functions as the integrative skeleton of the discipline. Without it, no measurement system — however sophisticated, however AI-augmented — can be coherently aggregated. The C-suite hears noise where it needs signal. And then it shoots the messenger, not the architecture. 

One diagnosis, three layers: a naming problem, a tooling problem, and an architecture problem. Fix one and the others still bite.

If the first question is what's wrong, the second is what to wire differently. The operating model. The cadence. The rituals that turn a VoC signal into an actual decision.

Start with the journey

Michel’s prescription is uncompromising: every VoC program needs to be anchored to a specific, documented set of moments of truth on the customer journey, with named operational owners, before any survey is fielded. The survey is the consequence of the journey work — not a substitute for it.

“VoC becomes valuable the moment the insight changes a moment of truth for a real customer — not the moment it changes a slide in a steering committee. Until then, it’s a dashboard talking to itself.”

Heskett, Sasser, and Schlesinger’s Service Profit Chain ⁽⁶⁾ backs this empirically. Customer-experience metrics translate into financial outcomes only when the operational chain — internal service quality, employee behavior, customer-facing delivery — stays intact between insight and action. VoC that doesn't change a behavior doesn't change a P&L.

Then build the structure around it

Once the journey is shared, Gerben provides the systemic answer. VoC needs to be anchored to the value strategy at the top, and tied to a KPI architecture in which:

• Top-line KPIs cascade downward.
• Functions are measured on shared metrics, not just individual ones.
• The IT landscape is critically reviewed before any new tool gets bought, and redundant systems are removed.

He's refreshingly against more software:

“Less really is more. Use the data you already have and turn it into actionable insight. Only invest where something is genuinely missing.”

This is exactly what Day called a market-driven organization ⁽⁷⁾, one where sensing, sharing, and using market intelligence are organizational capabilities rather than the property of a single team. Day's empirical work shows that firms with stronger inside-out diffusion of customer information outperform their peers, but only when aligned incentives back the diffusion. Misaligned KPIs don't slow integration; they actively reverse it.

Finally, fix the rhythm
Journey set, operating model in place — and yet, Jean insists, none of it holds up unless the cadence does.

The moment VoC becomes truly operational is the moment a real practitioner sits across from a real customer, runs the conversation, and brings the synthesis back into a recurring decision forum. Rhythm matters as much as structure. And rhythm is what AI just changed.

“You can’t rewire VoC by rewriting the org chart. You rewire it by changing what the team is asked about in the first standup of the week — and by making sure the answer is grounded in a customer conversation from the previous one. Modern technology is what makes that weekly cadence realistic. Ten years ago, it was a quarterly luxury.”

Edmondson's work on team learning ⁽⁸⁾ backs this directly. Change in mature teams happens when local rituals, daily standups, weekly reviews, performance conversations, start asking different questions, not when leadership announces a new mandate.

Jean's added point is that AI-assisted qualitative tooling is what makes that agenda change sustainable. A weekly customer-evidence ritual is no longer aspirational; it's operationally feasible. The transformation Gerben describes at the strategic level, anchored to Michel's journey, is, in the end,  Jean's standup.

VoC moves an organization when the journey is shared, the KPIs are aligned, the cadence is weekly, and the technology is honest.

This is where the contributors most productively diverge, and where the literature is least settled. The question, narrowed: if VoC needs to be repositioned, what does the new function look like? What does it own? Who runs it? Where does it report?

The new capability mix is hybrid

Jean opens with capability, because it's the prerequisite for every other answer. Beyond strategy and IT, he argues, the next-generation VoC team is defined by two things at once:

• The human craft of running a structured customer conversation.
• The technical fluency to deploy AI and modern qualitative-research platforms in service of that craft.

Neither, on its own, is enough.

“If the new mandate is orchestration, the new capability set is half facilitation, half technology. You need the practitioner who can run a customer interview that actually surfaces the why — and the same person, or a partner sitting next to them, who can wire that conversation into an AI pipeline that scales it across hundreds more. VoC teams that hire for either skill in isolation will produce either thin insights at speed, or deep insights too slowly.”

Kotter's work on organizational change ⁽⁹⁾ makes the closely related point: the limiting factor in transformation is rarely the diagnosis or the plan. It's the social infrastructure — the coalitions, the short-term wins, the recurring forums — through which decisions get made and made again. A VoC function that owns insight without owning the rooms in which decisions are made will, predictably, fail to produce decisions.

Jean's hybrid-capability point is the operational corollary: those rooms now run with AI in the background, and the team that orchestrates them needs to be fluent in both registers.

Reporting line is identity

Michel sharpens the question into a reporting-line one — and, by extension, into a question about how seriously the firm takes the customer in the first place. He's direct:

“The day VoC stops reporting into marketing and starts reporting into the COO is the day it gets taken seriously. Not because marketing is wrong — but because operations is where the friction lives, and where the customer feels it.”

Vargo and Lusch’s service-dominant logic ⁽¹⁰⁾ frames Michel’s point precisely: value is co-created with the customer at the point of operational delivery, not at the point of brand communication. The reporting line of the function that translates customer signal into operational change is therefore a leading indicator of how seriously the firm takes co-creation as a discipline — not a lagging one.

Where the function reports tells you what the function is allowed to do.

Maybe a rebrand

Gerben goes furthest. Even with the right operating model, the right mandate, and the right reporting line, he argues, the function may be too burdened by its current image: attractive dashboards, limited action. His prescription is a rebrand, a re-capability, and a reposition, all in one move.

“Reporting is one thing. Actually moving an organization is something else entirely.”

In his framing, the function shifts, in his words, from number cruncher to catalyst for change. It sits between strategy, IT, operating-model design, and change management, and owns both:

• The inner loop — direct customer-facing recovery, where issues get resolved with the customer who raised them.
• The outer loop — structural change, where systemic problems get routed back to the teams that can fix them.

This is consistent with Shah and colleagues’ work on the path to customer centricity ⁽¹¹⁾. They identify the orchestration layer — not the measurement layer — as the binding constraint for most firms attempting the transition. Their longitudinal data is unambiguous: organizations that succeed in becoming customer-centric do so by relocating the customer function closer to operations and strategy, not closer to marketing communications.

Gerben’s rebrand, Michel’s COO reporting line, and Jean’s hybrid capability are three faces of the same structural shift.

Rebrand, new reporting line, hybrid capability — or all three. The one thing the contributors agree on: VoC’s next identity has to be defined by the decisions it owns, not by the data it produces.

The path from VoC dashboard to VoC impact isn’t a measurement problem. It’s an orchestration problem.

It’s a question of where the function sits, what it owns, which conversations it’s allowed to host, and what tooling it’s allowed to deploy. Bigger dashboards, smarter sentiment models, and prettier scores can’t substitute for a function that is:

• Wired into the journey, with named operational owners on each moment of truth.
• Anchored to shared KPIs that cascade from the value strategy at the top.
• Run on a weekly cadence, with AI-assisted qualitative work feeding decision rituals.
• Reporting somewhere closer to the COO than to the CMO.
  
  

The shift is from mirror to motor: from a polished surface that everyone admires, to the moving part that drives the decisions, rituals, and operating model through which the customer is actually served.

Mirror, mirror on the wall, who is the fairest of them all? The honest answer is: no one. Not until VoC is allowed to do something about it.

(1)  Morgan, N. A. & Rego, L. L. (2006). The Value of Different Customer Satisfaction and Loyalty Metrics in Predicting Business Performance. Marketing Science, 25(5), 426–439.

(2)  Reichheld, F. & Markey, R. (2011). The Ultimate Question 2.0: How Net Promoter Companies Thrive in a Customer-Driven World. Harvard Business Review Press.

(3)  Lemon, K. N. & Verhoef, P. C. (2016). Understanding Customer Experience Throughout the Customer Journey. Journal of Marketing, 80(6), 69–96.

(4)  Berger, J., Humphreys, A., Ludwig, S., Moe, W. W., Netzer, O. & Schweidel, D. A. (2020). Uniting the Tribes: Using Text for Marketing Insight. Journal of Marketing, 84(1), 1–25.

(5)  Homburg, C., Jozić, D. & Kuehnl, C. (2017). Customer Experience Management: Toward Implementing an Evolving Marketing Concept. Journal of the Academy of Marketing Science, 45(3), 377–401.

(6)  Heskett, J. L., Sasser, W. E. & Schlesinger, L. A. (1997). The Service Profit Chain: How Leading Companies Link Profit and Growth to Loyalty, Satisfaction, and Value. Free Press.

(7)  Day, G. S. (1994). The Capabilities of Market-Driven Organizations. Journal of Marketing, 58(4), 37–52.

(8)  Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350–383.

(9)  Kotter, J. P. (1996). Leading Change. Harvard Business School Press.

(10)  Vargo, S. L. & Lusch, R. F. (2004). Evolving to a New Dominant Logic for Marketing. Journal of Marketing, 68(1), 1–17.

(11)  Shah, D., Rust, R. T., Parasuraman, A., Staelin, R. & Day, G. S. (2006). The Path to Customer Centricity. Journal of Service Research, 9(2), 113–124.