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 To Implement A Workplace Diversity Survey For DEI Success

Amazon CEO Jeff Bezos said, “It’s not only that diversity and inclusion are good for our business. It’s more fundamental than that — it’s simply right.” DEI programs may be right, but it’s no secret that they are controversial in the workforce. Employees are often skeptical when a workplace diversity survey is introduced, which makes it difficult for DEI programs to flourish.

To solve this, here’s our guide to implementing a workplace diversity survey that will give you actionable results and lay the foundation for a successful DEI program.

But first, consider this truth: without scientific data, DEI programs are nearly guaranteed to flop.

Why? Because it takes empirical data to ensure your managers are truly on board with upcoming initiatives. Moreover, it takes sound data to craft DEI programs that meet employees’ preferences and needs.

illustration of people talking about dei definitions for the workplace diversity survey from Interaction Metrics

DEI: Definitions

Definitions matter. DEI stands for Diversity, Equity, and Inclusion, three connected goals that many companies value. These goals focus on upholding individuals of different races, sexual orientations, and backgrounds.

Diversity refers to who your employees are. Are men and women equally represented? Are nonbinary individuals represented? Are your employees mostly from one generation, or is there an even spread across generations? Do they come from homogenous ethnic and religious backgrounds, or is there a variety?

Equity considers employees’ diverse backgrounds and provides different levels of support so that their outcomes are equal.

Inclusion refers to how your employees experience their jobs and company culture. Do employees feel their voice is heard? Do they think their contributions matter? Do they feel like they are a part of meetings and events?

illustration of man thinking and questioning DEI initiatives

DEI: A Mixed, Complicated Bag

When DEI programs are first introduced at organizations, many employees express concerns about reverse discrimination, retaliation, tokenism, lowered standards, and political agendas.

In fact, Dobbin and Kalev pointed out in their excellent Harvard Business Review article that many diversity programs fail to increase diversity in the workforce. They write that “Laboratory studies show that this kind of force-feeding can activate bias rather than stamp it out. As social scientists have found, people often rebel against rules to assert their autonomy. Try to coerce me to do X, Y, or Z, and I’ll do the opposite just to prove that I’m my own person.”

And yet while Dobbin and Kalev’s article finds grave downsides to diversity programs, other research finds that DEI efforts are quite popular. For instance, according to Pew Research Center, fully 56 percent of U.S. workers say that efforts to increase diversity, equity, and inclusion in the workplace are good. But the same study finds that only 32 percent of workers say it’s very important to work for a company with a diverse workforce.

In sum, DEI is a mixed, complicated bag. While most workers support DEI efforts, they are significantly less likely to see a need for them in their workplace.

Meanwhile there is often company-wide confusion regarding the basics of DEI values and how to roll out DEI initiatives. Forrester Research finds, “Whether it’s fear of alienating a portion of their customer base by taking a stand on the issues of the day or a lack of clarity around how to operationalize inclusion, we’ve seen many organizations make things worse, not better, in their initial attempts.”

Data-Driven DEI

Given the skepticism of, resistance to, and bad execution of DEI programs, establishing a foundation of objective facts is essential.

Implementing an impartial workplace diversity survey builds your foundation because employees are less likely to view DEI programs as part of management’s political agenda if they are invited to share their voices first. Plus, a baseline of employees’ opinions on DEI allows companies to gauge changes in employees’ perceptions over time.

illustration of a survey email invitation from Interaction Metrics

First Things First: Your Survey Email Invite

Achieving scientific (not subjective) data is a multi-faceted project that starts by setting the right tone in the email that asks employees to take your workplace diversity survey. Let staff know that their answers will improve the workplace for everyone. And be sure to:

  • Use disarming language, such as: “All opinions count, and your perspective matters.” Showing the importance of your survey in a neutral way encourages employees to respond and share their feelings.
  • Reassure employees upfront that their answers cannot and will not be used against them. And if you are using a third party to implement your survey, emphasize that to employees.
  • Use engaging, strong words in the links to your survey.
  • Offer an incentive like an Amazon gift card or raffle ticket giveaway. Employees are already burdened with the responsibilities of their jobs. Make the survey a fun and celebratory event for them, not another chore. (And as soon as the survey window closes, be sure to send out the gift cards, select a winner, etc.)
  • Underscore the survey’s anonymity, objectivity, or the fact that it’s administered by a third party in the email signature.
  • Always use a postscript under the signature – it’s a classic direct marketing method proven to boost response rates. Yielding a high response rate is essential because this helps ensure your data is statistically valid.

illustration of employees responding to a workplace diversity survey from Interaction Metrics

Workplace Diversity Survey: 11 Best Practices

Here are eleven tips on how to design your workplace diversity survey that will ensure objective data and that all employees’ voices are heard.

