Filtering survey analytics

 Great people analytics can help HR admins, managers, and executives to make informed decisions about your employees or workforce. Especially in bigger companies, filtering survey results becomes more important. With the new survey analytics, you can now use combinable filters that are applied after visibility filters and before further processing (e.g., segmentation) of results.

You can read more on how to interpret and work with the results here.

Just a note that Analytics (except for the 'Participation Rate'), are based on the 'snapshot' taken when the response was given. Therefore any changes made in a user’s profile settings during the course of the survey round will not presently be indicated in the analytics. Our product team are currently working on a feature to allow for survey data filtering based on the latest data of users. This is currently the case with the 'Participation Rate' which reflects updated user profile settings in real time.

Filtering Logic

You can filter the list, heatmap, or comments by different parameters and also combine these filters. To prevent individual respondents from being identified with a combination of different filters, Leapsome will dynamically increase the anonymity threshold you have set once you apply more than one demographic filter (such as 'department' or 'manager'). This is also explained in the tool if you hover over the small triangle on the top right side of the survey results. 

In the heatmap, the filtering logic works as follows: If you filter for two or more of the same filter (e.g. two teams) Leapsome will apply an OR logic, meaning that it will show people who are either in Team 1 or in Team 2. If you combine different filters, e.g. a team and an office location, it will apply an AND logic. This means you would only see the answers that came from people who are in e.g. Team 1 and work in the London office. 

Please note: After a survey round has been closed, if users are deactivated, when filtering by teams, the deactivated users do not show in the participation rate (as deactivating a user removes them from the team assignments). 

Filter and segmentation options

You can filter...

...the list 

• by survey round
• by question
• by category
• by team 
• by manager 
• by user level
• by office location
• by gender
• by age
• by tenure
• by user (if the survey is non-anonymous)
• by custom attributes

...the comments

• by team 
• by manager
• by survey round
• by sentiment
• by question
• by user level
• by gender
• by age
• by tenure
• by office location
• by conversation status
• by comment topic
• by comment text
• by comment priority
• by conversation assignee
• by user (if the survey is non-anonymous)
• by custom attributes

...the heatmap

• by team
• by manager
• by survey round
• by question
• by category
• by level
• by gender
• by age
• by tenure
• by office location
• by user (if the survey is non-anonymous)
• by custom attributes

You can also segment the heatmap

• by team
• by manager
• by performance quantile of the respondent (which takes the latest manager score of a review and groups survey respondents into quantiles)
• by tenure
• by office location
• by level
• by gender
• by age
• by custom attributes

Please note: When you segment the heatmap with "group by manager", the manager is not included in the results, but if you "group by team" then the manager is included in the results. 

For both list and heatmap you have the further option to sort the results by question, by category, or by total score across all questions for a specific group, location, or round for instance. 

If the anonymity threshold is not met, then admins and survey owners will see the name of the team and N/A in the heatmap results. You will also be shown an icon letting you know that the anonymity threshold was not met, which is why survey results for select teams are not visible. 

How team filters are affected by filters

The heatmap team segments show team memberships based at the time of submitting the answer.
The list view (& Filters) use the current team assignments. In the event that employees switch teams, the results between the heatmap and list view may differ to reflect team assignment based on when the survey was submitted, or what the current team assignment is.

For filtering (participation rate or heatmap), the system first checks which users currently fall within that filter and then checks all answers by those users. For segmentation, the system checks all answers that were submitted by users who were part of that team at the time of submitting the survey. If you then apply a filter on top, the system first gets the answers of all users that are part of that team today, then attributes the answers to the teams based on the team membership at the time of answering the survey.

Comment Priority

You can tag a comment as important and be able to filter for the important comments through the filter “comment priority.” In this way, if a comment seems that it needs a follow-up, or you find a recurring theme in the comments that you may want to filter for more easily to create an action plan from, the filter comment priority > important, is a quick way to view all those comments concurrently. 

Save and share filters

The filters you apply under any one view like 'Heatmap' will persist when you switch to any other view like 'Comments' or 'Radar'.  However, we recommend saving filter combinations if you find yourself using certain filter combinations more frequently. 

You can save your filter combinations and share them with other users in the platform. Simply click on “Save filters” to save, and, if applicable, you share a filter combination with colleagues by entering their names. You can use the 'Filter’ drop-down menu to choose from a list of filters you’ve saved and / or colleagues have shared with you.