Skip to content

rajeski/People_Analytics

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 

Repository files navigation

People Analytics, Human Resources Turnover

"Human Resource analytics (HR analytics) is an area in the field of analytics that refers to applying analytic processes to the human resource department of an organization in the hope of improving employee performance and therefore getting a better return on investment. HR analytics does not just deal with gathering data on employee efficiency. Instead, it aims to provide insight into each process by gathering data and then using it to make relevant decisions about how to improve these processes" - Techopedia.

Mindset

  1. Regardless of how 'data-centric' or 'data-driven' any given organization may claim to be, data is only as insightful as the willingness to look at it as objectively as possible, i.e., if management asserts anything along the lines of, "this is way we have always done things around here" and/or "while so-and-so may be rough around the edges, they are a top-performer and cannot be replaced", etc., it should give pause the forces of institutional-inertia are likely entrenched. And, depending on how deeply-entrenched, they might just make the resulting 'data' or findings moot.

'Data-centricism'

  1. Despite the current 'we are a data-centric' spin any organization may claim, data is still data. In order to maximize data's usefulness, meaning must be derived to positively impact real-world issues, i.e., involving people in actual problem-solving to utilize and apply (said) data's usefulness. The companies hiring based on what employees seek (amongst others 'perks') from permanent work-from-home options to child care support to flex-time to up-skilling to better work-life balance, etc. based on the data verifying some of these quality of life issues either currently are and/or will be truly 'data-driven'.

Preliminary Work

  1. In a business-setting, an initial consultation with organizational stakeholders would occur to determine the focus and scope of the project.
  2. Set timeframe(s) for deliverables.
  3. Provide (regular) status updates
  4. Share initial findings with the Executive Team, e.g., Cost-benefit Analysis including estimates on maintaining status quo versus Change Management initiatives.
  5. Upon approval, re-purpose initial findings to be shared with Technical and/or Non-technical staff.

Objective(s)

  1. Understand what are the factors contributing to employee turnover.
  2. Create a predictive model to determine if a certain employee (type) will leave or stay.

Analysis

Examined overall employee satisfaction, tenure, and evaluation to determine if they are/were the three main influences determining staff departures.

Conclusion(s):

Employee Satisfaction, Years At Company, Evaluation are/were the biggest factors regarding staff turnover.

  1. Low to medium salaried employees had higher attrition rates. Conversely, higher-salaried employees had lower attrition rates.
  2. Highest employee turnover (ranked order) Sales, Technical, Support. Conversely, Management had the lowest employee turnover.
  3. High employee turnover 2, 6, 7 projects; most employees with 3, 4, 5 projects remained; all employees with 7 projects left the company.
  4. Low to high performance employees tended to leave the most; employee evaluations between 0.6-0.8 tended to remain at the company.
  5. Employees with less hours of work (150 hours or less) or (250 hours or more) had higher attrition rates.
  6. Low satisfaction level employees (0.2 or less) or (0.3 to 0.5) and high-satisfaction level employees (0.7 or more) all left the company at higher rates.
  7. More than 1/2 of employees with 4 and 5 years tenure left the company.
  8. An average evaluation of roughly 70% meant an employee was likely to stay (even with difference project counts); the data skews towards a high turnover rate after 3 projects or two projects and a lower employee evaluation; employees with more than 3 projects and higher employee evaluations also had higher attrition rates.
  9. Using a Random Forest was the most accurate model for data modeling purposes.

Suggestions:

Utilize the Kirkpatrick Evaluation Model as part of conducting a Root-cause Analysis -

  1. Reaction - Conduct a company-wide survey of all employees
  2. Learning - Based on the survey's results implement on-the-job training aimed at reducing attrition rates
  3. Behavior - Monitor if desired improvements are being incorporated or if there is still cultural resistance (to reducing employee turnover)
  4. Results - Reduced employee turnover; increased employee evaluation scores

The above should center on, what are the knowledge, motivation, and organizational solutions to these barriers?