Tip 1: Guarantee anonymity, always. This one is non-negotiable.

Employees will not feel safe enough to voice their honest opinions unless you can guarantee that their answers cannot be linked back to them in any way.

Tip 2: Hire a third party to implement your survey. When it comes to a sensitive topic like DEI, employees are more likely to trust an impartial third party with no stakes in their company’s workplace culture and that can’t be accused of bias.

Tip 3: Only ask for the essentials, especially when it comes to demographics. Don’t unnecessarily drill down into the minutiae unless you plan to use that information.

Tip 4: Order your questions thoughtfully. Put open-ended questions in the middle of your survey instead of at the end to ensure employees have time to answer them. When mined properly, open-ended text offers a gold mine of insights.

Tip 5: Tell employees what to expect because they are less likely to start a task if they have no idea how long it will take or what they’ll be required to do.

Be upfront about how many questions your workplace diversity survey consists of.

You might even describe the content and flow of your survey in its opening screen. For example, if there are 11 rating questions, followed by two open-ended questions, and five yes/no questions at the end, let employees know.

Tip 6: Use a balanced rating scale that reflects how employees actually express themselves. For example, instead of asking employees if they “strongly disagree” or “neither agree nor disagree” with a statement, provide answer options that sound familiar.

Rating scales such as “Bad”, “Poor,” “OK,” “Good,” and “Great” tend to collect accurate data because they reflect the way your staff thinks.

As much as possible, use language in your surveys as though you’re talking in person.

Tip 7: Say thank you! Be sure to thank respondents for their feedback in the email invite and at the end of the survey.

Tip 8: Connect your survey to specific DEI goals. For instance, if your organization’s goal is to increase the number of women in the workforce, ask questions about how many women have applied for positions and how receptive your working environment is for women.

Tip 9: Test your workplace diversity survey for bias. Bias is the scourge of any survey, but it’s especially easy for it to sneak into a workplace diversity survey that touches on sensitive topics.

Have a diverse group of individuals (outside of your department) read through your survey questions to check for unintended biases in your wording.

Tip 10: When possible, make sure that your survey is accessible to employees with disabilities. Offer different visual, auditory, and text-based formats.

Tip 11: Include questions that let you benchmark your company’s diversity data against your standards and subsequent survey data. You want to be able to track and show your progress over time!

Your Workplace Diversity Survey: Six Areas to Consider

DEI goals will vary from company to company, and template surveys never deliver the precise insights your company needs to grow. But while your approach needs to be customized to your core mission, here are six question prompts to consider on your path toward scientific data.

Remember, the goal is to find out how your staff genuinely experiences the workplace you provide – and what their ideas are for how you could do better.

How many times have you witnessed harassment in the workplace?

Why this question works: Having employees think critically about what they’ve witnessed is a great way to measure aggravations in the workplace objectively and prepares them to share more in the open-ended survey questions.

Do you feel comfortable talking about issues related to racial equity, harassment, and diversity with your manager?

Why this question works: The relationship between employees and supervisors is critical. This question can help you determine whether leadership needs training.

Have you felt discriminated against for the following: gender, age, ethnicity, sexual orientation, religion, or another reason?

Why this question works: Discrimination may be ongoing in the workplace, and employees may not feel safe enough to report it. An anonymous, impartial survey may be the only place they can honestly report discrimination they’ve experienced.

Do you hide things about yourself to fit in at work?

Why this question works: Inclusion means employees should feel comfortable being authentic in the workplace. If they aren’t, then it’s clear where to focus your DEI efforts.

Does your job inspire you to be your best self?

Why this question works: Companies thrive when their employees thrive. This question helps you gauge how connected employees feel to your company’s mission.

Would you recommend this company as an inclusive workplace?

Why this question works: Akin to the Net Promoter Question, this question asks whether your employees would encourage their peers to join your company.

illustration showing the process of a workplace diversity survey at Interaction Metrics

Your Survey is Just the Start

Too often, companies launch DEI programs without first conducting a workplace diversity survey and establishing how employees feel. The result is a misalignment between executives and the workforce.

By starting the process with solid data you’ll know what your employees are thinking and rather than sweeping employees’ skepticism under the rug, you’ll develop DEI initiatives based on evidence.

This data-driven approach produces benefits, including:

  • Ease in getting executives’ buy-in
  • Clear, targeted next steps
  • Ability to test and measure the impact of DEI programs

When employees are skeptical of a new program, that’s an opportunity to grow — but only when leaders address skepticism head-on.

While it’s comforting when everyone agrees with a new initiative, addressing criticism immediately ensures that programs remain realistic. Realism based on employees’ thoughts and opinions is the key ingredient to building positive values around DEI that last.

Interested in conducting a workplace diversity survey at your company? Get in touch.

Categories: Employee Engagement