The context has an impact on all of the data contained within the dashboard, including all engagement and driver scores, comments, and even the benchmarks used. This article will explain how the benchmark adapts to the context view. It will contain:
- How it works
- Administrator's point of view
- Manager or senior leader's point of view
- Exception: Segment specific benchmark
How it works
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. You can think of the context switcher as an all-round filter to all survey data.
The areas segment's scores are benchmarked against depends on how the segment is viewed. The below table contains the general rules the system follows for benchmark selection:
|Context is set to the company||
The company score is benchmarked externally, to the appropriately chosen industry engagement score
|Context is set to a specific segment||
When the context is set to a specific segment, for example a manager segment, an office location, a department, an age group or a tenure category, scores of this segment will be benchmarked to the company scores
|Context is set to a specific segment, while viewing a sub-segment||
When viewing a 'segment within a segment' (for example the segment Females within the context of London), the sub-segment will be benchmarked to the main segment score (in this case Female segment within London is benchmarked to the overall London score)
Note: Customers using True Benchmark can click on The True Benchmark detail to view the slide-out panel that informs them of the benchmark source. Use this if you are unsure where the benchmark is coming from.
Administrator's point of view
An administrator sets their context to the company, and looks at the engagement score of the Marketing department (7.2). Since Marketing is a sub-segment of the company, this score is benchmarked against the overall company score (7.8).
The administrator then sets their context to London, and then looks at the Marketing department segment. The engagement score for Marketing has now changed (8.1), since now they are looking specifically at the Marketing employees in London only.
Additionally the benchmark has changed to be compared against the London average engagement score, instead of the company wide engagement.
Manager or senior leader's point of view
The majority of managers and senior leaders will have access to one or two contexts, depending on the number of employees they have directly reporting to them.
When a manager has her context set to her own team, the segment is benchmarked against the engagement score of the company.
However, when she views a sub-segment, for example the tenure segment 1 year -2 years after starting, this segment is benchmarked to her overall team score, since she is only viewing the portion of this segment that is within her team.
If an administrator were to view the whole 1 year - 2 years after starting segment it would be benchmarked to the company.
The same overall logic applies to users who manage multiple segments, not just their own direct or all reports.
Exception: Segment specific benchmark
Customers on the Premier plan can set a segment specific benchmark to a high-level segment (eg. a specific entity) and propagate that benchmark preference to the segments hierarchically linked to the high-level segment.
In such instances, when viewing in the context of that segment, the segment specific benchmark will be applied. To learn more, see About benchmarking and how it works.