After the end of every survey round (at 1:00 AM UTC), Peakon evaluates which segments need updated strengths and priorities.
Within each of these segments, Peakon then identifies specific drivers as strengths and priorities based on the associated survey scores.
This article covers each of these two processes in the following sections:
- Context selection - which contexts qualify for updated strengths and priorities
- Driver and subdriver selection - which drivers within a context qualify as strengths or priorities
For more information, please see Strengths and priorities and how they work.
The context switcher is located in the top left-hand corner of the Peakon dashboard, and allows users who have access to multiple datasets to switch between them.
The following checks ensure that Peakon only updates strengths and priorities within a context when enough new feedback has been collected to warrant an update:
- The aggregated participation rate for the context is more than 25% since the last update of strengths and priorities.
- At least 30% of the segment’s employees have been included in a survey schedule since the last update of strengths and priorities. This check refers to both enabled and disabled survey schedules.
The above logic tries to find the right balance by ensuring that priorities and strengths for each context are not updated unless Peakon receives feedback from a significant portion of employees.
The second check also prevents priorities and strengths for larger segments, such as male and female segments, being updated every time smaller segments are surveyed when running multiple survey schedules and frequencies for different target populations.
Example: A company runs an annual company-wide survey. The company also haves 1 department that runs a separate monthly survey and represents only 10% of the company’s employees. The checks prevent the company-wide results from updating monthly based solely on 1 department’s scores.
Running multiple survey schedules at different times
Some companies choose not to have company-wide surveys and instead set up multiple schedules, on various frequencies, for different populations of their employees (Example: regional surveys). In such instances, updates to the company-wide strengths and priorities are subject to the same checks and logic.
Consider such a company’s gender segments, which would represent a large portion of employees. The checks ensure that strengths and priorities don't recalculate every time the company surveys a small portion of those employees.
However, assuming the company had 40 surveys, each representing 2.5% of the company’s employees, the checks would also ensure that strengths and priorities for the gender segments update periodically once the company has surveyed 30% of the segment.
Driver and subdriver selection
A driver or a subdriver can become a priority for a combination of 2 reasons:
- Driver performance is low (measured against the 75th percentile of the benchmark).
- Driver impact on the overall score is high.
Most priority drivers have a strong negative difference to benchmark and high impact on the overall score, however a driver can become a priority even if it only meets 1 of the criteria. Example: Finding statistically significant driver impacts on segments with fewer than 30 people is more difficult. Difference to benchmark then becomes the main way to determine strengths and priorities, with no impact circles displayed.
Sometimes drivers that perform above benchmark become priorities. A driver must be in the top 75th percentile not to be eligible to become a priority.
It's possible for a driver to be above benchmark in Average mode, while being below benchmark in NPS mode, due to methodology differences. The strength and priority calculation uses scores from the mode that you selected in your company data settings.
In rare cases, it's possible for a priority to be above benchmark and for a strength to be below benchmark.
To determine the strength and priority drivers, Peakon:
- Assigns each driver a prioritization score using this calculation: score = performance x impact.
- Ranks all drivers by their prioritization score.
- Sets the highest and lowest ranking drivers as strengths and priorities, respectively.
Even though Peakon suggests priorities, you can reject the suggestions and set your own priorities. See Strengths and priorities and how they work.
A note on the 75th percentile of the benchmark
When you display your dashboard at company level, the 75th percentile is of the industry benchmark. At company level, it's possible to see benchmark percentiles for a driver by hovering over this text on the driver's dashboard: In the top [%] in the [Industry]. These benchmark percentiles use rounding and have True Benchmark adjustments, so they won't always be an exact match to the 75th percentile that the calculation uses.
When you display your dashboard at a segment level, the 75th percentile is of the company scores. Segment dashboards don't display benchmark percentiles in the user interface.