Skip to content

Commit

Permalink
Merge pull request #9178 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
Publish main to live, 01/13/25, 10:30 AM PT
Ruchika-mittal01 authored Jan 13, 2025
2 parents bed5362 + dcdf950 commit 8baab88
Showing 10 changed files with 136 additions and 98 deletions.
34 changes: 18 additions & 16 deletions Viva/glint/reports/act-strengths-opportunities.md
Original file line number Diff line number Diff line change
@@ -14,18 +14,20 @@ search-appverid: MET150
ms.topic: article
ms.service: viva-glint
ms.localizationpriority: high
ms.date: 08/29/2024
ms.date: 01/13/2025
---

# Use Viva Glint to act on Strengths and Opportunities

The Strengths & Opportunities (S&0) section is designed so a manager can focus on opportunities first, as they have the highest impact on employee engagement. For this reason, the option to *Take Action* appears by default in the Opportunities section. Taking action is initiated by:
The Strengths & Opportunities (S&0) section of a feedback report is designed so a manager can focus on opportunities first, as they have the highest impact on employee engagement. For this reason, **Take Action** appears by default in the Opportunities section. Continue the process:

- Selecting the **Take Action** button.
- Selecting the **ellipses** in the Strengths or the Opportunities column and selecting **Take Action**.
- Select the **Take Action** button.
- Select the **ellipses** in the Strengths or the Opportunities column and then selecting **Take Action**.

## Watch these videos

Share these tutorials with your managers.

**Lean into your strengths with Microsoft Viva Glint** (2:30)

