Culture, organization and governance

Overcoming Internal Resistance to VoC Transparency Across Teams

Sharing customer feedback widely can make teams nervous. Here's how to win them over and make VoC transparency part of how your company works.

Overcoming Internal Resistance to VoC Transparency Across Teams

Opening up customer feedback to the whole company sounds like an easy win. Then the pushback starts. Product leaders worry about being blamed for bugs. Sales teams worry about losing deals if complaints spread. Support leads worry about looking understaffed. Some managers simply prefer to control the story.

Why Teams Resist

Resistance usually comes from fear of blame. When feedback is shared, problems become visible, and people worry it'll reflect badly on them. Change fatigue adds to it. Gartner research found that employee willingness to support organizational change fell from 74% in 2016 to 38% in 2022.

Trust in data is low

Research from Precisely and Drexel University in 2024 found that 67% of data professionals don't completely trust the data they use for decisions. If teams doubt the numbers, they'll resist being judged by them. Share how the data is collected and cleaned so teams can see it's fair.

Compared

Employee willingness to support change

  • 201674%
  • 202238%

Source: Gartner. Figures as cited in this article

Frame Transparency as Help

Position shared feedback as a tool for solving problems. Avoid using it to assign blame. Show each team how feedback can make their work easier. Product teams get clearer priorities. Sales teams get early warning on account risk.

Start with good news

Share positive feedback first. When teams see customers praising their work, they warm up to the idea quickly. Mix in problems once people trust the process. A quick shout-out from a customer often does more than a long presentation.

Involve Skeptics Early

Invite the most resistant teams to help design how feedback gets shared. Ask what they're worried about and build safeguards around those concerns. People support what they help create.

Agree on ground rules

  • Feedback is shared to fix problems, never to rank individuals.
  • Teams see issues in their area before they're shared widely.
  • Every theme comes with context, such as volume and trend.
  • Leaders respond to bad news with questions instead of blame.
Checklist

Ground rules for sharing feedback

  • Shared to fix problems, never to rank individuals
  • Teams see their issues before wide sharing
  • Every theme comes with volume and trend
  • Leaders meet bad news with questions, not blame

Free review snapshot

See what your customers are saying, before you talk to us.

No commitment. We use your details only to send your snapshot and follow up. Privacy policy

Watch for Fatigue

Gartner's Hilary Richards has warned that “change fatigued employees exhibit much lower intent to stay.” Roll out transparency in steps. Start with one or two teams and expand once you can show results. Ask teams how the rollout feels and adjust the pace if people seem overloaded.

Keep the load light

Don't add a new dashboard to an already crowded week. Fold feedback into meetings and tools people already use. Our guide to VoC dashboard adoption covers what works.

change fatigued employees exhibit much lower intent to stay.

Hilary Richards, Gartner

Show Leaders Living It

Transparency spreads when executives model it. Ask leaders to share customer complaints about their own areas openly. When a senior leader says “here's what we got wrong and how we're fixing it,” teams feel safe doing the same.

Celebrate the fixes

Share stories where open feedback led to a quick win. Credit the team that acted. Keep a running list of wins and revisit it when doubts come back. Our post on executive VoC sponsorship explains how to get leaders involved, and our guide to breaking down VoC silos covers sharing across departments. You can share feedback openly across teams with NPS analysis, or book a demo.

Frequently asked questions

Why do teams resist VoC transparency?

Most resistance comes from fear of blame and doubts about whether the data is accurate.

How do you reduce fear of blame?

Agree that feedback is shared to fix problems and never to rank individuals.

Should you share negative feedback right away?

Start with positive feedback, then add problems once teams trust the process.

How do you win over skeptical teams?

Involve them in designing how feedback gets shared and address their concerns directly.

How fast should you roll out transparency?

Start with one or two teams and expand once you can show results.

What role do executives play?

They set the tone by openly sharing and acting on feedback about their own areas.

Put these ideas to work on your own feedback.

Book a 30-minute demo, or take the interactive tour of the Falcon workspace.

Book a demo