Most Voice of the Customer programs begin the same way: with genuine excitement and unusually strong executive buy‑in.
There’s a clear mandate from the top to “listen better.” A vendor is selected. Dashboards are built. Surveys are launched with care and optimism. Leaders talk openly about how important customer voice is going to be to the next phase of growth.
For a brief moment, VOC feels like momentum.
And then—quietly, almost imperceptibly—it starts to fade.
Response rates drop. The insights grow repetitive. Meetings that once lingered on survey results start glossing over them. Eventually, the VOC program still exists, but mostly as background noise. Maintained. Referenced occasionally. Rarely decisive.
This isn’t because leaders suddenly stopped caring about customers. It’s because most VOC programs are not designed for the reality they’re dropped into.
They are designed to gather feedback. But organisations don’t struggle with a lack of feedback. They struggle with prioritisation, trade‑offs, and decision friction.
The predictable arc no one talks about
Almost every VOC program I’ve seen follows the same trajectory.
It launches with fanfare and endorsement from the executive team. Response rates are high at first, partly because customers haven’t yet been conditioned to ignore the surveys. There’s novelty on both sides.
But as time passes, customers are asked again. And again. And again.
Roughly the same NPS or CSAT questions arrive after support interactions, product milestones, renewals, and occasionally for no clear reason at all. The intent is good—more data, more signal—but the effect is the opposite. Customers feel over‑surveyed. The most engaged voices answer repeatedly, while the quieter majority drops out.
The deluge of results shrinks to a steady trickle.
Ironically, this decline is often misdiagnosed as a tooling or wording problem, when it’s actually a trust problem. Customers stop responding not because they don’t have opinions, but because they don’t see evidence that responding leads to change.
When simplification goes too far
In response to falling engagement, many teams respond by simplifying.
Questions get shorter. Surveys get combined. NPS and CSAT are bundled together in the hope of “getting the best of both” while reducing friction. On paper, this looks efficient.
In practice, it produces the worst of all worlds.
NPS and CSAT answer different questions and are useful in different contexts. Combining them to boost response rates tends to blur intent, confuse respondents, and muddy interpretation. You end up with numbers that look familiar but explain very little. Representativeness doesn’t improve; it quietly worsens.
This is compounded by the fact that there is still widespread confusion about what NPS is actually for. Despite years of writing on the subject—including Bain’s own clarification that NPS is best used as a system, not a standalone score—it continues to be treated as either a revenue proxy or a performance metric for teams it was never designed to judge.
When leaders can’t agree on what a metric is supposed to tell them, they predictably stop trusting what it does tell them.
Dashboards don’t shift priorities—decisions do
One of the quiet reasons VOC programs lose influence is the belief that visibility equals impact.
Sophisticated dashboards give the impression of progress, but most do not change behaviour on their own. By the time VOC data reaches an executive forum, priorities are often already set. Roadmaps are committed. Headcount assumptions are locked.
If VOC insights don’t force a decision—to invest, to defer, to redesign, or to consciously accept risk—they become observational rather than operational.
This is a pattern I’ve seen repeatedly, not just with VOC but with QA programs and metric-heavy CX reporting more broadly. Anything that surfaces problems without embedding ownership and consequence eventually gets sidelined. I touched on this dynamic in Support Is Not a Cost Center — But Pretending It Isn’t Gets You Defunded, because the underlying issue is the same: leaders fund what reduces uncertainty, not what narrates it.
When VOC starts doing harm
There is also a more uncomfortable failure mode—when VOC data doesn’t disappear, but instead gets selectively used.
Over time, I’ve seen customer quotes and survey segments weaponised to justify decisions that were already politically favoured. Feedback becomes a rhetorical tool rather than an input. Teams begin to recognise this pattern quickly.
That’s when trust erodes internally.
Engineering stops engaging. Support managers become defensive. Frontline teams start treating VOC as something that happens to them rather than for them. At that point, you can continue running surveys, but the program has already lost its strategic value.
What effective VOC actually does
The most effective Voice of the Customer programs I’ve worked with were built around one clear purpose: reducing uncertainty at the point of decision.
They were not optimized for volume. They were optimized for clarity.
Feedback was surfaced selectively, not comprehensively. Insights were framed explicitly as choices, with clear implications if no action was taken. And crucially, every meaningful VOC insight had an owner before it reached senior leadership.
These programs did less broadcasting and more forcing. They didn’t try to make the company feel more customer‑centric. They helped leaders decide where to lean in—and where to accept discomfort intentionally.
That difference is subtle, but it’s everything.
When not to run a VOC program at all
There are situations where shutting a VOC program down is the most honest move.
If your organisation lacks the capacity or willingness to act on feedback, continuing to ask for it creates false expectations. Customers notice. Employees notice. Over time, the gap between listening and acting does more damage than silence would have.
I would rather see a narrowly scoped, decision‑oriented VOC program—or none at all—than a broad, performative one that trains everyone to ignore it politely.
A better starting question
Before launching or redesigning VOC yet again, I’d urge CX leaders to pause and ask a harder set of questions:
What specific decisions will this inform?
What uncertainty will it reduce for leadership?
And who is accountable when we choose not to act?
If you can’t answer those cleanly, the issue isn’t response rates or survey design. It’s that the program isn’t anchored in how decisions actually get made.
Voice of the Customer earns its influence not by speaking louder, but by speaking precisely—into the moments where trade‑offs are unavoidable.
That’s when listening turns into leadership.
Related reading on CX Master
- What 19 Years of Support Leadership Actually Taught Me
- Support Is Not a Cost Center — But Pretending It Isn’t Gets You Defunded
Hutch Morzaria is a Director-level CX and Support Leadership professional with 19 years of experience building global support organizations across SaaS, Fintech, and enterprise technology. He has hired dozens of support and CX leaders across his career and holds ITIL Expert certification across V3 and V4.