> [!VIDEO https://www.microsoft.com/videoplayer/embed/RW132G0]
@@ -35,30 +37,30 @@ The Strengths & Opportunities (S&0) section is designed so a manager can focus o
> [!VIDEO https://www.microsoft.com/videoplayer/embed/RW12ULW]
> [!NOTE]
> If there are less than two eligible items ranked, the Strengths & Opportunities section is hidden on a user's dashboard. This can happen when:
> - There are insufficient results
> - All items have low or medium impact
> - A user is on a report filtered to only one item
> When less than two eligible items are ranked, the S&O section is hidden on a user's dashboard. This happens when:
> - There are insufficient results.
> - All items have low or medium impact.
> - A user is on a report filtered to only one item.
## Why does my screen indicate *View Focus Area* rather than *Take Action*?

When a manager has already acted - by choosing a Focus Area - the platform indicates View Focus Area. This option is to view how the manager and their team are progressing in their team conversations and action taking.
When a manager has already acted -chosen a Focus Area- the platform indicates **View Focus Area**. This feature shows how the manager and their team are progressing with Team Conversations and action taking.

>[!NOTE]
> *Take Action* or *View Focus Area* does not appear for users without *Create Focus Areas* enabled within their role permissions.
> *Take Action* or *View Focus Area* doesn't appear for users without *Create Focus Areas* enabled within their User Role permissions.
## Understand realized vs. unrealized strengths
## Understand realized versus unrealized strengths

Within the strengths section, you may see "realized" or "unrealized" labels or no such label.
Within the strengths section, you may see **realized** or **unrealized** labels, or even no such label.

- Realized strength - something your team is good at and do on a regular basis
- Unrealized strength - something that your team is good at but doesn't practice regularly and should be considered as an opportunity
- Unlabeled - the gap between what is realized and unrealized, for purposes of calling out the items that deserve attention
- **Realized strength:** something your team is good at and does on a regular basis.
- **Unrealized strength:** something that your team is good at but doesn't practice regularly and should be considered as an opportunity.
- **Unlabeled:** - the gap between what is realized and unrealized, for purposes of calling out items that deserve attention.

## Custom Strengths and Opportunities

Outcomes and comparisons used to calculate S&Os can be customized in either of the following ways:

- Select **Settings** to reveal the option to change outcomes and comparisons.
- In the Strengths and Opportunities section, select the hyperlinked words to change the outcome or comparison.
- In the Strengths and Opportunities section, select the **hyperlinked words** to change the outcome or comparison.

25 changes: 13 additions & 12 deletions Viva/glint/reports/aggregate-trending.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Viva Glint aggregate grouping - trends and best practices
description: Aggregate grouping can surface useful insights but the survey cycles must be identical in order for this trend to show.
description: Aggregate grouping can surface useful insights, but the survey cycles must be identical in order for trend data to show.
ms.author: JudithWeiner
author: JudyWeiner
manager: MelissaBarry
@@ -14,7 +14,7 @@ search.appverid: MET150
ms.topic: article
ms.service: viva-glint
ms.localizationpriority: high
ms.date: 12/11/2024
ms.date: 1/13/2025
---

# Viva Glint aggregate groupings - trends and best practices
@@ -23,12 +23,12 @@ ms.date: 12/11/2024

Aggregate trending informs historical data over time. Trend points reflect matching items from one cycle to the cycle immediately preceding it. Changing items within an aggregate (group) interrupts trend.

## Viva Glint aggregate trending terminology
## Aggregate trending terminology

| Term | Definition |
|-----------|-----------|
|Aggregate | A grouping of two or more items that measure a concept within a survey|
|Aggregate score | The average score of all the items divided by that number of items|
|Aggregate score | The average score of all the items divided by the number of item responses|
|Trend | Any difference in the score of a single item from one cycle to the previous cycle |
|Aggregate trend | Any difference in the combined score from one cycle to the previous cycle. Aggregate trend exists only when all items in two consecutive cycles are identical. |

@@ -39,35 +39,36 @@ Aggregate trending informs historical data over time. Trend points reflect match

Why **not** to use aggregate groupings in surveys:

- Surveying more frequently with fewer individual questions produce more useful, focused results.
- Surveying frequently with individual questions produces more useful, focused results.
- Measuring single items are better than multiple-item measures when it comes to utility and reliability. They can predict future behavioral outcomes, and they can do it consistently over time.
- Grouping multiple items (an aggregate) may limit the intervention opportunities for a single item within that group. That one item can become lost inside the group of items.
- Action taking should only happen at the single item level. Focusing managers on aggregate scores doesn’t help enable action.
- Grouping multiple items may limit the intervention opportunities for a single item within that group. An important item can become lost inside the group of items.
- Action taking should only happen at the single item level. Aggregate scores aren't recommended for action taking decisions.

>[!CAUTION]
> Trend is unreliable when it isn't measuring “apples to apples” - when there are differences in the items that appear in an aggregate between the new cycle and the same aggregate in the previous cycle. Trend is shown when at least one item is identical in the same aggregate in two cycles. Unless all items are identical, however, the aggregate trend isn't measuring a consistent group of items and isn't as reliable as single item trend data.
> - Trend is unreliable when it isn't measuring apples to apples. When there are differences in the items of an aggregate between the current cycle and the same aggregate in the previous cycle, trend is undependable.
> - Trend is shown when at least one item is identical in the same aggregate in two cycles. This means that unless all items are identical, the aggregate trend isn't measuring a consistent group of items and isn't as reliable as single item trend data.
## Aggregate trend examples across 2 cycles
There's a lot to consider when comparing survey cycles with aggregate groupings.

### Use case 1
3 items are part of the aggregate in both cycles, but because they aren't the same 3 items; no aggregate trend forms.
Three items are part of the aggregate in both cycles, but because they aren't the same three items; no aggregate trend forms.

:::image type="content" source="../../media/glint/reports/aggregate-1.png" alt-text="Chart showing that Cycle A and Cycle B don't share the same three items.":::

### Use case 2
One item is removed from the aggregate in the second cycle.
Cycle A contains 3 items, but Cycle B contains only 2 items. Aggregate Trend doesn’t exist because the aggregate isn't identical; there's no aggregate history. Individual items show trend but they don't reflect upon the aggregate as a whole unit.
Cycle A contains three items, but Cycle B contains only two items. Aggregate Trend doesn’t exist because the aggregate isn't identical; there's no aggregate history. Individual items show trend but they don't reflect upon the aggregate as a whole unit.

:::image type="content" source="../../media/glint/reports/aggregate-2.png" alt-text="Chart showing the 2 cycles share no history because the aggregate trend isn't identical.":::

### Use case 3
A new question is added to the aggregate grouping.
A new item is added to Cycle B so no aggregate trend is associated; there's no identical history.
A new item is added to Cycle B so no aggregate trend is associated. There's no identical history.

:::image type="content" source="../../media/glint/reports/aggregate-3.png" alt-text="Chart showing that no aggregate history is associated between the 2 cycles.":::

## Aggregate trend across 3 or more cycles
## Aggregate trend across three or more cycles

>[!IMPORTANT]
>Trend always looks at the previous cycle.
21 changes: 9 additions & 12 deletions Viva/glint/reports/alerts-report-attrition-risk.md
Original file line number Diff line number Diff line change
@@ -14,7 +14,7 @@ search-appverid: MET150
ms.topic: article
ms.service: viva-glint
ms.localizationpriority: high
ms.date: 06/18/2024
ms.date: 01/13/2025
---

# The Viva Glint Alerts report and Attrition Risk Index
@@ -32,11 +32,11 @@ The Alerts report is found on the **Reports** tab of the admin dashboard. Alerts
## Select attributes in General Settings to generate an Alerts report

>[!IMPORTANT]
>Attributes must be preselected in [General Settings](https://go.microsoft.com/fwlink/?linkid=2230744) for an Alerts report to generate. Create alerts based on specific user attribute combinations. If no attributes are selected, no alerts are created.
>Attributes must be preselected in [General Settings](/../../viva/glint/setup/manage-general-settings) for an Alerts report to generate. Create alerts based on specific user attribute combinations. If no attributes are selected, no alerts are created.
:::image type="content" source="../../media/glint/reports/reports-alerts-attributes.png" alt-text="Screenshot of the dropdown box in General Settings to choose attributes that will trigger Alert reporting." lightbox="../../media/glint/reports/reports-alerts-attributes.png":::
:::image type="content" source="../../media/glint/reports/reports-alerts-attributes.png" alt-text="Screenshot of the attribute dropdown box in General Settings that triggers Alert reporting." lightbox="../../media/glint/reports/reports-alerts-attributes.png":::

Populations are defined by the attributes in your Employee Attribute File. The alerts algorithm searches for patterns within single attributes (for example, Team: Sales > Corporate Sales) and combinations of attributes (for example, gender and tenure > 5 years). If a population or demographic group has scores for items that are statistically significant, that group is tagged for an alert.
Populations are defined by the attributes in your Employee Attribute File. The Alerts algorithm searches for patterns within single attributes (for example, Team: Sales > Corporate Sales) and combinations of attributes (for example, gender and tenure > 5 years). If a population or demographic group has scores for items that are statistically significant, that group is tagged for an Alert.

Configure which demographic attributes are used by the alerts algorithm:

@@ -48,7 +48,7 @@ Configure which demographic attributes are used by the alerts algorithm:

Example #1:

If all the subpopulations in Engineering have low scores on *Purpose* and *Role*, but one subpopulation of Engineering (for example, *Engineering & Tenure > 5 years*) has low scores for *Career*, then two Alert populations will be visible:
If all the subpopulations in Engineering have low scores on *Purpose* and *Role*, but one subpopulation of Engineering (for example, *Engineering & Tenure > 5 years*) has low scores for *Career*, then two Alert populations are visible:

- Engineering for both questions – *Purpose and Role*
- Engineering & Tenure > 5 years for the question on Career
@@ -68,26 +68,23 @@ Glint can predict the effect of score differences and overall response profiles

Populations identified with elevated attrition risk are those that show a higher future attrition rate than your company's average.

Based on extensive cross-validation studies, when using our standard survey questions/items, risk alerts have a precision of at least 80% and in many cases, even higher. If a population is flagged for elevated attrition risk, there is at least an 80% chance that attrition will be elevated.
Based on extensive cross-validation studies, when using our standard survey questions/items, risk alerts have a precision of at least 80% and in many cases, even higher. If a population is flagged for elevated attrition risk, there is at least an 80% chance that attrition is elevated.

The model uses Glint standard items in making predictions to allow for the most useful information to be available. Outcome items - eSat and Recommend - are immensely powerful and are a proxy for many insights, so a minimal set of items should include at least eSat and Recommend.
The model uses Glint standard items in making predictions to allow for the most useful information to be available. Outcome items -eSat and Recommend- are immensely powerful and are a proxy for many insights, so a minimal set of items should include at least eSat and Recommend.

>[!TIP]
> Regularly incorporate the Alerts report into your Viva Glint dashboard.
>[!NOTE]
>The Elevated Attrition Risk model was updated in October 2022.
## Set up the Alerts report

Configure which demographic attributes you want to include in **Alerts** from **General Settings** on the admin dashboard. To configure them initially, or to change them over time:

1. Navigate to **Reporting,** then **Attributes for Alerts.**
2. From the attributes you have preselected in your Employee Attribute File, narrow down to those items *most important to attrition risk* within your organization.
2. From the attributes preselected in your Employee Attribute File, narrow down to those items *most important to attrition risk* within your organization.
- Use the Search box to add attributes.
- Delete attributes by choosing the **X** next to those you don't want on the report.

> [!TIP]
> Select only attributes that are necessary for Alerts, such as important hierarchies, tenure, and generation. Avoid attributes with many values that can't be grouped, such as hire date, birth date and manager email. Using all attributes doesn't surface helpful insights.
> Select only attributes that are necessary for Alerts, such as hierarchies, tenure, and generation. Avoid attributes with many values that can't be grouped, such as hire date, birth date and manager email. Using all attributes doesn't surface helpful insights.
3. Select thresholds for the minimum population size (default is 20 respondents) and the minimum score differences (default is eight points) that qualifies for an alert. You may choose not to see alerts for populations smaller than 25 respondents or score differences smaller than 10 points. Filter the populations by size, using the slider in the Alerts report.
Loading

0 comments on commit 8baab88

Please sign in to comment.