Warning: Constant WP_CACHE_KEY_SALT already defined in /home/staging_interaction/www/wp-config.php on line 64

Deprecated: Return type of Illuminate\Support\Collection::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1789

Deprecated: Return type of Illuminate\Support\Collection::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1800

Deprecated: Return type of Illuminate\Support\Collection::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1812

Deprecated: Return type of Illuminate\Support\Collection::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1827

Deprecated: Return type of Illuminate\Support\Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1768

Deprecated: Return type of Illuminate\Support\Collection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1747

Deprecated: Return type of Illuminate\Support\Collection::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 1716

Deprecated: Return type of Illuminate\Container\Container::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1197

Deprecated: Return type of Illuminate\Container\Container::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1208

Deprecated: Return type of Illuminate\Container\Container::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1220

Deprecated: Return type of Illuminate\Container\Container::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 1233

Deprecated: Return type of Illuminate\Config\Repository::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 141

Deprecated: Return type of Illuminate\Config\Repository::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 152

Deprecated: Return type of Illuminate\Config\Repository::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 164

Deprecated: Return type of Illuminate\Config\Repository::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/config/Repository.php on line 175

Deprecated: Method ReflectionParameter::getClass() is deprecated since 8.0, use ReflectionParameter::getType() instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 826

Deprecated: Method ReflectionParameter::getClass() is deprecated since 8.0, use ReflectionParameter::getType() instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/container/Container.php on line 900

Deprecated: Brain\Hierarchy\Branch\BranchSingle::__construct(): Implicitly marking parameter $postTemplates as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/brain/hierarchy/src/Branch/BranchSingle.php on line 29

Deprecated: Brain\Hierarchy\Branch\BranchPage::__construct(): Implicitly marking parameter $postTemplates as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/brain/hierarchy/src/Branch/BranchPage.php on line 30

Deprecated: Illuminate\View\View::render(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 87

Deprecated: Return type of Illuminate\View\View::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 308

Deprecated: Return type of Illuminate\View\View::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 319

Deprecated: Return type of Illuminate\View\View::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 331

Deprecated: Return type of Illuminate\View\View::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/view/View.php on line 342

Notice: file_get_contents(): Read of 12288 bytes failed with errno=21 Is a directory in /home/staging_interaction/www/wp-includes/functions.php on line 4666

Notice: wp_json_file_decode(): Error when decoding a JSON file at path /home/staging_interaction/www/wp-content/themes/interaction-metrics/resources: Syntax error in /home/staging_interaction/www/wp-includes/functions.php on line 6114

Notice: file_get_contents(): Read of 12288 bytes failed with errno=21 Is a directory in /home/staging_interaction/www/wp-includes/functions.php on line 4666

Notice: wp_json_file_decode(): Error when decoding a JSON file at path /home/staging_interaction/www/wp-content/themes/interaction-metrics/resources: Syntax error in /home/staging_interaction/www/wp-includes/functions.php on line 6114
Should Your Customer Surveys be Anonymous?
Bain & Company’s Rob Markey says “no” to customer anonymity. But it’s not so clear.

Clients often ask: do we need to allow for customer anonymity in our surveys?

Market researchers generally provide the option for customer anonymity so that respondents who might otherwise feel embarrassed or fear reprisal can answer honestly. In the context of sensitive employee feedback like DEI surveys and engagement surveys, most researchers consider the option for anonymity to be essential.

But in our recent CXPA workshop roundtable on NPS for B2B companies, Bain’s Rob Markey disputed that premise.

A Bain & Company veteran of more than 30 years, Markey is the co-inventor of NPS and created Bain’s approach to customer centricity. He recently wrote “Are You Undervaluing Your Customers?” and founded Bain’s Customer Strategy and Marketing practice.

Rob Markey shared his insights last month during a wide-ranging CXPA roundtable conversation where we discussed how to meet decision-makers’ needs and weigh feedback from various groups.

Market researchers generally provide the option for customer anonymity so that respondents who might otherwise feel embarrassed or fear reprisal can answer honestly.

Our next B2B Customer Experience roundtable on June 27 will cover an AI Case Study with special guests Leslie Pagel and Lynn Dumas. If it’s anything like my conversation with Rob, it’s sure to be a lively discussion. Register here!

Back to Rob Markey: Building the Customer Relationship

Our conversation was fascinating, but Rob’s argument against customer anonymity was a highlight.

One of Markey’s core CX objectives is that the main goal of soliciting customer feedback should be to enhance a company’s relationship with its customers. Further, he recommends that the Net Promoter Survey should be the jumping-off point for additional conversations.

Of course, those conversations are impossible if the customer chooses to give feedback anonymously — hence Markey’s position that anonymity is counterproductive.

It’s important to note here the difference between anonymity and confidentiality in the context of customer surveys.

  • Anonymity means that no one can associate your answers with any of your identifying information.
  • Confidentiality means that your answers can be associated with your identifying information, but that information will not be disseminated and will be stored in a secure manner.
Offering the option for survey takers to choose anonymity if they wish is a sound business practice and leads to higher quality, more factual customer survey data.

I’ve often said that follow-up conversations with survey participants is a huge advantage, mainly because customers can let their hair down and expand on topics in a way they simply can’t within the confines of a survey.

And yet, offering the option for survey takers to choose anonymity if they wish is a sound business practice and leads to higher quality, more factual customer survey data.

The Need for Customer Anonymity

When provided the option, roughly half of all survey participants will choose to give anonymous feedback. Therefore, excluding this option impacts the sample size and skews the data itself.

In smaller surveys, losing half of the participants for the sake of insisting customers identify themselves means the response rate can become statistically invalid.

While Rob argues that the quality of feedback between the anonymous and non-anonymous respondents is nearly identical, our data from many years of surveys finds anonymous respondents consistently give lower scores than those who choose to be named.

And if survey respondents are required to identify themselves, it can lead to social desirability bias. This is the tendency to answer based on how others view you rather than the truth.

Furthermore, some clients will only agree to participate in a survey if they can give anonymous feedback. For instance, large corporations may have legal and PR policies preventing them from participating in customer experience surveys unless they are guaranteed strict anonymity.

When provided the option, roughly half of all survey participants will choose to give anonymous feedback. Therefore, excluding this option impacts the sample size and skews the data itself.

Promote Honest Dialogue

Markey views customer experience surveys through the lens of promoting honest and open dialogue in a B2B partnership.

Other market researchers see the decision to offer customer anonymity as the right thing to do for respondents. In research, it’s the norm.

So, should customer surveys be anonymous?

At the end of the day, the decision whether or not to allow anonymous feedback comes down to what’s right for the client and their business.

If you’d like to participate in interesting CX conversations like this one with Rob Markey, get notified of our B2B CXPA Roundtables here.

In Sum: Should Customer Surveys be Anonymous?

Bain & Company’s Rob Markey says “no” to customer anonymity. But it’s not so clear.

 

 

Categories: Customer Satisfaction Surveys