Most enterprise Voice of the Customer programs do not have a listening problem. They run surveys, monitor reviews, analyze contact-center text and publish dashboards to hundreds of users. Yet when a CX leader is asked what changed in the business last quarter because of customer feedback, the answer is often a short list of resolved complaints and a longer list of insights still waiting for an owner.
This article calls that distance the VoC execution gap: the space between what an organization knows about its customers and what it actually changes as a result. It is the cornerstone of a seven-part series on where customer insight stalls and what high-functioning programs do differently.
A voice of the customer program drives real change only when every insight has a path to a decision, an owner with authority to act, and a way to verify that the fix worked. Most programs invest heavily in the first stage, collection and analysis, and lightly in the stages that follow. The gap is rarely caused by too little data. It is caused by missing decision rights, weak links to the operating teams that control the root causes, and measurement that reports scores instead of outcomes.
Independent research points in the same direction.
Forrester's 2025 State of Feedback Management and CX Measurement Practices survey of 311 practitioners concluded that most CX teams "still don't get stakeholders to act on insights." Only about half of teams could link CX metrics to business outcomes, fewer than a third (27%) communicated insights in a timely way, and close-the-loop practices typically responded to negative feedback while rarely communicating what the organization changed (Forrester, August 2025). Forrester notes that the sample was self-selected, so the figures are descriptive rather than representative.
McKinsey's survey of more than 260 US CX leaders found that 93% relied on a survey-based metric as their primary measure of CX performance, but only 15% were fully satisfied with how their company measured CX, and only 6% were confident their measurement system supported both strategic and tactical decisions (McKinsey, February 2021). The fieldwork predates 2020, but the pattern persists.
Qualtrics XM Institute's State of Customer Experience Management 2025 found that 65% of organizations remain in the early stages of CX maturity and only 17% of practitioners can point to monetary benefits from CX spending. In an interview about the findings, the Institute's Isabelle Zdatny described CX teams caught in a cycle where "executives are only giving them remit to collect insights, not to implement substantive initiatives" (Freshworks interview, August 2025).
Gartner has framed the same issue in its research note Why Voice of the Customer Falls Short, and How a Two-Loop Process Helps (Gartner, October 2025), and earlier survey work found that organizations able to show how customer satisfaction is associated with growth, margin and profitability were 29% more likely to secure more CX budget (Gartner press release, May 2022).
The market is not short of customer understanding. It is short of conversion: from understanding to decisions, and from decisions to verified change.
Definition: The VoC execution gap is the share of validated customer insight that never results in an owned, completed and measured change to a product, process, policy or service.
Three distinctions matter:
The most useful lens for the gap remains the distinction Rob Markey, Fred Reichheld and Jamie Dullweber described in Harvard Business Review in 2009: an inner loop, in which frontline teams follow up with individual customers and learn from them, and an outer loop, in which aggregated feedback drives changes to processes, policies and products that no single frontline team controls (HBR, December 2009).
Most enterprises have a functioning inner loop: alerts fire, cases are assigned, customers get a call back. The outer loop is where programs stall, because it requires coordination across functions that report to different executives, run on different planning cycles and measure success in different ways.
Six recurring failure points explain most of the gap. Each gets its own article in this series.
Behind all six sits a seventh, organizational condition: the mandate. Many CX teams are chartered to measure and report. Few are chartered to convene decision-makers, escalate unresolved issues, or hold other functions to agreed service levels for acting on insight.
Forrester's 2026 predictions warn that CX teams under budget pressure risk becoming "replaceable reporting functions" if they keep feeding demand for dashboards that do not reveal which problems to solve or why they matter (Forrester, October 2025). A program whose charter ends at insight will produce insight. Closing the execution gap usually begins with rewriting the charter, not buying more listening capacity.
The following scenario is illustrative and does not describe a specific company.
A multi-country insurer notices that claims-related detractor comments mention "documents" far more often than a year earlier. The CX team flags it in a monthly report. The claims operations team agrees it is a problem, but the document-upload flow belongs to digital, and the document requirements belong to underwriting and compliance. Each team treats the insight as useful context rather than a decision for them to take. Six months later the theme is still in the report.
Nothing here is a data failure. What was missing was a mechanism that converts a recurring theme into a named owner, a decision deadline and a follow-up measure.
Closing the gap is mainly organizational work, but tooling determines whether that work is visible and repeatable. In Pisano, feedback arriving in the Feedback Inbox can be tagged, filtered and assigned by role, branch or region. Critical feedback can become a structured case in Ticket Manager, where teams assign ownership, track SLA performance and record root causes across related cases so recurring problems can be prioritized beyond the individual ticket. Workflows define next steps automatically based on feedback content, and Planner keeps improvement tasks linked to the feedback and reports that justified them.
None of this replaces a clear mandate or decision rights. It makes them easier to enforce, as we discuss in why automated workflows matter for acting on feedback.
The most revealing metric for a VoC program is not its response rate or its NPS. It is the proportion of validated insights that became an owned, completed and measured change. Few organizations track it, which is part of why the gap persists.
The articles that follow examine each stall point in turn, starting with the most familiar one: the score that tells you something changed, but not what to fix.