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

Deprecated: WP_Rocket_Mobile_Detect::__construct(): Implicitly marking parameter $headers as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/classes/dependencies/mobiledetect/mobiledetectlib/Mobile_Detect.php on line 888

Deprecated: MwpWorkerResponder::callback(): Implicitly marking parameter $response as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/init.php on line 165

Deprecated: MWP_WordPress_Context::__construct(): Implicitly marking parameter $globals as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/MWP/WordPress/Context.php on line 28

Deprecated: MWP_WordPress_Context::__construct(): Implicitly marking parameter $constants as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/MWP/WordPress/Context.php on line 28

Deprecated: Symfony_EventDispatcher_EventDispatcher::dispatch(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/Symfony/EventDispatcher/EventDispatcher.php on line 40

Deprecated: Symfony_EventDispatcher_EventDispatcherInterface::dispatch(): Implicitly marking parameter $event as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/Symfony/EventDispatcher/EventDispatcherInterface.php on line 36

Deprecated: MWP_Extension_HitCounter::increment(): Implicitly marking parameter $dateTime as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/worker/src/MWP/Extension/HitCounter.php on line 37

Deprecated: Jaybizzle\CrawlerDetect\CrawlerDetect::__construct(): Implicitly marking parameter $headers as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/pixelyoursite/vendor/jaybizzle/crawler-detect/src/CrawlerDetect.php on line 79

Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60

Deprecated: WP_Rocket\Dependencies\League\Container\Container::__construct(): Implicitly marking parameter $definitions as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 42

Deprecated: WP_Rocket\Dependencies\League\Container\Container::__construct(): Implicitly marking parameter $providers as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 42

Deprecated: WP_Rocket\Dependencies\League\Container\Container::__construct(): Implicitly marking parameter $inflectors as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 42

Deprecated: WP_Rocket\Dependencies\League\Container\Container::inflector(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Container.php on line 156

Deprecated: WP_Rocket\Dependencies\League\Container\DefinitionContainerInterface::inflector(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/DefinitionContainerInterface.php on line 19

Deprecated: WP_Rocket\Dependencies\League\Container\Inflector\InflectorAggregate::add(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Inflector/InflectorAggregate.php on line 19

Deprecated: WP_Rocket\Dependencies\League\Container\Inflector\InflectorAggregateInterface::add(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Inflector/InflectorAggregateInterface.php on line 12

Deprecated: WP_Rocket\Dependencies\League\Container\Argument\LiteralArgument::__construct(): Implicitly marking parameter $type as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Argument/LiteralArgument.php on line 27

Deprecated: WP_Rocket\Dependencies\League\Container\Inflector\Inflector::__construct(): Implicitly marking parameter $callback as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/plugins/wp-rocket/inc/Dependencies/League/Container/Inflector/Inflector.php on line 36

Deprecated: array_first(): 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/support/helpers.php on line 112

Deprecated: array_last(): 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/support/helpers.php on line 184

Deprecated: optional(): 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/support/helpers.php on line 722

Deprecated: with(): 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/support/helpers.php on line 1175

Deprecated: App\sage(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/app/helpers.php on line 15

Deprecated: Illuminate\Support\Collection::times(): 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/support/Collection.php on line 117

Deprecated: Illuminate\Support\Collection::filter(): 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/support/Collection.php on line 468

Deprecated: Illuminate\Support\Collection::when(): Implicitly marking parameter $default as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 485

Deprecated: Illuminate\Support\Collection::unless(): Implicitly marking parameter $default as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/support/Collection.php on line 504

Deprecated: Illuminate\Support\Collection::first(): 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/support/Collection.php on line 655

Deprecated: Illuminate\Support\Collection::last(): 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/support/Collection.php on line 905

Deprecated: Illuminate\Support\Collection::sort(): 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/support/Collection.php on line 1444

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: Illuminate\Container\Container::resolving(): 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/container/Container.php on line 958

Deprecated: Illuminate\Container\Container::afterResolving(): 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/container/Container.php on line 978

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

Deprecated: Illuminate\Contracts\Container\Container::resolving(): 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/contracts/Container/Container.php on line 143

Deprecated: Illuminate\Contracts\Container\Container::afterResolving(): 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/contracts/Container/Container.php on line 152

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: Illuminate\Support\Arr::first(): 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/support/Arr.php on line 162

Deprecated: Illuminate\Support\Arr::last(): 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/support/Arr.php on line 191

Deprecated: Roots\Sage\Template\BladeProvider::__construct(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/roots/sage-lib/Template/BladeProvider.php on line 21

Deprecated: Illuminate\View\FileViewFinder::__construct(): Implicitly marking parameter $extensions 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/FileViewFinder.php on line 53

Deprecated: Illuminate\Events\Dispatcher::__construct(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/illuminate/events/Dispatcher.php on line 59

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\Hierarchy::getHierarchy(): Implicitly marking parameter $query 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/Hierarchy.php on line 66

Deprecated: Brain\Hierarchy\Hierarchy::getTemplates(): Implicitly marking parameter $query 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/Hierarchy.php on line 78

Deprecated: Brain\Hierarchy\Hierarchy::parse(): Implicitly marking parameter $query 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/Hierarchy.php on line 90

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 111

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 135

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 167

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 180

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 220

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 260

Warning: Private methods cannot be final as they are never overridden by other classes in /home/staging_interaction/www/wp-content/themes/interaction-metrics/vendor/soberwp/controller/src/Controller.php on line 281

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
How Using a Research Mindset Avoids Huge Survey Blunders

Listening to your customers is smart—as long as you ask thoughtful questions that elicit useful insights. Unfortunately, when it comes to customer surveys, too many companies go through the motions, conducting customer surveys just to say they did it. That’s a big, BIG blunder. To avoid this, customer experience teams need to establish clear goals and put on their research hats. This means tackling customer experience with a research mindset.

Surveys designed without a research mindset are a waste of time and energy for businesses and their customers.

What’s more, when a company fails to approach their survey with a research mindset, they generate junk data and their survey can even tarnish their brand image. Consider for example the latest survey I got from Lively, Inc.

Lively, Inc.’s Dead-in-the-Water Survey

I recently signed up with Lively, Inc., a San Francisco-based startup that provides Health Savings Accounts (HSAs). I created my account but had questions about how to fund it, so I decided to check with my accountant first.

A few weeks later, even though I still hadn’t funded my account or used any other features on the company’s website, I received an email survey asking how likely I would be to recommend Lively to a friend.

How could I answer this question when I hadn’t used their service yet? Did the Lively team think it was important to determine how likely customers are to recommend them based solely on the experience of setting up an account?

Here’s what I suspect: Lively didn’t have a goal with their survey, and they weren’t really trying to learn anything from it. Instead, they assumed that interacting with customers via a survey WAS the end goal.

Bad Surveys Are Common

To be fair, Lively’s co-founders Alex Cyriac and Shobin Uralil (now respectively CEO and COO) don’t claim to be survey experts. Cyriac’s past includes a stint with a payroll and compliance company, while Uralil worked in commercial energy efficiency. Because they are not researchers (and most CEO’s are not) they probably don’t know that sending half-baked surveys is a mistake. And, they don’t know what they don’t know: They don’t know that a survey can be a source of learning that can yield significant business insight.

Lively is not alone in sending “check-the-box-we’re done” non-research driven surveys. GoDaddy, the goliath web-hosting company recently sent me a survey asking how likely I was to recommend a trademark service that they might offer sometime in the future. How could I possibly know whether I’d recommend a service that’s yet to be created?

It’s worth repeating: sending a survey is NOT the end goal, the goal of a survey is to learn.

What Lively Could Learn

For example, Lively could learn why customers open accounts but don’t fund them. Their hypotheses about why this happens might include that customers are:

  1. Confused about how to use the service
  2. Comparing Lively to other options before depositing money
  3. Finding superior options through their employer, a bank, or another company

These are all possibilities worth testing—but that requires a research mindset, so let’s look at that.

Qualities of the Research Mindset

You’ll know you have a research mindset when you: have a goal with a hypothesis, match methods to the investigation of that hypothesis, and confirm or deny that hypothesis through measurement.

For example:

  • If Lively’s goal is to learn about the web interface and the experience of signing up, they should ask about that.
  • If they want to learn why customers don’t fund their account, they should ask about that.

Once they know what the goal of their survey is, they should hypothesize about potential answers to those questions. Then, they should design a 2-3 question survey combining simple rating questions with an open-ended question.

The open-ended question enables them to uncover unknown themes from the verbatims. They could apply intelligent coding (possibly driven by AI, although probably driven by analysts) to measure those emergent themes. This would give Lively a complete, measured view that addresses a goal and provides useful business insight.

What Lively got right is they measured something, namely Net Promoter Score (NPS). What they got wrong is they weren’t measuring something that is relevant and interesting to a specific point in the customer experience.

 More about Your Research Mindset

Here are a few tips for how to adopt a research mindset.

  • Formulate thoughtful hypotheses: Once you have established your goals, create hypotheses that could be disproven by the information you gather. To be able to disprove something requires you to be very clear about what you are testing and requires thoughtful planning.
  • Use the right tool for the job: Keep in mind that surveys are an important and versatile feedback tool, but they are not always the best method. For example, if a company is interested in what services it could add to increase customer retention, interviews or focus groups may be the best methods.
  • Avoid bias: Regardless of the method you use, avoid leading or biased questions. Your job is to elicit accurate data that you can use to grow your company. Even the Net Promoter Score (NPS) question has some bias, it assumes customers are at least somewhat likely to recommend.
  • Target different customer groups differently: Your customers are not homogenous and can be at vastly different stages of their experience with your company. With that in mind, tailor your questions to target customer segments (e.g. new customers, committed customers, former customers, etc.).

Companies that are customer centric often emerge as market leaders, so the payoff is there. To achieve customer centricity, what’s required is intellectual curiosity and a commitment to asking important questions in worthwhile ways.

Lively, find a better question for your new customers. And for all companies: Let’s make the world better through better customer listening!

Categories: Customer Satisfaction Surveys