Follow

Guide to impact analysis at different organizational levels


Impact analysis for the company overall versus different organizational levels?

Have you ever been asked to run the driver analysis for a specific department, team or location? We break down the scenario so you can decide if you want to go that deep!

 

Setting the scene

Scenario:

  • “We have different departments and we feel they are different enough to have a separate driver analysis run”

Reality:

  • Driver analysis is most statistically reliable and powerful with more respondents (the more the better usually)
  • Driver analysis works by analyzing patterns between responses (including responses from individuals in different departments)
  • If everybody within a specific department responds quite uniformly low, or high, on certain factors, a department specific driver analysis will not pick up important patterns relative to other departments
  • To identify these differences it is better to run the driver analysis at the overall level because it will be more sensitive to important variation between groups

 

An example (a real one!)

In this example, we see how the focus changes depending on whether the driver analysis is calculated at the company overall, or calculated at the Department level. Specifically, we look at how the Sales Department scored compared to the company overall on the question: “The leaders at Hooli demonstrate that people are important to the company's success”, which turns out to be a top 5 driver for the company overall.

 

 Calculating the driver analysis at the “Department” level

“The leaders at Hooli demonstrate that people are important to the company's success”

Group

Favourable Score

Impact

Overall

69%

 

Sales Department

65%

0.30 (Moderate)

 

What you would see in your results:

  • Sales are 4 points below the company overall, with a Moderate (bordering on Low) Impact
  • This result would mean that this area of “The leaders at Hooli demonstrate that people are important to the company's success” would slip down to the bottom of the list of potential areas of focus for the Sales Department. However, this is an area we know is a common driver of Engagement, and a top 5 driver of Engagement at this company (Top driver of Engagement in What New Tech Employees Need)
  • People reviewing the results would typically skip over this result and say the Sales department don’t need to focus on it!

 

 
Calculating the driver analysis at the “Organizational” level

Group

Favourable Score

Impact

Overall

69%

 0.47 (High)

Sales Department

65%

 


What you would see in your results:

  • Sales score 4 points below the company overall, with a High Impact
  • People reviewing the results would typically say this is something the Sales department should focus on!

 

Tying it all together

Group

Favourable Score

Impact

Summary

Focus?

Overall

69%

0.47

(High)

   

Sales

65%

 

Low Performance, High Impact

Should be a focus!

Engineering

60%

 

Low Performance, High Impact

Should be a focus!

Marketing

63%

 

Low Performance, High Impact

Should be a focus!

All others

73%

 

High Performance, High Impact

Not a focus!


What you would see in your results:

  • People reviewing the results would typically say this is something the Sales, Engineering and Marketing departments definitely should focus on!
  • Bonus: it is something they can focus on together!

 

Summary

Running the driver analysis at the company overall level means that you’ll be able to find the patterns that exist across all groups, while nuances will be captured by the performance (favorable) scores for each of the groups.

Running a driver analysis at a specific level means you may miss out on patterns that exist between groups. While you’ll be able to find patterns within that group, with smaller groups, you might be better served with using the performance (favorable) scores to identify those nuances.

See Also:

 

If you do have a requirement to run the driver analysis for specific demographic groups, such as Business Unit, Department, Team or Location, please reach out to Culture Amp Product Support.

 

Here's how it would work once enabled
Demographic driver analysis will apply to demographic values that are directly and indirectly contained within the configured driver demographic - e.g. Business Unit.

Values directly contained example:
Business Unit configured as driver demographic
Business Unit includes Product Group, Customer Group and Org Group
You would get demographic level drivers for reports filtered on Business Unit=Product Group, Business Unit=Customer Group and Business Unit=Org Group.  Any other filter would show All Company drivers


Values indirectly contained example:
Business Unit configured as driver demographic
Business Unit includes Product Group, Customer Group and Org Group
A Product Manager for example is inside of Product Group, so we look at the responses and detect that every Product Manager is inside of Product Group and show the Product Group drivers instead of the All Company drivers

*If a demographic contains people from multiple groups, eg. Design practice is both Customer Group and Product Group, it will default to All Company drivers (i.e if anything less than 100% of responses within a filter are inside a driver demographic, All Company drivers will be used)

 

How will report viewers know?

Everywhere driver questions are displayed we call out what demographic is used for the calculation in the user interface:
Impact_Analysis_call_out.jpg

 

 



Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments