As an administrator, the dashboard product settings can be accessed and configured by clicking on the Administration option in the left menu, followed by the selecting the Data settings option and you will find them under Dashboard tab. There are four components to the dashboard settings, which will be covered in this article.

  • Driver sorting
  • Engagement score
  • Comment date visibility
  • Score aggregation for drivers

Driver sorting

The driver sorting option controls the default sorting of drivers that managers in your organisation will see on their dashboard when they log into Peakon. 

The standard setting is to sort the drivers by Priority, however it's also possible to sort drivers By score or By difference to benchmark

Managers will still be able to sort drivers by any three of these options, but will receive the view selected for this setting by default with every new login session.

Engagement score

This setting controls the leading score shown on dashboards for any engagement, driver, or sub-driver question. The average or e/NPS score can be shown by default on dashboards.  

Managers will also have the option to switch between the two options on their dashboards but will receive the view selected in this setting by default with every new login session.

When using the eNPS as the default leading score, NPS will be shown on dashboards for all questions excluding the core engagement question ("How likely is it you would recommend [company name] as a place to work?"). For this core engagement question, eNPS will be used instead as this is the standard terminology used to refer to this question specifically.

Comment date visibility

There are two options for how dates are displayed on comments:

  • Comment date (standard) - Comment date is displayed when listing comments.
  • Round end date - Round end date is displayed when listing comments.

By default, the comment date option will be selected. This means that the comments will display the date the comment was entered into Peakon. If you prefer, it's also possible to select the Round end date option which will show the date the survey round closed on comments. This option then marks all comment dates according to the survey round they belong to.

Score aggregation for drivers

By default, Peakon aggregates driver and subdriver scores to give the driver a score based on the average scores given for both the driver and subdriver questions. This setting allows the scores to be separated meaning that they will not be aggregated.

To illustrate with an example, imagine a company with just two employees (employee A and employee B), and answers for the autonomy driver questions as follows: 

Aggregated score

When using the aggregated score, Peakon would calculate the Autonomy score as follows:

Employee A:  (7 + 9 + 5) / 3 = 7
Employee B:  (5 + 10 + 9) / 3 = 8  
The aggregated score for autonomy would be (7 + 8) / 2 = 7,5.

Separated score

When using the separated score, Peakon would calculate the Autonomy score as follows:

Employee A: = 7
Employee B: = 5
The average score for autonomy would be (7 + 5) /2 = 6. 

The average subdriver scores would be calculated in the same way, with "Remote work" being 9,5 and "Flexibility" being 7.

When to use the aggregated score vs separated score

The default setting on Peakon is for scores to be aggregated, however, in some cases you may wish to have the scores separated. Below are some considerations for both options:

Considerations for using the "Aggregated" scores option

  • The main advantage of using the aggregated score is that the driver score is then a measurement of multiple scores. This enables you to focus on the driver score as a holistic measurement of a set of questions. 
  • As the driver scores are representative of both the driver and sub-driver questions. By giving weighting to all questions within a particular driver, score variability is decreased
  • The driver score will therefore experience less extreme values and changes 
  • The driver score is less sensitive to any question customisation to subdriver questions. However, if you plan on customising any driver or subdriver questions, please reach out to your Customer Success Manager who will be able to assist you
  • In some cases, the main driver question may be turned off but the subdriver questions are left on. This can lead to a situation where the driver and subdriver both appear as priorities even though they are based upon the same question

Considerations for using the "Separated" scores option

  • When using multiple engagement questions, it's possible to isolate the core engagement question upon which the eNPS is calculated i.e. "How likely is it you would recommend [company name] as a place to work?
  • Double counting is eliminated. For example, if a low score is given to a subdriver question, the driver score is unaffected since the driver and subdriver scores are not aggregated 
  • The driver and subdriver scores are more sensitive to customisation of questions since drivers and subdriver scores are not aggregated
  • The split mode will also be reflected in the calculation of strengths and priorities, meaning that when a driver or a subdriver is selected as a strength or a priority, it is only based on the isolated question that belongs to that driver or subdriver

Article: Data aggregation and anonymity
Article: Peakon benchmarking: what is it and how do you compare?
Article: Enabling and using the sensitive comments feature

 


 

Did this answer your question?