When setting up your employee data for a survey, it's always worth considering how you plan to roll out results to employees. This is especially important if you're planning on having your managers sign in to Culture Amp as you need to ensure that you have the right demographic data to let managers see their results.
An example company
ACME is structured as a set of departments. Each department is broken into teams and some of these teams have sub-teams within them.
Each of these groups within the organization is managed by an employee. For simplicity, let's zoom in on the Engineering department to see which managers are responsible for each area.
Jimmy Brown is the head of the engineering department. The two teams inside Engineering are the Product Dev team and the Tech Support team which are managed by William Collins and Janice Starks respectively. The Product Dev team includes the User Experience Sub-team and Core Dev sub-team which are managed by Bobby Byrd and Jenny Griggs respectively. The employee data file for this structure is outlined below - the managers and the groups they manage are bolded for clarity.
You'll note that not all employees have values for each of the demographics - Dorothy (the CEO) doesn't have a Team, Sub-Team, or Manager demographic which is to be expected.
The rollout approach
As described in the Analyze and Share guidelines, the most typical approach to rolling out results is to:
- Give HR Manager access to everything. This is usually done by making them survey administrators
- Give Department heads access to all of the results in their own departments (but not other departments)
- Give Managers access to all of the results for employees that report to them directly and indirectly (but not the results for other managers)
To support this configuration, Culture Amp provides the ability to define a View of the results. The view specifies a single demographic that results are limited to. This view is then assigned to one or more employees. For ACME, this would mean:
- Jimmy Brown => Is given access to the results restricted by the Department: Engineering demographic
- William Collins => Is given access to results restricted by the the Team: Product Dev demographic
- Bobby Byrd => Is given access to the results restricted by the Sub-Team: User Experience demographic
- Jenny Griggs => Is given access to the results restricted by the Sub-Team: Core Dev demographic
An example of a department report would look like this:
Jimmy will be able to filter to all of the various demographics (Team, Sub-Team etc) within the engineering department, however, he will not be able to see the results for other departments at ACME.
Simulating Manager Views with your data
It's possible to simulate which data each manager will be given access to by filtering your employee file by the relevant demographic.
|For William Collins...||For Jenny Griggs...|
It's possible to assign managers multiple views of the data. This is often useful when you'd also like managers to see the results for their direct reports only. In this example, we may give Jenny Griggs two views of the data - one restricted by Sub-Team: Core Dev, and another restricted by Manager: Jenny Griggs.