Every week, bi-weekly or monthly your employees can fill in the engagement survey. But how should you analyse the results? If you want to learn more about how the score is calculated, read this article.
Go to Engagement and you'll get this engagement overview:

Average Score

On the top left you see the average score. This is the average engagement score, taking into account all engagement answers, calculated over the last 4 engagement sessions on a rolling basis

Next to the average score you see the amount of pulsed questions. These are all the questions that already have been sent to your employees since your company started working with the intuo platform. Underneath you see the amount of questions that have been answered. In this example the company has 7 employees and 5 of them are inactive. This means that 5 of the employees missed more than 3 pulses on a row.
Depending on what the admin of the platform has decided, you will be able to click on inactive users and you'll get a list of the inactive users.

Important: This results will be filtered by the relevant teams if the user is not an admin. In this case, the user will see the results of teams he's either part of (if a regular team member) or the teams he's leading in the hierarchy (if a team lead)

Engagement Score Graph

On the top right you see a graph with the evolution of the engagement score. This graph breaks up the engagement score in months. This is in contrast to see the engagement score you see on the left hand side, in the green circle. The engagement score on the left depicts the average score of your teams over the last 4 engagement sessions, on a rolling basis.

In order to calculate the monthly engagement scores, we take the scores on each question asked in that month - for all the applicable users - and then take the average. In other words, each question has the same weight in the overall monthly engagement score.

As a team lead or admin, you will see these scores when you hover a monthly data point: 

  • Team name(s): If you select a team in the filter, the score of that team will be displayed in the graph as well. If you are a team lead of multiple teams, you will be able to select multiple teams, than you see different team names on the graph.
  • Your teams score: The Your teams score shows the overall engagement score of all your team members in that month. For example if you are team lead of two teams, the score depicted will be a combination of all the unique members in those two teams. Important: if your team is smaller than three members(*), the score won't be visible because of privacy reasons. The score will be taken into account in the company score.
  • Company score: The company score shows the overall engagement score of all the company's participants in that month, unregarded of the teams.
  • Your score: This is how your overall engagement score in that month compares to the other scores.

By clicking in the legend on one of the above scores, you hide that score on the graph. For example in the example bellow the Company score is hided. Important: if you hide this score and afterwards click on an engagement driver this score will stay hidden.

On the graph you also see the response rate. To calculate the response rate, we count all the answered and skipped questions, and take the ratio with the total answers that have been questioned. For example, in a certain month:

  • User 1: 5 questions were asked. Answered 3 and skipped 1, then left the survey. Their response rate will be 4/5 or 80%
  • User 2: 10 questions were asked. Answered 9 and skipped 1. Their response rate will be 10/10 or 100%.
  • The overall response rate for the above example will be 14/15 or 93,3%

Engagement Drivers

Underneath the average score and the engagement score graph, you find all the engagement drivers/topics. (These drivers can be changed by the admins in the engagement studio).

Per engagement driver you see a percentage in a green circle. This percentage indicate the average score of the last 4 engagement surveys on a rolling basis for that specific driver. For example in the example on the screenshot, 50% for the engagement driver Ambassadorship.
The percentage on the right of each engagement driver compares the percentage in the green circle with the previous engagement period value. In this example the minus 12% indicate a decrease of 12% in comparison with the previous 4 engagement surveys.

If you click on a specific engagement driver you can get a more in depth analysis of each engagement driver. If you want to read more about how you should analyse these results, read this helpdesk article

Comments

If you scroll down in the engagement overview, you see all the comments employees gave. These comments are always visible for the admin, but can also be visible for teamleaders (this is a setting in the Studio). They will of course only see the comments of their team members and not of everybody in the company.

NB: What is described above refers to the initial screen when accessing the engagement overview. It's possible to filter on different periods, in which case the data will be filtered based that period!

Filters

If you click on the filter icon (on top right) you're able to filter the engagement results on teams and/or pulses.

  • Teams: admins can filter on all teams on the platform. Teamleaders can only filter on the team(s) he's teamleader of. Remark: if the team is in light grey, it means that less than three people(*) have filled in the engagement survey. Due to privacy concerns you won't be able to select these teams.
  • Include Child Teams: Once you've selected a team (or teams) you will see an extra option to include the child teams. That way you can have the average score of an entire team hierarchy
  • Don't show team leader data in results: You can option to leave out the team leader data.
  • Pulses: you can specify the period of time you want to see the results of. You can select the dates or the number of pulses you want to go back in the past.

If you click on apply filters, this filter will be applicable until you clear all filters.

(*) This refers to the default value. This can be changed in the Studio.

Did this answer your question?