Areas to address include:

  1. Overall attrition-rates
  2. Sales, Technical and Support turnover rates, i.e., KPI's; Salary; Management; Career Mobility; finding the possible causes / solutions?
  3. Project-related turnover rates; lack of support; level of difficulties; timelines; again, finding the possible causes / solutions?
  4. Employee satisfaction; what (if anything) is being done about this? Re-assess management (including Human Resources' policies to find the possible areas where this can be addressed and improved).
  5. Employee retention, i.e., in the 4 to 5 year-segment means knowledge, motivation, and organizational is being lost (aside from the people who left with such).
  6. Examining why project count; employee evaluation and attrition are correlated and determining (what, if/any) causation.

Libraries:

Matplotlib (Data Visualizations)

Numpy (Mathematics)

Pandas (Data Analysis)

Seaborn (Data Visualization)

Scikit-learn (Predictive Analysis)

References:

Clark, R. E., & Estes, F. (2008). Turning research into results: A guide to selecting the right performance solutions. Atlanta, GA: CEP Press.

Hofstede, G. H. (2001). Culture's consequences: Comparing values, behaviors, institutions, and organizations across nations (2nd ed.). Thousand Oaks, CA: Sage Publications.

Kirkpatrick, J. D., & Kirkpatrick, W. K. (2016). Kirkpatrick's four levels of training evaluation. Alexandria, VA: ATD Press.

Appendix:

People Analytics -

  1. Workforce Planning
  2. Talent Sourcing
  3. Hiring Practices
  4. Onboarding / Engagement
  5. Performance Measurement
  6. Attrition / Retention
  7. Employee Wellness

Currently, it seems points 1, 3, 4, 5, 6 and 7 all need detailed, Root-cause Analysis with point 2 being set aside from now (although it could also be an issue influencing attrition).

Proposed Preliminary Discussion with Management would be focused on -

Institutional-inertia, e.g., 'this is the way we have always done it, etc.'

Post-findings Discussion would be focused on -

Reason why these findings (unfortunately) are unsurprising.

Examples include;

  1. Compensation - examining pay-disparities (what are they?)
  2. Mentorship - are new employees assigned tenured staff to help them to become long-term / successful employees? If, so what is the cost-benefit analysis of this 'initiative'? If not, again, what is the cost-benefit analysis of not implementing this initiative?
  3. Promotions - what tangible career advancement opportunities does the company offer? How are these structured? What are the mechanisms for enacting them and ensuring they are implemented as objectively as possible?
  4. Management - has a toxic work environment been ignored, e.g., in the Sales, Technical and Support Departments? If so, why has this happened and what are the root-causes, i.e., nepotism, etc.?
  5. Incentives - (classic) carrot versus stick management, i.e., Sales (unrealistic targets); Technical (issues with product releases and not listening to End-user feedback, etc.) and Support (are bugs and/or other issues being reported but ignored?)

SWOT Analysis

Project Strengths:

  1. Working in isolation without being influenced by any unintentional bias, e.g., caused by meeting or speaking with any given employee

Project Weaknesses:

  1. Conversely, working in isolation, i.e., just looking at the data 'clinically' could also not be without any challenges

Project Opportunities:

  1. The enclosed findings offer an opportunity for this organization to not just conduct an audit but undertake an organizational change initiative

Project Weaknesses:

  1. Conversely, the enclosed findings could be seen as a threat by stakeholders resistant to undertaking an organizational change initiative

Data Visualizations

  1. Heatmap_Correlation_Matrix (Displaying the values based on the color-shading and darkness). Note: The darkness, i.e., satisfaction and turnover.
  2. Avg_Monthly_Hours_Distribution (Displaying a bimodal data-distribution). Addressing the polarity of too few versus too many hours and creating a better balance is an area to address and remedy.
  3. Emp_Satisfaction_Distribution (Left-skewed data-distribution).
  4. Emp_Project_Distribution (Right-skewed data-distribution). Compare these two charts and their interrelationship, i.e., dynamic between projects and employee satisfaction.
  5. Project_Count(Project count visualization)
  6. Employee_Tenure (Employee Turnover) Note: The highest-level of employee turnover peaks in Year Three with the first two years ascending to that apex. This raises of number of relevant questions from employee on-boarding programs and follow-on training to if more senior-staff are assigned to (even informall) guide and/or mentor junior-staff members. If so, this warrants closer examination, e.g., how are senior-staff assigned; are 360 degree reviews involved, etc. If not, why? Is it a budgetary issue and/or more senior-staff are resistance; un-trained, etc. to actively support junior-staff? Finally, evaluating the effectiveness of assigning junior-staff projects is also another areas to consider for futher review.
  7. Work_Accidents (Work Accidents) Note: Briefly, one out of six employees, i.e., just under 17% are involved in an on-site work accident.
  8. Depart_Turnoover (Departmental Turnover) Note: The three highest areas are Sales; Technical and Support.
  9. Salary_Turnover (Employee Salary to Turnover) Note: This goes without saying and no matter how 'obviousness' this may seem, the importance of emphasizing this reality cannot be overstated, i.e., economic-determination is a fundamental reason 'why' people work!
  10. Salary_Attrition (Employee Salary to Attrition by Tenure) From the lowest to the highest salary-ranges, Year 3 and Year 2 seems to be problematic for this organization. Related to the above points; is this attributed to project-count and/or employee / stakeholder engagement (or lack thereof?)
  11. Depart_Turnover (Departmental Turnover) Again, look at the three areas of highest employee turnover (Sales; Technical and Support) versus the lowest (Management) and it is clearly evident these three departments are problematic.
  12. Emp_Pro_Turnover Project count to turnover, what is driving this? Workload; lack of support; expectations; limited resources; poor management? This area alone warrants closer examination. (Employee Project Count to Turnover)
  13. Emp_Ev_Turnover Lowest (i.e., decreased opportunities; poor management; working conditions, etc.?) and highest (increased opportunities; better management; working conditions, etc.?) employee evaluations result in the greatest turnover. (Employee Evaluation to Turnover)
  14. A_E_Hrs_Turnover Note: Underutilization, i.e., not enough hours and over-utilization, i.e., too many hours result in the two main polarities within this category. (Average Employee Monthly Hours to Turnover)
  15. Emp_Turnover_Ten(Employee Turnover to Tenure)
  16. Emp_WA_Turnover Whether no accidents and/or one accident, non-Management turnover is significantly higher than Management turnover and could be attributable to the data and supporting details provided above. (Employee Work Accidents to Turnover)
  17. Em_Pro_Turnover Employees who received a promotion tended to stay at the company (Employee Promotion to Turnover)
  18. Emp_Project_Eval Employees with an evaluation-average of roughly 70% tended to stay at the company; the data skews in employee turnover after 3 projects; employees with two projects and a lower evaluation left the company; employees with more than 3 projects and a higher evaluation left the company. (Employee Project Count to Evaluation)
  19. Project_Avg_Hrs The average employees worked about 200 hours/month remained at the company; employee turnover for around 150 hours/month or 250 hours/month worked resulted in a higher attrition rate. (Project Count to Average Monthly Hours)
  20. Emp_Sat_Eval (Worked and Dissatisfied with...) Employee satisfaction was below 0.2; evaluations were greater than 0.75, could indicate an employee who put in the work but was unsatisfied with the job, the work environment and/or the company; (Worked and Dissatisfied because...) Employee satisfaction between about 0.35 to 0.45; evaluations were below 0.58, could indicate an employee who received a poor evaluation and as a result felt bad about it or for being at the company itself; (Worked and Satisfied about...) Employee satisfaction between 0.7 to 1.0; evaluations were greater than 0.8, could indicate an employee who was optimal due to being both satisfied with this job who also received a high performance evaluation (which could be self-reinforcing). (Employee Satisfaction to Evaluation)
  21. Emp_Turnover_Cl This chart provides a color-based representation (Employee Turnover Cluster)

Data Modeling -

  1. ROC_GraphChecking for false-positive rates. (ROC Graph)
  2. Dec_Tree_ClassEmployee Satisfaction, Years At Company, Evaluation are the biggest factors regarding staff turnover. (Feature Importance by Decision Tree Classifier)

Conclusions -

  1. Conclusions Conclusions (Embedded Jupyter Notebook)

Misc. -

  1. Dummy_Var (Dummy, i.e., Test Data Variables)

END